Who is responsible
Makers Wall is run by Maxime Bertonnier, who is the data controller for the information described here. He is an individual based in France; Makers Wall is not a registered company and isn’t run to make money. You can reach us at m.bertonnier@gmail.com.
What we store and why
| Part | What | Why |
|---|---|---|
| Waitlist | Name, email, what you're building, a link to it (optional), and the campaign tags (utm_…) in the address you arrived from. | To invite you when we open, and to know which channels bring people in. |
| Account | Email, display name, handle, and either a password (stored only as a one-way hash, never readable) or the ID GitHub or Google gives us when you sign in with them. Single-use tokens for email verification and password resets, also hashed. | To create your account and let you sign in securely. |
| Profile | Everything optional you add: picture, solo or team, what you do, languages, bio, location, timezone, links (website, X, GitHub, LinkedIn), and the devices you can test on. Badges we award, like founding member. | To show other makers who they're working with and to match tests to the devices you have. |
| Projects | Name, tagline, description, URL, favicon and cover image (fetched from your page or uploaded), platforms, tags, language, the public brief, the private brief and access link, the testing window and the number of testers you want. | To list your project and brief the people who test it. |
| Tests | Claims and claim requests (with any note or decline reason), the dates and state of each test, reports (summary, time spent, devices used, findings with screenshots and video links), chat messages and attachments, and problem reports sent to us. | To run each test from claim to rating, and to step in when something goes wrong. |
| Ratings & reputation | Stars, tags, a private note and an optional public note for each rating, plus the scores we compute from them: tester and maker averages, completed tests, missed deadlines, and your place in the queue. | To reward good testing and decide who gets tested next. |
| Notifications | The notifications we send you, whether you've read them, which ones went out by email, and the kinds you've muted. | To keep you informed the way you chose. |
When you add a project, our bot (“MakersWallBot”) fetches that public page once to read its title, description and images. It doesn’t log in or follow links.
We use a single cookie that keeps you signed in. It’s strictly necessary, can’t be read by scripts, and expires after 7 days. When you join the waitlist we briefly use your IP address to limit how many sign-ups one address can make in an hour; it isn’t stored in our database.
Our legal bases
- Running the service you signed up for (contract): your account, profile, projects, tests, reports, messages, ratings and notifications.
- Legitimate interest: keeping the platform secure, preventing abuse and rating manipulation, fixing errors, and understanding where the waitlist comes from.
- Consent: analytics cookies. You can withdraw it at any time.
Who can see what
- Everyone, including visitors who aren’t signed in: your public profile (name, handle, picture, bio and the other profile details you fill in, badges, scores and public rating notes) and your published projects with their public brief.
- Only testers who claim your project: the private brief and access link.
- Only the maker and the tester of a test: its chat, attachments and report, and the private note attached to each rating. Ratings stay hidden until both sides have rated or the rating window closes.
- Us: we access data only to run the service, answer a problem report or investigate abuse.
Services we rely on
These companies process data on our behalf, only for the purpose listed:
- Resend: sending emails (verification, password reset, notifications).
- Railway (storage buckets): storing pictures, screenshots and videos you upload.
- Railway: hosting the website, API and database.
- Sentry: error reports from our server, so we can fix bugs.
- GitHub and Google: only if you choose to sign in with them.
- Google Analytics: only if you accept analytics cookies (below).
- Deskcord: the support chat on every page. Messages you send through it are delivered to our Discord server.
Some of these providers may process data outside the European Economic Area. When they do, they rely on safeguards such as the European Commission’s standard contractual clauses.
Analytics
With your consent, we use Google Analytics to count visits and see which pages help people, including when someone joins the waitlist. It sets cookies starting with _ga that last up to 13 months. Until you accept, Google’s script isn’t loaded at all.
You can change your mind any time with the Cookies link in the footer. Declining removes the analytics cookies already set.
How long we keep it
- Waitlist entries: until we open, or until you ask us to remove them.
- Account data: as long as your account is open.
- Verification and reset tokens: they expire within 72 hours and 2 hours.
- After you delete your account, we delete your profile and personal details within 30 days. Reports, messages and ratings you exchanged with other makers are kept for them, with your name removed.
Your rights
You can ask to access, correct, export or delete your data, to restrict or object to how we use it, and to withdraw consent. Most profile details can be edited directly in Settings; for everything else, write to m.bertonnier@gmail.com. We answer within a month.
If you think we’ve got something wrong, you can complain to your data protection authority. In France, that’s the CNIL (cnil.fr).
Age
Makers Wall is not for anyone under 16, and we don’t knowingly collect their data.
Changes
When we store something new or use data in a new way, we update this page and change the date at the top. If the change matters, we’ll tell you by email or in the app first.