Privacy policy
Version 2026-11-17
A1. In short
- Your data is yours. Your records, memories and photos are processed to provide the Service to you; they are not used for advertising and not sold.
- No ads, no tracking, no analytics. Fama contains no advertising, ad-measurement or usage-analytics software (SDKs); we do not track you across apps and websites.
- Only the people you invite see what you share. You decide who sees what. In the Me profile, close people can see only your period dates; your mood, water, rituals and journal are never shared with anyone.
- Your health data requires your explicit consent, and you can withdraw it at any time.
- No location is collected. Location and other metadata are removed from your photos on your phone before upload.
- Download or delete at any time. You can download all your data in the app and permanently delete your account inside the app.
- Your data is stored encrypted on servers in the European Union (Frankfurt, Germany).
A2. Controller and contact
Controller: the person who develops Fama. Their name and contact details are at the end of this policy (A20).
A3. What this policy covers
This policy covers the Fama mobile app (iOS and Android), the app's server side, and the legal pages and web account-deletion page on famastudio.app. It applies to everyone who uses Fama: profile owners and invited family members, parents, partners and doctors. Processing within Apple's and Google's own services (sign-in, App Store, Google Play) is governed by their privacy policies.
A4. What data we process
| Category | Examples | Source |
|---|---|---|
| Account information | E-mail address (with Sign in with Apple this may be Apple's private relay address), Apple/Google account identifier, first name, last name, display name in the circle, role label (Mum, Dad, Parent), profile photo, app language and theme preference, account creation and sign-in times | You; from Apple or Google when you sign in with them |
| Profile information | Profile type (Pregnancy, Baby/child, Me), the baby's name, date and time of birth, sex (girl, boy or prefer not to say), birth weight and length, profile photo; estimated due date; your answer to "Is this your first pregnancy?"; pregnancy status (ongoing, completed with birth, or tracking stopped) | You |
| Health and pregnancy data (special category) | Kick counts, contractions, weight (including pre-pregnancy weight), symptoms and severity, mood, sleep, water; appointments (date, doctor's name, place, type, questions for your doctor, notes); hospital bag; ultrasound images and the measurements you enter | You |
| Baby care and health data (special category) | Feeding (breastfeeding, bottle, solids), sleep, diapers (colour, consistency), temperature and measurement site, medicines (name, dose, times, doses given), growth (weight, length, head circumference), vaccines, teeth, firsts, bath, outings, pumping and milk stock, tummy time; the temperature threshold and goals you set | You and invitees you allow to add care logs |
| Cycle data (special category) | Period days and flow (spotting, light, medium, heavy), estimated next period and cycle length, cycle symptoms, energy, mood, sleep, water, rituals; confirmation that you read the period-tracking notice | You |
| Memories and content | Memories, notes, journal, photos, albums and memory books, comments, hearts, tasks | You and people in your circle |
| Sharing data | Invitations (role, areas opened, the name you gave the invitee, status, expiry), memberships and approvals; while approval is pending, the accepting account's name and its server-masked e-mail shown to the owner, people you have blocked, ownership transfer offers, comment reports (reason, note and the reported comment's text at the time) | You and invitees |
| Notification and device data | Your notification preferences and times, in-app notification inbox (e.g. "Mert added a log"), read status; a reminder log kept on your phone; app lock and appearance settings | You; partly only on your phone |
| Purchase status | Plan (Işıltı, İnci, Gezegen), monthly/yearly, status (active, grace period, expired, refunded), store (App Store, Google Play), expiry date; for gifts, the giver, recipient, plan, period and store transaction ID | Verified with Apple's or Google's servers |
| Consent and security records | Consents given and withdrawn (type, text version, time); audit log (changes to sharing permissions, data downloads, account deletion, rate-limit hits); failed invite code attempts; rate-limit counters | From the operation of the app |
| Technical connection data | Server logs such as IP address, request time and app/client information; browser environment signals for the security check during e-mail sign-in | Your device, via our server provider and Cloudflare |
| Support correspondence | Your e-mail address, message and app version when you write to us | You |
What we do not collect: Location (the app has no location permission), contacts, advertising identifiers (IDFA/AAID), face or fingerprint data (your phone performs the lock check and the data never reaches the app), the contents of your calendar (you add an appointment with your phone's own dialog; Fama does not read your calendar), card and payment details (they stay with Apple or Google).
A5. How we collect data
- From what you enter: on logging screens, during profile setup, in memories and the album.
- From what invitees enter: baby logs, comments, hearts and tasks by people you have given care permission.
- From sign-in providers: your e-mail and (if you allow) your name when you sign in with Apple or Google.
- From the stores: from Apple's and Google's servers to verify purchase status.
- Automatically: technical logs created when the app connects to the server.
Your data is collected electronically, by both non-automated (manual) and automated means.
A6. Purposes and legal bases
| Purpose | Data | KVKK legal basis | GDPR legal basis |
|---|---|---|---|
| Creating your account, signing you in, managing your account | Account information | Art. 5(2)(c): establishment and performance of a contract | Art. 6(1)(b) |
| Storing and displaying pregnancy, baby and cycle records; calculating weeks, estimates and charts; preparing record summaries and exports | Health, baby and cycle data | Art. 6(3): explicit consent (for baby data, the explicit consent you give as parent/guardian) | Art. 9(2)(a) explicit consent |
| Storing memories, photos, journal and albums | Memories and content (including health-related content such as ultrasound images) | Art. 5(2)(c); for health-related content Art. 6(3) explicit consent | Art. 6(1)(b); for health-related content Art. 9(2)(a) |
| Sharing inside the app with people you choose | Relevant data according to your sharing settings | For health data Art. 6(3) explicit consent (sharing consent); otherwise Art. 5(2)(c) | Art. 9(2)(a); otherwise Art. 6(1)(b) |
| Verifying plans and gifts, applying feature locks | Purchase status, account identifier | Art. 5(2)(c) | Art. 6(1)(b) |
| Sign-in e-mails and essential account notices | E-mail address | Art. 5(2)(c) | Art. 6(1)(b) |
| In-app notifications and phone reminders | Notification data | Art. 5(2)(c) | Art. 6(1)(b) |
| Security and abuse prevention (rate limits, invite-code attempt limits, automatic security check, audit log) | Technical connection data, security records | Art. 5(2)(f): legitimate interest | Art. 6(1)(f) |
| Reviewing reported comments, blocking | Sharing data, reported comment | Art. 5(2)(f); where required Art. 5(2)(ç) | Art. 6(1)(f) |
| Answering support requests | Support correspondence | Art. 5(2)(c) and Art. 5(2)(f) | Art. 6(1)(b) and (f) |
| Proving your consents and actions concerning your rights | Consent and security records | Art. 5(2)(ç): legal obligation; Art. 5(2)(e): establishment, exercise or protection of a right | Art. 6(1)(c) and (f) |
| Meeting lawful requests of competent authorities and courts | Data subject to the request | Art. 5(2)(ç); for special-category data the statutory grounds in Art. 6(3) | Art. 6(1)(c); Art. 9(2)(f) |
| Optional: sending news and tips by e-mail (at most two a month) | E-mail address, name, language | Explicit consent (Art. 5(1)) and consent to commercial electronic messages under Turkish Law No. 6563 | Art. 6(1)(a) |
A7. Health data and your explicit consent
A7.1. Pregnancy, baby and cycle records are special-category personal data. We process them only on the basis of the explicit consent you give during app setup (text: Part C1). For your baby's records you give this consent as their parent/guardian.
A7.2. You can withdraw your consent at any time: Settings › Privacy & security › My consents. Withdrawal does not affect the lawfulness of processing before it. Without health consent, pregnancy and health records cannot be kept; the app takes you back to the consent screen and health features are switched off.
A7.3. What happens to your existing records when you withdraw: Your existing health records are not deleted; they are kept in your account until you delete them or your account. During this time no new records can be added, the reminders on your phone are turned off and your sharing stops: the people you invited cannot see your profiles (they are not removed from your circle). If you give consent again, your sharing reopens automatically. If you wish, you can delete them permanently in Settings › My data or by deleting your account.
A7.4. Your health and cycle data is not used for advertising, marketing, profiling or data mining, is not sold to third parties, and is not shared with anyone other than the people you invite.
A8. Who sees what
In Fama, people can see only profiles that the profile owner has invited them to and approved. Invitations are made with a one-time code valid for 7 days and completed with the owner's approval.
| Who | Pregnancy and Baby profile | Me profile |
|---|---|---|
| Profile owner | Everything | Everything |
| Parent and Family member | The areas the owner opens: Health (the owner can hide individual record types), Memories, Album, Record summary. In a Baby profile, can add logs if given care permission. Cannot see memories and photos marked "Only me". | — (these roles do not exist in the Me profile; see Partner/close person) |
| Doctor | Read-only: Health and Record summary. Cannot add, edit or react to anything. Cannot see memories or albums. | There is no Doctor role in the Me profile |
| Partner / close person (Me) | — | Only the dates of your period days (last 400 days), whether period tracking is on, and the period length on file. Flow intensity, spotting days, symptoms, mood, rituals and journal are not shared. |
| No one (other than the owner) | Mood, water and ritual records, journal | Mood, water, sleep, symptoms, rituals, journal, memories |
- Invitees cannot see that areas you keep closed exist.
- Health information on the profile (temperature threshold, birth weight, length and time, tummy-time goal, the "first pregnancy?" answer) is visible only to you and to active members who have the Health area; information belonging to a record type you hid from someone (e.g. the temperature threshold if you hid temperature) is not shown to that person. Other members see the profile's other basic information (e.g. name, type, sex, date of birth or due date, photo).
- Pending invitations: When someone enters an invite code, only the profile owner sees that account's own name and a partly hidden e-mail address (e.g. m***@gmail.com; for Apple-hidden addresses only "Email hidden with Apple") before approving. Masking is done on the server and the full e-mail is never sent to the owner; this information is no longer shown after approval.
- Invitees see your name and (if any) profile photo; comments show the commenter's name and photo.
- You can change sharing, end it or block a person at any time. When sharing ends, access is closed.
- When someone invites you, they decide what you see in their profile; data you are not allowed to see is not sent to your phone.
- The record summary (PDF) is created on your phone and not stored on the server; you decide whom to send it to.
A9. Who we share data with
We do not sell or rent your data, and we do not share it with advertising networks or data brokers. We transfer data only as follows:
a) Our service providers (processors) — only on our instructions, to provide the Service:
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Supabase (Supabase Pte. Ltd., Singapore; for technical support and operations Supabase, Inc., USA) | Database, authentication, file storage, server functions, server logs | All account, profile, health and content data in Fama | Data and backups: Amazon Web Services Frankfurt (EU) region; logs in the EU. Limited access from outside the EU may occur when support requires it. |
| Brevo (Sendinblue SAS, France) | Sending e-mail (sign-in code/link, e-mail change confirmation; announcements if you consented) | E-mail address, e-mail content | |
| Cloudflare, Inc. (USA) | Automatic security check (Turnstile) on e-mail sign-in requests; hosting the website | Browser environment signals, IP address | Global network |
| Namecheap (e-mail forwarding) and Google (Gmail) | Receiving and answering support and privacy e-mails | Support correspondence | USA |
b) Independent controllers:
- Apple and Google: when you use Sign in with Apple / Sign in with Google and when you purchase through the App Store / Google Play. To link a purchase to your account, only your random Fama account ID is attached to the purchase; your health data is not sent to these companies. Their processing is governed by their own privacy policies.
c) People you invite: the areas you choose, under the rules in Section A8.
d) Legal obligations: in response to lawful requests from competent public authorities or courts under applicable law, only to the extent requested and necessary.
We contractually require our service providers to protect your data at the level described in this policy or higher.
A10. International transfers
A10.1. Fama's servers are located in Germany (Frankfurt, EU). If you live in Türkiye, storing your data on these servers is a transfer abroad under KVKK. In addition, our providers' support teams (Singapore, USA) and Cloudflare (USA) may access limited data; Apple and Google use their own global infrastructure.
A10.2. Basis (KVKK Art. 9). As the Turkish Data Protection Board has not yet issued an adequacy decision for any country, we transfer data abroad under KVKK Art. 9(4) on the basis of the standard contract announced by the Board, and we notify the Turkish Data Protection Authority of the standard contract within 5 business days of signing.
A10.3. For users in the EU/EEA: Your data is stored within the EU (Germany). Transfers outside the EU (Singapore, USA, Türkiye) rely on European Commission adequacy decisions or Standard Contractual Clauses (SCCs).
A10.4. You can ask us which safeguard is used and for a copy of the contract.
A11. Retention and deletion
We keep your data as long as needed to provide the Service. When you delete a record, a profile or your account, the following periods apply:
| Data | How long it is kept |
|---|---|
| Account, profiles, health, care and cycle records, memories, journal, comments | Until you delete them or your account. When an account is deleted, it is deleted from the database immediately and in cascade. |
| Photos (memory, album, ultrasound, profile photos) | On account deletion, removed from storage in the same operation. When a single profile is deleted or an ownership transfer is declined, removed by a clean-up job that runs once a day. |
| Database backups | Deleted data is also removed from backups within at most 7 days as backups roll over automatically. Photo files are not included in database backups. |
| Ended sharing | Access ends immediately; the "sharing ended" notice is shown to the invitee for 3 days. The membership row remains until the profile is deleted. |
| Invite codes | A code is valid for 7 days; the code itself is not stored, only an irreversible hash. The invitation row remains until the profile is deleted. |
| Failed invite-code attempts, rate-limit counters | 1 day |
| Read in-app notifications | 90 days (unread ones until the related profile or account is deleted) |
| Reminder log on your phone | At most 14 days / 60 entries on your phone; not sent to the server; deleted on sign-out and account deletion |
| Ownership transfer offer | 30 days; if not accepted, the profile and its photos are deleted. In a transfer, your journal notes and the memories the recipient could not see are not transferred: they are first moved to your Me profile and deleted, with their photos, together with your account (see Terms of Use 8.8). |
| Subscription status | Until the account is deleted. Your purchase records are kept by Apple and Google under their own policies. |
| Gift records | Until the gift recipient's account is deleted; if the giver deletes their account, their identity is removed from the record. |
| Consent records (given and withdrawn) | Until the account is deleted. |
| Audit log (changes to sharing permissions, data downloads, account deletion) | 3 years — These records contain no health data; after account deletion they remain only with your random account ID. |
| Reported comments | Until review is completed and for as long as needed for a possible dispute, at most 6 months. |
| Server logs (IP etc.) | For our server provider's log retention period, at most 7 days. |
| Support correspondence | 2 years after the request is resolved. |
| Legal obligations | Data we are legally required to keep, for the period set by the relevant law and only for that purpose. |
Under our personal data retention and destruction policy, we periodically (at least every 6 months) delete, destroy or anonymise data whose processing conditions no longer apply. We complete deletion requests within 30 days at the latest.
A12. Security
Our main technical and organisational measures to protect your data:
- Access rules in the database: Row-level security (RLS) is enabled on every table, with separate rules for reading, inserting, updating and deleting. Who can see what (owner, parent, family, read-only doctor, person whose sharing ended, stranger) is checked by automated tests. The doctor's read-only status is enforced at database level.
- Encryption: All connections between the app and the server are encrypted with TLS; on the server, data and backups are stored on disks encrypted with AES-256 by our provider.
- Photos: Kept in a private (non-public) storage bucket; to display them in the app, signed links valid for only a few minutes and never shown to the user are generated, and the permission to see them is checked again on each request. They are re-encoded before upload, removing metadata including location.
- Keys: The server's administrative key is not in the app; it is used only in server functions. Your session tokens are kept in your phone's secure storage (iOS Keychain / Android Keystore).
- Against abuse: Invite codes are stored only as hashes; there are per-person limits on wrong code attempts, photo links, purchase verification and account deletion requests; an automatic security check runs on e-mail sign-in.
- On your phone: Optional app lock (Face ID / fingerprint / phone passcode), blurring content in the app switcher, and hiding notification content on the lock screen (on by default).
- No health data in logs: Health data, notes, photos and names are not written to error logs, notification texts, e-mails or log lines.
- Audit log: Changes to sharing permissions, data downloads and account deletions are recorded.
- Purchases: Verified by asking Apple's and Google's servers, not by trusting what the app says.
To be clear: Your data is not end-to-end encrypted; on the server side it can be decrypted so that the Service can work. Administrative access is limited to the smallest number of authorised people, protected by two-step verification, and health data is looked at only at your request or where legally required.
No system is completely secure. If a data breach affecting your data occurs, we will notify the competent authority and affected persons within the periods required by law (under KVKK, the Board within 72 hours).
A13. Children's data
- Fama is for people aged 13 or over; children under 13 cannot open an account. If you are under 18, you use Fama with your parent's or guardian's permission, and their approval is also needed for the explicit consent you give for your health data. If we learn that someone under 13 has opened an account, we delete it.
- Information in a Baby/child profile is about a child and is entered by the child's parent or guardian. You give explicit consent to the processing of the child's health data as parent/guardian, and you exercise the child's rights on their behalf.
- We share a child's data only with the people the parent chooses; we never use it for advertising or profiling.
- If a Baby profile has more than one parent, the profile owner decides who sees what; when deleting their account, the profile owner can transfer the profile to the person with the Parent role; in that case the owner's journal notes and the memories the recipient could not see are not transferred and are deleted with the owner's account (see Terms of Use 8.8).
A14. Advertising, tracking and analytics
- Fama has no advertising; no advertising SDK and no usage-analytics SDK is used.
- We do not track you across other companies' apps and websites; therefore Apple's App Tracking Transparency (ATT) permission is not requested and no advertising identifier is collected.
- We do not sell your data and do not make advertising-related transfers that could count as a "sale" or "sharing".
- If we add usage statistics that do not directly identify you in the future, we will first update this policy and enable it only if you consent; health data will not be used for this purpose.
A15. Notifications and e-mails
- Reminders are scheduled on your phone (appointments, water, kicks, medicines, vaccines, period, rituals etc.). Their content is not sent to the server.
- Lock-screen content is hidden by default. You can change this under Settings › Privacy & security.
- In-app notification inbox: Activity in your circle (e.g. a new care log, comment, heart, task, accepted invitation) is written to your notification inbox stored on the server and appears when you open the app. Read items are deleted after 90 days. If "Get notifications from shared profiles" is off, no notifications are written from other people's profiles. A notification about a note on a record goes only to people who can see that record (the relevant area is open and that record type is not hidden from them). When your sharing of a profile ends, that profile's notifications disappear from your inbox; only the "sharing ended" and "profile transferred to you" notices remain visible.
- Push notifications: Not currently used. When added, names and content will not appear on the lock screen by default (e.g. "There's an update from your family").
- E-mails: Sign-in codes and essential account e-mails are sent. News and tips e-mails are sent only if you consent (at most two a month), and you can turn them off at any time via the link in each e-mail or in settings. E-mails contain no health data.
A16. Your rights and how to exercise them
Under KVKK Article 11, by applying to the controller you have the right to: (a) learn whether your personal data is processed, (b) request information if it has been processed, (c) learn the purpose of processing and whether data is used in line with it, (ç) know the third parties to whom data is transferred in Türkiye or abroad, (d) request correction if data is incomplete or inaccurate, (e) request deletion or destruction under the conditions of KVKK Art. 7, (f) request that the operations under (d) and (e) be notified to third parties to whom data was transferred, (g) object to a result against you arising from analysis exclusively by automated systems, (ğ) claim compensation if you suffer damage due to unlawful processing.
If you live in the EU/EEA, under the GDPR you additionally have the rights of access, rectification, erasure, restriction of processing, data portability, objection to processing based on legitimate interest, and to withdraw consent at any time.
What you can do right away in the app:
- Access and portability: Settings › My data › Download all my logs (PDF or CSV). The file is prepared on your phone and covers your account, consents, the details of profiles you own, your logs (frequent logs as daily totals), appointments, and vaccine, growth, teeth, firsts, period and ritual records. Your memories, journal, album and photos are always available in the app, and you can save photos to your phone one by one. For a copy of all your data, including these, simply write to privacy@famastudio.app; we will respond free of charge within 30 days at the latest. Profiles others have shared with you are not included, because they belong to those people.
- Rectification: from the profile and logging screens.
- Deletion: individual records, record types, profiles, or Settings › Delete my account. Also at famastudio.app/delete-account.
- Withdrawing consent: Settings › Privacy & security › My consents.
- Managing sharing: Profile › My family / Who sees what.
Requests: For other requests, send your application from the e-mail address registered in Fama to the address in A20. Include your name, your request and contact details. We may ask for additional information to verify your identity. We complete your request free of charge within 30 days at the latest; if the operation entails an additional cost, the fee schedule set by the Board may apply.
Complaints: If your application is rejected, you find the answer insufficient or no answer is given in time, you may lodge a complaint with the Turkish Personal Data Protection Board within 30 days of learning of the answer and in any case within 60 days of the application date. If you live in the EU, you have the right to complain to the data protection authority of your country of residence.
A18. Changes to this policy
We may update this policy because of new features, new service providers or changes in law. We will announce material changes in the app in advance; if new processing based on explicit consent is added, we will ask for your consent again. We do not use data for purposes other than those for which it was collected without your new consent. The current text is always at famastudio.app/privacy; the version date is at the top.
A19. Language
This policy is prepared in Turkish and English. In case of any discrepancy, the Turkish text prevails.
A20. Contact
Controller: Egem Sarrafoğlu (developer of Fama)
For any privacy question: privacy@famastudio.app · In the app: Settings › Help & support › Write to us