Privacy policy
This English text is a translation. The French version is the binding one.
Version of 9 November 2026.
This policy explains how Peerbeta processes your data when you visit peerbeta.com, have an app tested, test apps or use the Android tester app.
1. Controller
The controller is Yvhan MOUAFO YO EI, sole proprietorship, SIREN 841 074 867, M2 chez YEMELI, 12 impasse de la Vallée, 78800 Houilles, France. For any question or request about your data: [email protected].
2. In short
- We process what is needed to run tests: your account and, depending on your role, your apps and tests, or your tester profile, device, opens and feedback.
- Developers see feedback under a tester number, never your name or email address.
- We do not sell your data.
- Basic audience measurement runs without prior consent, within the limits the CNIL (the French data protection authority) sets for that exemption: anonymous statistics about this site, crossed with no other processing. You can object to it. Detailed analytics, linking a payment to your visit, session recording and ad measurement wait for your consent.
- You can export your data and delete your account from Account › Privacy.
3. Data processed, purposes and legal bases
| Data | Examples | Why | Legal basis |
|---|---|---|---|
| Account | name, email address, photo, linked account identifiers (Google), sign-in methods, sessions, language, time zone, notification preferences | create and secure your account, email you | contract |
| Organization | spaces, members, roles, invitations | work together | contract |
| Apps and tests (developer) | app name and package, icon, description, opt-in link, countries, features to test, instructions, content declarations, announced updates, reports, suggested answers | run the test and produce the report | contract |
| Tester profile | languages, interests, Play account country, adult confirmation, level, reputation, quality score, quiet hours, reminders, sanctions | offer compatible tests, keep a reliable tester pool | contract; legitimate interest in fighting fraud |
| Device | manufacturer, model, Android version, country, language, time zone, Play Integrity verdict, notification token, tester app installation identifier | check the app is installed on a real phone, send reminders | contract; legitimate interest in fighting fraud |
| Test activity | timestamped opens and their outcome, time spent outside the tester app, usage time of the tested app if you grant usage access, mission answers, active days | prove real use, calculate credits and report figures | contract |
| Feedback and screenshots | texts, bugs, severity, screenshots, appeals, quality assessment, developer's opinion | pass feedback to the developer, check its quality | contract |
| Credits and referrals | credit movements, referral code, referrals | keep your balance | contract |
| Orders | offer, add-ons, amounts, promo code, status, proof of consent (date, terms version, answers), Stripe customer ID, invoice, receipt, guarantee claims and screenshot of Google's refusal | sell, invoice, apply the guarantee | contract; legal obligation (accounting) |
| Support and reports | messages, content reports | reply, moderate | contract; legal obligation (Digital Services Act) |
| Feedback and support through Quackback | feedback, ideas, votes, support chat messages and, when you are signed in, your account's identifier, name and email address; from the tester app, the name of the test your request comes from | answer you, decide what comes next | contract; legitimate interest in improving the service |
| Testimonials (developer) | quote, name and role shown, app name, screenshot of Google's acceptance, date of your consent | publish your testimonial on the site, once checked | consent, which you can withdraw at any time |
| Free tools | what you type in the Play Store listing writer; a fingerprint of your IP address for the usage limit | write the listing, prevent abuse | legitimate interest |
| Security | IP address and browser of a session, technical logs, audit log of sensitive actions, pages opened in the application | prevent abuse, diagnose errors, help you | legitimate interest |
| Basic audience measurement | page views, source, city or country, device type, key steps, links to other sites clicked; the IP address, shortened before it leaves our server, is only used to locate the visit | anonymous traffic statistics for peerbeta.com, not crossed with your account, your payments or any other processing | legitimate interest, under the conditions of the CNIL's consent exemption (you can object) |
| Detailed analytics and session recording | clicks, journeys, errors, performance, session replay (inputs masked); when you are signed in, your visits linked to your account (identifier, name, email address) | understand usage and fix bugs | consent |
| Where sales come from | the identifiers of your visit and session, attached to the payment at Stripe, then matched with the visit by DataBull | know which channels bring customers | consent ("Detailed measurement"); without it, the payment goes without your visit |
| Ad measurement | page views, account creation, checkout start | know whether a visit came from one of our ads | consent |
With Google sign-in, Peerbeta receives your Google identifier, name, email address and photo, never your password. You can remove Peerbeta's access in your Google account's security settings.
4. Who sees what
- The developer of a tested app sees your feedback, screenshots and mission answers under a tester number, along with testers' devices, Android versions and countries. They see neither your name, nor your email address, nor your IP address.
- An app's testers see its description, its instructions and, if the developer provides one, its test account.
- Members of an organization see that organization's apps and tests, according to their role.
- The Peerbeta team accesses the data needed for support, moderation, quality and fraud prevention. Its sensitive actions are recorded in an audit log.
- Google sees your Google address when you join the testers' Google group and an app's closed test, under its own privacy rules.
5. Artificial intelligence
Peerbeta uses Anthropic's Claude API to score and translate feedback, check that screenshots come from the tested app, and write the report, the suggested answers for the production access application form and Play Store listing texts. What is sent: the app's information, its features, feedback texts and screenshots. Testers appear as numbers; their phones and countries, as totals. No name or email address is sent.
6. Automated decisions
Each piece of feedback is scored by rules and, when available, by the AI. The result can be an automatic refusal, which means that feedback earns no credits. The refusal is told to you with its reason. You can contest it once: a person on the team then reviews the feedback and decides. Feedback marked "to review" is always decided by a person. The Play Integrity check can prevent an open from counting; a sanction for fraud is decided by a person.
7. Retention
| Data | Period |
|---|---|
| Account, profile, devices, preferences | as long as the account exists |
| Sign-in session | expires 7 days after its last renewal; erased when the account is deleted |
| Pages opened in the application | 90 days |
| Opens, active days, feedback, screenshots, appeals | as long as both the tester's account and the test exist; erased with either |
| Screenshots uploaded but never attached to feedback | 24 hours |
| Testimonials and screenshot of the acceptance | until you withdraw the testimonial, or when the test is deleted |
| Text typed in the Play Store listing writer | not kept: it is only used to write the listing |
| Fingerprint of the IP address for the free tools | 24 hours |
| Apps, tests, reports, suggested answers | as long as the space containing them exists; an organization keeps them when a member leaves |
| Credits | each credit expires 12 months after it is earned; the balance is erased with the account |
| Orders, invoices, proof of consent | 10 years (accounting obligation), anonymized when the account is deleted |
| Tester app API responses | 7 days |
| Content reports | 1 year after the case is closed |
| Export file of your data | 1 hour |
| Audit log of sensitive actions | 1 year; anonymized earlier, when the account is deleted |
| Log of AI calls (cost and amount of text processed, without the content) | 1 year |
| Status page probes (results per day, no personal data) | 90 days |
| Alerts and operations journal | 1 year |
| Fraud prevention fingerprints: network and browser | 1 year after they were last seen |
| Other fingerprints (device, installation, mailbox, card) | as long as the account exists |
| Fraud alert closed without action | 6 months after the decision |
| Fraud alert followed by a sanction or a credit adjustment | 3 years after the decision |
| Runs of the fraud check (counts only) | 90 days |
| Audience measurement (DataBull) | 25 months; its cookies last 1 year at most |
| Detailed analytics (PostHog) | 12 months; session recordings 30 days |
| Feedback, chat messages and support account (Quackback) | 2 years after your last exchange; you can ask for earlier erasure at [email protected] |
When an account is deleted, orders are not erased, because the law requires keeping them: the link to the Stripe customer, invoice and receipt links and free notes are removed; the invoice number, amounts and dates remain.
8. Recipients and processors
| Provider | Role | Where |
|---|---|---|
| Yvhan MOUAFO YO EI, M2 chez YEMELI, 12 impasse de la Vallée, 78800 Houilles, France, +33 6 38 19 78 81 | hosting of the site, databases and files | according to the host stated |
| Cloudflare, Inc. | network, tunnel and cache of the site | United States and global network |
| Resend | sending emails | United States |
| Anthropic | Claude API: scoring and translating feedback, reports, suggested answers, Play Store listing texts | United States |
| Stripe (Stripe Payments Europe Ltd. and Stripe, Inc.) | payment, invoices, refunds | Ireland and United States |
| Google (Google LLC, Google Ireland Limited) | Google sign-in, Google Groups, Play Integrity check | European Union and United States |
| Firebase Cloud Messaging (Google LLC) | tester app push notifications | United States |
| DataBull | audience measurement and, with your consent, where sales come from; instance self-hosted by the publisher (databull.alex-tsague.fr), behind Cloudflare | France |
| PostHog (PostHog Cloud EU) | product analytics and session recording, with your consent | European Union |
| Sentry (Functional Software, Inc.) | technical errors of the website, the servers and the browser: stack trace, service and page path, never the content of a request or a cookie; Sentry does not keep the IP address | European Union (Sentry's EU data region) |
| Quackback | feedback and support widget, feedback.peerbeta.com portal: feedback and messages, identity of the signed-in account, on an instance run for the publisher | according to the host stated |
| Discord | internal team alerts: new sign-ups and payments, with the member's name | United States |
| Telegram (Telegram Messenger Inc. and its group companies) | processor for the messaging of the team's internal alerts: the state of the service (outages, incidents, backups) sent by Peerbeta, sales, refunds and traffic sent by DataBull. These alerts contain no name, no email address and nothing else that identifies you: Peerbeta masks any email address that would slip into them | outside the European Union (notably the British Virgin Islands and the United Arab Emirates). Telegram signs no standard contractual clauses with bot operators: this is why nothing that identifies you is sent there |
| Meta Platforms Ireland Ltd. | measuring our ads, with your consent, only when we run ads | Ireland and United States |
Stripe, Google and Meta also act as controllers for their own purposes, under their policies. Peerbeta never sees your card number.
9. Transfers outside the European Union
Some providers process data outside the European Union, mainly in the United States. These transfers rely on the EU–US Data Privacy Framework when the provider is certified, and otherwise on the European Commission's standard contractual clauses. You can ask for a copy at [email protected].
10. Security
Traffic goes over HTTPS. Access to data depends on your role. Passwords and tester app tokens are stored hashed. The team's sensitive actions are logged.
11. Your rights
You can ask for access to your data, its rectification, erasure, restriction of its processing and its portability, object to processing based on legitimate interest, withdraw your consent at any time and give instructions on what happens to your data after your death.
- Export: Account › Privacy produces a file of your data, after confirming your identity.
- Deletion: from the same page. Orders are then anonymized (section 7).
- Objecting to basic measurement and consent choices: "Manage my choices" link in the footer, or Cookies and trackers.
- Other requests: [email protected]. We reply within one month.
You can also file a complaint with the CNIL, the French data protection authority (www.cnil.fr).
12. Minors
You must be at least 18 to create a tester account, and an adult to have an app tested. If we learn that an account belongs to a minor, we delete it.
13. Cookies
Cookies and browser storage are described on the Cookies and trackers page.
14. Changes
This policy may change. Each version is dated at the top of the page. For a significant change, you are notified by email or in the service.