At Tellyah, protecting your personal data is a priority. This policy explains, clearly and transparently, what data is collected, why, who processes it, and what your rights are.
This English version is provided for convenience: in case of discrepancy, the French version prevails.
1. Who is responsible for processing your data?
The controller of your personal data is:
BEEHAY
Entreprise Unipersonnelle à Responsabilité Limitée (EURL), a single-member limited liability company
Registered office: 14 rue Bausset, 75015 Paris, France
SIRET: 88384510900023
Email: support@tellyah.com
Data Protection Officer (DPO): not applicable.
For any question about your personal data:
support@tellyah.com
2. What data is collected?
2.1 Account and profile
- your email address and your password (stored in encrypted form by Firebase Authentication: we never have access to it in clear text), or your Google identifier, or your Apple identifier if you use social sign-in;
- a technical account identifier (uid);
- the date from which the tellys you start can be translated (section 5);
- if you have an account and your reading language is neither English nor French, that language and the date of your last visit (section 5);
- your username;
- your bio and your profile photo (optional).
2.2 Content you publish
- your tellys: titles, bubbles, choices, categories, keywords;
- the images you add (covers, bubble illustrations);
- your emos (reactions), your favourites and your reports, along with the reason given;
- your echoes: the feedback you choose from a predefined list and leave on a bubble of a telly. An echo is never free text. The telly's author does not know who left an echo: they see, for each bubble, the share of each echo and each emo received (see section 6);
- your "Another Take" suggestions: the short alternative (80 characters at most) that you propose on a bubble with choices. The telly's author does not know who proposed it: they see the ideas proposed most often, grouped by meaning, never your username;
- your Challenges: the written, reasoned feedback you send to the author of a telly that accepts Challenges, with the topics you chose. The telly's author sees your username;
- your messages in a Challenge discussion: if the telly's author chooses to discuss it, a private discussion opens between the two of you for 7 days. Only its two participants read it, unless one of them reports it (see section 4).
2.3 Usage data (subject to your consent)
If you consent, we measure how the app is used, including: telly opened, bubble read, choice made, emo added, echo left or removed, profile viewed, gem sent, sequel requested, share made.
These measurements are linked to your account identifier and to the identifier of the author of the content concerned. In other words, they describe interactions between users (who reads, who reacts to whose tellys, and how often). This information constitutes a social graph within the meaning of the regulations and of app store rules: we declare it as such. It is used exclusively to calculate the compatibility scores of the Community tab and to recommend tellys.
If you do not consent, this collection is disabled and the Community tab falls back to a ranking of popular tellas, without personalisation.
2.4 Technical data
- device model, operating system version, language;
- crash reports and performance diagnostics;
- push notification token (FCM) and device platform, to send you notifications;
- device attestation token (Firebase App Check / Play Integrity), to prevent fraudulent use of our servers.
2.5 Advertising data (subject to your consent)
- your advertising identifier and your consent signals, sent to Google AdMob to display ads.
2.6 Purchases
Purchases of gems and boosts are processed by Google Play. We receive neither your payment method, nor your bank details, nor your billing address. We only keep the resulting state in the app (gem or boost active, and its expiry date).
2.7 What we do not collect
- your address book: the app requests no permission to access your contacts and never accesses them;
- your location: the app uses no location API;
- your messages outside Tellyah (text messages, messaging apps), your files, your browsing history, your health data.
2.8 Year of birth
Challenges and their discussions are reserved for adults. The first time you use this feature, we ask for your year of birth, and nothing else (neither day nor month). It is never displayed, not even on your profile; it is not part of any usage measurement and is never passed on for advertising (it is hosted like the rest of your account, see section 6); it is used only to know whether you can use Challenges. It cannot be changed from the app; to correct it, write to support@tellyah.com.
3. Why is this data collected, and on what legal basis?
| Purpose | Data concerned | Legal basis |
|---|---|---|
| Creating and managing your account | 2.1 | Performance of the contract (Terms of Use) |
| Publishing and hosting your content | 2.2 | Performance of the contract |
| Translating published tellys, to offer them to users of other languages | 2.1, 2.2, 2.4 | Legitimate interest (you can object, section 5) |
| Moderation and platform security | 2.2, 2.4 | Legitimate interest + legal obligation |
| Restricting Challenges to adults | 2.8 | Legitimate interest (protection of minors) |
| Push notifications | 2.4 | Performance of the contract, can be turned off in the system settings |
| Audience measurement and content recommendation | 2.3 | Consent (can be withdrawn at any time) |
| Displaying ads | 2.5 | Consent (can be withdrawn at any time) |
| Improving the app, diagnosing failures | 2.4 | Legitimate interest |
| Accounting and legal obligations | 2.6 | Legal obligation |
4. Automated content moderation
Before publication, the texts and images of your tellys (covers, illustrations) and your profile photo are automatically analysed to detect content prohibited by our Terms of Use (hate, violence, sexual content, endangering minors):
- texts are sent to the moderation API of OpenAI, L.L.C. (United States);
- images are sent to the Google Cloud Vision SafeSearch service.
"Another Take" suggestions and the text of a Challenge are analysed in the same way before being passed on to the telly's author, by OpenAI's moderation API and then by an OpenAI model that catches what the API misses (an attack on the person rather than on the telly, solicitation, contact details, a message with no substance). To group similar "Another Take" suggestions, their text is also converted by OpenAI into a numerical representation of its meaning, stored with the suggestion.
Messages in a Challenge discussion are neither analysed nor filtered: the telly's author chose to discuss it, and we do not read these exchanges. You can block or report the other participant at any time; a report is reviewed by our team.
These analyses may result in a publication being automatically blocked. Under Article 22 of the GDPR, you can challenge this decision and ask for a human review by writing to support@tellyah.com.
None of these providers uses your content to train its models. Image analysis results are cached as a cryptographic fingerprint (SHA-256), not as the image itself.
5. Video sharing, text-to-speech and translation
When you generate a share video from a telly, the text of the bubbles concerned is sent to the Google Cloud Text-to-Speech service to produce the narration. The video itself is assembled on your device.
Automatic translation only applies to published tellys: a draft is never translated, nor is a sequel until it is published. As soon as a telly is published, its text (title, bubbles and choices) is sent to OpenAI, L.L.C. (United States) so that it exists in English and in French. It may also be translated into the reading languages of users with an account. A published sequel and a modified title are translated like the rest of their telly. This text is sent on its own, without your identifier or that of the users who read it.
If you were already using Tellyah when translation was done on your device, a telly you had started before seeing the in-app message announcing this change is never translated, even if you publish it later or add a sequel to it.
Each translation is stored with the telly, then shown to the users who later read it in that language. Translations follow the telly: if it is deleted, they are deleted with it.
To choose these languages, the app records, for each account whose reading language is neither English nor French, that language and the date of its last visit. No other user can read this information.
As with moderation, OpenAI does not use these texts to train or improve its models. OpenAI may, however, keep the texts sent and their translations for up to 30 days, in abuse-monitoring logs, and longer if required by law or if reasonably necessary to protect its service or third parties. Deleting the telly does not erase these logs.
You can object to the translation of your tellys by writing to support@tellyah.com: they will no longer be translated, and their translations will be removed from our servers.
You can object to the recording of your reading language by turning off "Automatic translation" in your profile settings: it is then erased, and tellys are shown in their original version.
6. Who has access to your data?
Your data is accessible:
- to the Tellyah team, to the extent necessary for the operation and improvement of the service;
- to the author of a telly, for the echoes you leave on its bubbles: they see, bubble by bubble, the share of each echo received, without your username or your identity. Other users do not see your echoes;
- to the author of a telly, for a Challenge you send them: they see your username, your text and the topics you chose, and can discuss it with you. They never see your username for an "Another Take" suggestion: only the ideas proposed most often, grouped by meaning;
- to the following processors, acting on our behalf and under our responsibility:
| Processor | Role | Data concerned |
|---|---|---|
| Google LLC · Firebase Authentication | authentication | 2.1 |
| Google LLC · Cloud Firestore, Cloud Storage, Cloud Functions | hosting of accounts and content | 2.1, 2.2, 2.6, 2.8 |
| Google LLC · Firebase Cloud Messaging | push notifications | 2.4 |
| Google LLC · Firebase Analytics & BigQuery | audience measurement, recommendation | 2.3 |
| Google LLC · Firebase Crashlytics | crash reports | 2.4 |
| Google LLC · Firebase App Check / Play Integrity | fraud prevention | 2.4 |
| Google LLC · Cloud Vision, Cloud Text-to-Speech | image moderation, text-to-speech | 2.2 |
| Google LLC · AdMob | serving and measuring ads | 2.5 |
| Google Ireland Ltd · Google Play | processing purchases | 2.6 |
| OpenAI, L.L.C. | automated moderation and translation of texts, numerical representation of the meaning of "Another Take" suggestions | 2.2 |
These providers are bound by contractual confidentiality and security obligations in accordance with Article 28 of the GDPR.
Tellyah never sells, rents or transfers your personal data to third parties. Google AdMob, as an advertising partner, receives your advertising identifier when you have consented to it: this is the only transfer to a third party acting on its own behalf.
7. Where is your data stored? Transfers outside the European Union
- Your accounts, your content and your analytics data are hosted in the European Union, region europe-west1 (Belgium): Firebase and BigQuery.
- Some processing takes place in the United States: AdMob, the moderation and translation of texts by OpenAI, and certain internal Google processing.
These transfers are governed by:
- the participation of Google LLC in the EU–US Data Privacy Framework, recognised by an adequacy decision of the European Commission;
- the Standard Contractual Clauses approved by the European Commission, for OpenAI and for processing not covered by the DPF;
- additional technical and organisational measures.
You can obtain a copy of these safeguards at support@tellyah.com.
8. Retention periods
| Data | Period |
|---|---|
| Account and profile | as long as the account is active |
| Published content | as long as the account is active, or until you delete it |
| Emos and echoes you leave | as long as the account is active, or until you remove them; when the account is deleted, anonymised: they are no longer linked to you and only count towards each bubble's totals |
| Year of birth | as long as the account is active; deleted with the account |
| "Another Take" suggestions | as long as the account is active, or until you remove them; deleted with the account |
| Challenges and discussion messages | 12 months after the discussion is closed (or after sending, if no discussion was opened); deleted with the account, the other participant keeping their own messages until then |
| Telly translations | as long as the telly exists, then deleted with it |
| Texts sent to OpenAI for translation | up to 30 days at OpenAI, longer in the cases set out in section 5 |
| Reading language and date of last visit | until your next visit, and at most as long as the account exists |
| Usage data and technical logs | 14 months maximum (CNIL recommendation) |
| Crash reports | 90 days |
| Exchanges with support | 3 years after the request is closed |
| Accounting records related to purchases | 10 years (legal obligation) |
After account deletion: the request opens a 48-hour cancellation window, during which your tellys remain visible to other users. At the end of this period, the deletion is carried out automatically. The following are then deleted: your account (email address, password, or link with Google or Apple) and your profile, with everything attached to it (favourites, blocked users, notification tokens); all your tellys, drafts included, with their bubbles and what other users have left on them (emos, echoes, "Another Take" suggestions, gems, sequel requests); and the images you added.
Deleting the account does not erase, in particular:
- the gems you sent and your sequel requests on other users' tellys: they remain recorded under the technical identifier of your former account and contain neither your username nor your email address;
- notifications already received by other users, which may mention your username or the title of your tellys: they remain in their list until they have read them;
- the reports you sent or that concern you, kept for as long as necessary for moderation and to comply with our legal obligations;
- usage data and crash reports, which follow the periods in the table above;
- share videos already distributed outside Tellyah, which may show your username and profile photo, and whose distribution we do not control;
- the audio narrations produced to create a share video, which are not linked to any account.
Some data may be kept longer in case of a legal obligation or litigation.
9. Your rights
Under the GDPR and the French Data Protection Act (loi Informatique et Libertés), you have the following rights:
- access: obtain a copy of your data;
- rectification: correct inaccurate data;
- erasure: delete your data;
- restriction: temporarily suspend a processing;
- objection: object to a processing based on legitimate interest;
- portability: retrieve your data in a machine-readable format;
- withdrawal of consent: at any time, from the Trust & care screen of the app (button "Manage analytics consent");
- post-mortem instructions: decide what happens to your data after your death.
Write to support@tellyah.com. We reply within 1 month (extendable by 2 months in complex cases).
If you believe your rights are not being respected, you can lodge a complaint with the CNIL, the French data protection authority:
www.cnil.fr/fr/plaintes
10. Account deletion
You can request the deletion of your account at any time from your profile, in the Trust & care screen of the app (button "Delete account"), or by writing to support@tellyah.com. From the app, the request immediately deactivates your access to the service, then your account and your tellys are deleted at the end of the 48-hour period described in section 8. During this period, you can cancel the deletion by signing in again; after that, it is final. Section 8 details what is deleted and what is kept.
11. Advertising and consent
The app displays ads provided by Google AdMob.
In the European Economic Area, the United Kingdom and Switzerland, a consent form compliant with the TCF framework is shown to you at first launch. Your choice governs both advertising and audience measurement: without consent, Firebase Analytics is disabled and the ads displayed are not personalised.
You can change this choice at any time from the Trust & care screen of the app.
12. Cookies, trackers and audience measurement
Tellyah uses no cookies on its website, neither advertising nor measurement cookies.
- Strictly necessary (exempt from consent): session maintenance, security.
- Subject to consent, in the app only: advertising identifier (AdMob), audience measurement identifiers (Firebase Analytics, BigQuery).
Website audience measurement
The website measures its own traffic, without cookies and without any identifier that would follow you from one visit to the next. Here is exactly what is recorded, for each event:
- a randomly drawn session identifier, kept in your browser's session storage: it disappears when you close the tab, and nothing links it to a later visit or to your account;
- the path of the page viewed, without URL parameters;
- the display language, the system (Android, iPhone or computer) and a screen-width bracket, never the exact dimensions;
- the domain name of the site you came from, never the full address;
- the campaign parameters (
utm_source,utm_medium,utm_campaign) present in the address; - the event itself: page view, click on an install button, interaction with the playable excerpt, language change, end of session;
- the detail of this event, chosen from a closed list: which install button and to which store, which branch of the playable excerpt, to which language, and the length of the visit, rounded to five seconds.
What audience measurement never records: your IP address, even truncated; the details of your browser (user-agent); the full address of the site you came from; the exact dimensions of your screen; and any identifier that would outlive the tab. None of this information is read by the measurement service, or stored in its records.
To be complete: like any web service, our host keeps technical connection logs that contain your IP address, kept for 30 days and used only for security and diagnostic purposes. They are separate from the audience measurement described here, and are never matched with it.
If your browser signals a refusal of measurement (Global Privacy Control or Do Not Track), nothing is sent at all, and no session identifier is even created.
Where this data goes. It is received by a function hosted in the European Union (Google Cloud, europe-west1, Belgium) and stored in BigQuery, in the same region. No new processor is involved: they are the same as those already listed in section 6.
How long. These records are deleted automatically after 425 days, about fourteen months, enough to compare a period with the same one a year earlier. The deletion is done by the database itself, not by a person.
To find out more about cookies and trackers in general: www.cnil.fr/fr/cookies-et-autres-traceurs
13. Minors
Tellyah may only be used by people aged at least 16, in accordance with the Terms of Use. We do not knowingly collect data about younger people. If you notice that an account has been created by a minor under 16, write to support@tellyah.com: the account will be deleted.
Challenges and their discussions are reserved for people aged 18 and over, based on the year of birth you declare (see section 2.8). If the declared year of birth indicates an age under 18, the account can neither send nor receive Challenges, and no exception is possible.
Our child protection policy is detailed on the Child safety page.
14. Data security
Tellyah implements appropriate technical and organisational measures to protect your data against unauthorised access, loss, alteration or disclosure: systematic encryption of communications (clear-text traffic is forbidden by the app), strict access rules at database level, device attestation and logging of administrative access.
15. Changes to this privacy policy
This policy may be updated to reflect changes to the service or to regulations. In case of a significant change, users are informed in the app.
16. Contact
For any question about this policy or your personal data:
support@tellyah.com