Privacy Policy

Version 2026-10-31. It takes effect on the day it is published on this page.

1. Who we are

Sheina AI is operated by PALATNIKS LTD ("we"), which is the controller of the database for the information described here.

Privacy contact: hello@sheina.ai

You are not required by law to give us any information. An account is needed to use the app (section 2). Everything else in the journal is recorded only if you choose to record it. If you do not provide something, the feature that depends on it will not work. Usage analytics (section 7) are not required by law; they are part of how the app works, and you can ask us to stop them.

2. Your account

An account is required to use the app. There is no anonymous mode. You sign in one of three ways:

• Apple (Sign in with Apple), including "Hide My Email". The relay address Apple issues is stored as-is and works as an ordinary address.
• Google (Google Sign-In).
• An emailed sign-in link (magic link), with no password. The link itself is a credential: whoever holds it can sign in.

We store your email address, first name, parent gender (Hebrew needs it to address you correctly), interface language, a user id (Firebase UID), the identifiers of the sign-in service you used, when the account was created, which versions of the Terms of Use and this policy you accepted and when, and the choices you made in the app's privacy settings.

We do not collect a phone number, a postal address or a parent's date of birth.

3. Your baby's details

Information you enter that describes your child:

• Name, date of birth, sex
• Gestational age at birth, for corrected-age calculations
• Birth weight and current weight
• A profile photograph, if you choose to add one. It is stored with the baby's record in the cloud.
• Country — set when the baby's profile is created, from your device's region setting, and changeable at any time in Settings. It is stored as a field on the baby and is never re-sampled: changing your phone's region or travelling abroad does not change it. This is not location tracking — the app reads no GPS and requests no location permission. The country decides which medical emergency number is shown and whether the vaccine module appears at all — Sheina's vaccine schedule is the Israeli one, so outside Israel the vaccine screens and entries are not shown. Vaccine records already logged are kept.
• Feeding method and any notes you write about it
• Day/night boundaries and engine preferences

4. The journal

• Sleep — settling start, onset, night wakes and returns to sleep, waking, day/night classification, extensions, settling attempts that were stopped before the baby fell asleep, tiredness signs you reported and any free text you added, mood on waking, settling method, the sound played, and a lateness reason if you gave one.
• Feeding — type, nursing duration per side, volumes, descriptions of solids, notes.
• Pumping — side, duration, volume. This is information about the parent's body.
• Diapers — type, duration, notes.
• Developmental events — teething, growth spurts, milestones.
• Answers to short questions the app asks about your baby, including "not now" and "don't ask again".
• Free-text notes that you write.
• A correction history: when an entry is edited or deleted, the app keeps an append-only record of the change — what changed, when, and which parent made it — so both parents' phones stay in agreement.

5. Health information

Called out separately because it is information of special sensitivity:

• Body temperature readings
• Medications — name and dose — and medication reminders
• Vaccinations, including any side effects observed and notes
• Growth measurements — weight, height and head circumference

This is stored only if you choose to record it. We use it to show it to you and to the other parent in your family, in reports and charts, and in the app's features that depend on it. It is not part of usage analytics (section 7) and is not exposed by a public share link (section 11).

Sheina is not a medical device and does not diagnose. See the medical section of the Terms of Use.

6. How recommendations are produced, and the records we keep of them

Sheina's recommendations (for example, when to start settling for the next sleep) and insights are calculated by the app's own engine from what you record — your baby's age and the sleeps, feeds and events in the journal — and become more personal as data accumulates. The app currently has no AI chat, and your data is not sent to any external AI service. Earlier versions included a chat, in which a message you typed was sent through our server to an AI provider (OpenAI or Google Gemini) to produce a reply. That chat is no longer available.

Recommendation records. For each recommendation, the app stores a record in your baby's shared record. It is part of the journal, both parents can see it, and it contains no names and no free text:

• The recommendation — the recommended times, the type of sleep, and when it was calculated.
• The inputs and the learning state — the age and age group used, the wake time and window, the personal adjustment the engine has learned for your baby so far, the reasons the engine gives for the recommendation, and the version of the engine. The journal itself is not copied into it: the entries used are referred to by identifiers and technical fingerprints.
• When it was shown — on which screen, in a notification, or in an alert. This is recorded per parent and is linked to that parent's user id, together with whether the parent opened the explanation of the recommendation ("why this time?").
• Settling attempts that followed it, including attempts that were stopped before the baby fell asleep, and how long they lasted.
• The outcome — the sleep that actually happened, the link between that sleep and the recommendation, how far the actual times were from the recommended ones, and whether the recommendation had been seen.

Per-parent entries follow usage analytics. The parts that are about a particular parent — when the recommendation was shown to that parent, whether that parent opened the explanation, and the settling attempts that parent started — are recorded together with usage analytics (section 7): if a parent asked us to stop usage analytics, these entries are not recorded for that parent. The recommendation itself, its inputs, the learning state and the outcome are part of the baby's shared journal record, which both parents see.

We use these records to run the recommendations (the engine learns from earlier outcomes), to investigate a recommendation you report as wrong, and to measure and improve the engine's accuracy (section 8). Some of the details listed above are switched on from our servers, so not every record contains all of them.

7. Usage analytics

To understand how the app is used and to improve it, the app records usage analytics. They are recorded automatically for a parent who has been told about them: a new parent accepts this policy when signing up. A parent who already had an account is recorded only if they acknowledged, in the app, the one-time notice that the policy had been updated, which listed what is recorded and how to stop it (earlier versions of the app showed it); a parent who did not acknowledge it is not recorded. There is no switch for usage analytics in the app.

To stop usage analytics, write to us at hello@sheina.ai from the email address of your account. Providing this information is not required by law, and stopping it has no consequence: every feature of the app works the same.

What is recorded: which screen of the app was opened and which action was taken, from a fixed list (for example "opened the reports screen" or "started a sleep"); the time; a coarse result (succeeded, cancelled, failed); a coarse kind (for example feeding, diaper or sleep, or the sign-in method); a duration range; whether the action was yours or automatic; the app version and the platform (iOS or Android). Events are collected on the device and sent in batches to a separate database (Google Cloud Firestore, region me-west1, Israel), where they are stored under your user id. They are linked to your account.

What is never recorded: anything you type, your baby's name or identifier, amounts (millilitres, minutes, sides), any health screen or action (temperature, medication, vaccines, growth, milestones), promotional codes, product ids or prices, email addresses, links or sign-in codes, anything about the other parent, and device or advertising identifiers.

When we stop it at your request, recording stops and the usage events already collected are deleted, both those still waiting on your device and those in our database. From then on, the per-parent entries in the recommendation records (section 6) are not recorded for you either. Deleting your account deletes your usage events too.

Legal basis. We record usage analytics on the basis of your informed consent, which you give by accepting this policy when signing up, or by having acknowledged the update notice in the app. You can withdraw that consent at any time by asking us to stop usage analytics (write to us at hello@sheina.ai).

We use usage analytics only to understand how the app is used and to improve it — for example to find screens that confuse parents or flows that fail. They are not used for advertising or sold, and no one outside our service providers (section 16) receives them: they are not given to an analytics company, but stored in our own database at Google Firebase. Collection is also controlled from our servers, so at times nothing may be recorded even while the setting is on.

8. What we use information for

• Providing the service — your account, the journal, syncing between the parents of a family, reports, notifications, reminders and the recommendations.
• Product improvement and analysis — checking how accurate the recommendations were against what actually happened, finding errors in the calculation, and improving the engine and the app. For this we analyse the journal and the recommendation records (section 6) and, except for parents who turned them off, usage analytics (section 7). The analysis is done by us, on our systems. We do not sell the information or give it to others for their own purposes.
• Support — answering your questions and investigating the reports you send (section 15).
• Security and integrity — protecting accounts, preventing abuse, and keeping the two parents' records consistent.
• Billing — managing subscriptions and promotional codes (section 13).
• Service email (section 12).
• Legal obligations, and the establishment or defence of legal claims.

Aggregate statistics in the future. We may in the future produce statistics about babies' sleep in aggregate form — for example average sleep durations by age group. We will do so only after the result has been tested to ensure that no family, parent or baby can be identified from it, and we will update this policy before doing so. We do not produce or publish such statistics today.

9. Where your data is stored

The journal, the baby's details and the recommendation records are stored in Google Cloud Firestore and processed by Cloud Functions in region me-west1 — Israel. Usage analytics are stored in a separate Firestore database in the same region.

Some Google services we use run on Google's global infrastructure and may process data outside Israel: Firebase Authentication (your sign-in account), Firebase Crashlytics (crash reports) and Firebase Cloud Messaging (notifications). See section 21.

Your data is not kept on the device alone. Deleting the app removes the local copy only; the cloud copy remains until you delete your account. See section 18.

10. Sharing between the parents of a family

You can invite a second parent into your family. A parent who joins:

• can read, create, edit and delete every record for your baby — including records you created — and sees everything described in sections 3 to 6, including health information and the recommendation records;
• sees who performed each action, by first name ("who did what");
• sees a live indicator when the other parent has a sleep session open.

The recommendation records note which parent saw a recommendation and when, so a parent can see, through the shared record, that the other parent viewed it. This is not recorded for a parent who asked us to stop usage analytics (section 7).

If one parent leaves — leaves the family or deletes their account — the baby and the shared journal stay with the parent who remains, including the entries the departing parent made. When the departing parent deletes their account, their name is removed from those entries, which then read as "a parent"; their internal user id stays in the shared record as the technical marker of who created or changed an entry, without a name; and the records of which recommendations they saw are converted into counts with no identifier. Section 18 has the full details.

An invite link is a credential. Whoever holds it can join the family and see the whole record. Send it only to someone you mean to give full access.

You can send the invitation yourself (over WhatsApp, say) or ask us to email it. If you choose the second option:

• The address you enter is used solely to send that one invitation. We do not use it for mailing lists, for marketing, or for anything else.
• The email contains your first name, the link, the fallback code and the expiry. It does not contain your baby's name.
• We keep the address only while the invitation is pending, so you can see on your family screen where it was sent. It is deleted the moment the invitation is redeemed, revoked or expires, and it is never written to the audit trail.
• The address is visible only to you — the parent who created the invitation.
• We do not check whether the address already has a Sheina account, and we never report that either way.

On Android, the app reads the Google Play install referrer once, after installation. If the install came from an invitation link, the app takes the invitation code from it; if it came from a partner's link, the partner code (section 13A). If it holds neither, the app does nothing with it.

11. Public share links

You can create a link that shares the journal — with a grandparent, a nanny or a sleep consultant, for example.

• The link requires no sign-in, so it exposes only the minimum needed for everyday shared care: your baby's first name, their age (not their date of birth), sleep records (times, durations, settling and night wakings), feeds (type, amount, duration and side) and diapers. Records are shown with the first names only of the parents who logged them.
• What the link does not expose: temperature, medication name and dose, vaccinations and their side effects, growth measurements, pumping records, development entries, recommendation records, and any free text you have typed. The filtering happens on the server against an explicit list of fields: a field not on the list is not sent, and a new field added to the app in future stays private unless it is deliberately added to that list.
• You can revoke it at any time from the app.
• It is revoked automatically if its creator stops being a parent of that baby, or deletes their account.
• It does not expire on its own — it works until it is revoked.
• It is rate-limited, and marked so search engines do not index it.

You decide who receives the link, and you are responsible for that choice.

12. Email

Resend is used to deliver service-related email messages. Messages sent through it include:

• Sign-in links — sent to your account email address.
• Family invitations — only when you ask us to send an invitation by email to the address you provide. See section 10.
• Confirmation of a request from the professionals page — one email, to the address entered in the form at sheina.ai/pro, confirming we received the details. See section 13B.

The app also includes an optional "email tips and updates" preference, stored on your account, which you can turn off at any time. If we send optional tips or product updates in the future, they will be sent according to that preference, and you will be able to stop them through the app setting or an unsubscribe link.

Turning off optional tips and updates does not stop necessary service messages, such as sign-in links or family invitations you ask us to send.

For delivery, the provider receives the recipient's email address and the message content, and may retain technical delivery logs under its own policies. Verification and email-address-change messages sent by Firebase Authentication are handled by Google.

We do not sell email addresses and do not use them for advertising tracking.

13. Payments

• RevenueCat manages subscription state. It receives your user id (Firebase UID) and the purchase events from the store. It does not receive your name, your email or any baby data.
• Apple App Store and Google Play take the payment. We never see your payment details and have no access to them.
• We store your subscription status, plan tier and trial end date, the subscription events we receive, and the promotional codes you redeemed.
• From the subscription events we also keep the transaction details as RevenueCat passes them on: the store's transaction id, the amount paid and its currency, the estimated tax and store commission, the renewal number, the offer code if any, and the country. None of this includes payment details.

13A. Partners, influencers and offer codes

Some offer codes, and the links at sheina.ai/r/…, belong to partners — for example influencers, sleep consultants or professionals — who may receive a reward from us for families that came through them.

• What we record. When you redeem a partner's code, enter or buy with a partner's store offer code, or (on Android) install the app from a partner's link, we record on your account and family which partner, which code, how and when. Two parents of one family count as one family.
• Why. To know who referred you and to calculate the partner's reward. For this we link the record to the family's subscription transactions (section 13): trial, subscription, renewal, cancellation or refund, the time, the amount and the currency.
• What the partner gets. Nothing personal about you or your baby is passed to the partner: no name, no email, no identifier and no journal data. If we share figures with a partner, they are aggregates only — for example, how many new subscribers came through them.
• A partner's personal link. On the link page we count visits, taps on the store buttons and copies of the code: the time, the code and the device type only (iPhone, Android or other), as a daily count. We do not store your IP address (it is used only for rate limiting, in hashed form, and never stored with the count), a device identifier or cookies. We never read your clipboard and do not use device fingerprinting; the code is copied only when you tap the button.
• iPhone and Android. On Android, the Google Play link carries the partner code in Google Play's install referrer, and the app sends it to our server once after sign-up (section 10). iPhone has nothing equivalent, so there the attribution happens only when you enter the code in the app.
• No third parties. We do not use third-party attribution or advertising services, do not share this information with ad networks, and do not link it with information from other companies' apps or websites.
• How long. The attribution record is kept while the account exists. When the account is deleted, the attribution (which partner and when) is deleted. Transactions on which a reward was calculated are kept without any link to the account — the amount, time, the store's transaction id and the partner — as a financial record (section 18).

13B. Requests from professionals

Professionals can leave their details at sheina.ai/pro to get to know and try Sheina AI, receive explanatory materials, explore a professional collaboration (including joining the partner network) or hear about taking part in our podcast. This section is about the details of people who contact us there or are partners, not about parents. The controller is PALATNIKS LTD (section 1).

• What we keep. Full name, profession, email address and, if you choose to give them, phone and workplace. Also: how you chose to be in touch (getting to know and trying the app, explanatory materials, a professional collaboration, the podcast); if you arrived through a campaign link, the source tag in that link (for example utm_source=faceforward2026); whether the confirmation email was sent; when you applied and the policy version shown to you, the status of the application (pending, approved or declined) and our internal notes about it. If approved: your personal code and link, the partnership terms, and aggregate referral figures (section 13A).
• Do you have to? You are not legally required to give these details. Without name, profession and email we cannot review the application; phone and workplace are optional.
• Why. To handle your request and contact you according to your choices, to review a collaboration request and, if approved, run the partnership. The source tag is used to count requests per campaign, in aggregate. The form shows a short notice of what the details are for and a link to this policy; the basis is your consent, given by sending the form. You can withdraw it at any time by contacting us; we will then stop handling the application or end the partnership.
• IP address. Your IP address is not stored with the application. To rate-limit sign-ups a hashed value of it is kept for three days at most. As with any request to our servers, it may appear in technical server logs kept for about 30 days (section 17).
• Protection from automated sign-ups. When the check is on, your browser contacts Cloudflare Turnstile, which looks at technical signals of the browser and connection (including the IP address) to confirm the form was sent by a person. Nothing from the form is sent to Cloudflare, and we do not store the result.
• Public display. Your name is not shown on your personal link page or anywhere public unless you agree.
• Email updates. We do not send marketing email to people who contact us through this page. We only send messages about the application or the partnership itself (such as the confirmation email), which are not marketing. If we ever want to send updates or content, we will ask for separate, explicit consent.
• Who sees it and where it is kept. The Sheina AI team only, through a secured admin console; every look at your details is logged. The details are stored in Google Cloud Firestore in region me-west1 (Israel), like the rest of our database (sections 9 and 16). We do not sell them or share them with third parties for advertising.
• Rewards. If a monetary reward is agreed, the details needed for payment and invoicing will be requested separately, and payment records are kept as the law requires.
• Your rights and deletion. You can see, correct or ask us to delete your details at hello@sheina.ai; we will handle it within 30 days (section 19).
• How long. Details are kept while the application is under review or the partnership is active. A declined application is deleted automatically 24 months after it was declined (or earlier, on request). When a partnership ends, details no longer needed — such as phone, workplace, profession, request types, source and notes — are deleted 24 months after it ended. Information needed for tax, bookkeeping, payments, resolving disputes or a legal obligation — including the name and email of a partner who received or accrued a reward — is kept for as long as it is needed for those purposes.

14. Notifications

If you allow notifications, we store a device token for each install. Delivery is through Apple APNs and Google FCM, including iOS Live Activities on the lock screen.

Note that notification text contains your baby's name and the other parent's first name — "Dana put Noam down", for example. That content passes through Apple's and Google's notification infrastructure.

Notifications scheduled locally on the device (engine alerts, some reminders) never reach a server.

15. Diagnostics and reports you send

• Firebase Crashlytics is active in released builds. If the app crashes, we receive technical information such as the error and stack trace, platform, device model, operating-system version and app version. We do not attach your name, email address, user id or journal content. Before a report leaves the device, the app removes identifiers and email addresses it recognises in the error text. Crashlytics attaches a technical installation identifier for grouping crashes. Crash reports are kept for 90 days.
• Server logs are kept in Google Cloud for about 30 days and are used for operation, security and troubleshooting. They are written without names or email addresses.
• If you send a bug report from the app, it includes the text you wrote, a description of the device and your user id, so we can answer you. Bug reports are kept for up to 90 days.
• If you send a sleep-calculation problem report, it includes your description together with the technical data needed to reproduce the recommendation: the relevant inputs of the recommendation engine, the result, app version, device and platform, language and time zone. It does not include the baby's name or photo, parent names, email addresses or access keys. These reports are kept for up to 90 days.

The app contains no advertising, and we do not sell personal information.

16. Service providers

We use these providers to run the service. They process information on our behalf for the purposes described here:

We do not use advertising networks, data brokers or third-party analytics services. We may disclose information if the law requires it or to protect rights and safety.

17. How long we keep information

Your account, your baby's record, the journal, the recommendation records and usage analytics are kept for as long as the account exists. We do not delete them automatically because time has passed or because your child has grown. You can delete individual entries in the app at any time, and the whole account as described in section 18.

Shorter periods: crash reports — 90 days; bug reports and sleep-calculation reports — up to 90 days; server logs — about 30 days; a family invitation is valid for 7 days, and the invitee's email address is kept only while the invitation is pending.

18. Deleting your account

You can delete your account in the app (Settings → Delete account) or by email (see the end of this section). The deletion is performed on our server.

In every case, deleting your account:

• permanently deletes your sign-in account;
• removes your name, email, gender, photo, sign-in provider identifiers and other identifying details from your record;
• deletes your usage analytics;
• deletes any research copy of journal events you recorded in earlier versions (section 23);
• revokes your open invitations and every share link you created, and deletes your devices' notification tokens;
• deletes, immediately, the bug reports and sleep-calculation reports you sent;
• deletes the partner attribution — which partner you met, and when (section 13A);
• removes the local data on the device you deleted from.

If another parent is in the family: the baby and the shared journal stay with them — including the entries you made and the recommendation records — and you are removed from the family. Your name is removed from the entries, which then read as "a parent"; your internal user id remains in the shared record only as the technical marker of who created or changed an entry, without a name; and the records of which recommendations you saw are converted into counts with no identifier. If you hold the family subscription, the app asks you to transfer it to the other parent first.

If you are the last parent: the baby's record is deleted together with everything in it — the journal, sleep history, health information, photo, recommendation records and correction history.

What may be kept, and why:

• A minimal account record without identifying details: your user id, subscription status and tier, the deletion date (day only), and which versions of the Terms, this policy and any research consent you accepted, and when. It lets historical actions read as "a parent", lets a late billing event be processed, and records which consent was given.
• Billing records. Subscription-event, promotional-code and grant records keep your user id, for billing, accounting and dispute purposes and as the law requires. Transactions on which a partner's reward was calculated are kept without your user id and without any link to your family. The customer record at RevenueCat (your user id and purchase history) is not deleted automatically when you delete your Sheina account. Apple and Google keep their own purchase records under their own policies.
• The invitation audit trail — who joined the family and when — stays for the parent who remains.
• Backups. Deleted data is removed from the live database immediately. It can remain in backups for up to 98 days and in point-in-time recovery for 7 days, after which it expires automatically — so it is fully gone within 105 days. Backups are used only to recover from a system-wide incident; we do not restore a deleted account from them.
• Server logs, for about 30 days (section 15).

Sign-in providers. Deleting your Sheina account does not delete your Apple or Google account. If you signed in with Apple, you can remove Sheina from the apps using your Apple ID in your iPhone's settings (Settings → your name → Sign-In & Security → Sign in with Apple). If you signed in with Google, the app tries to revoke its access to your Google account during deletion; you can also check this at myaccount.google.com, under third-party connections.

Deleting your account does not cancel an active subscription. Cancel it in your App Store or Google Play subscription settings, or billing continues.

Pausing instead of deleting. You can also deactivate the account temporarily in Settings. While deactivated, the account cannot be used; the data is kept and returns when you reactivate.

You can also write to hello@sheina.ai from the account's email address. We will act within 30 days. The same details appear on the Delete account page.

19. Your rights

Under the Israeli Privacy Protection Law, 1981, you may:

• access the information about you held in our database (most of it you can see in the app itself);
• ask us to correct or delete information that is not correct, not complete, not clear or not up to date;
• delete your account and its information, as described in section 18;
• withdraw your consent to usage analytics at any time by asking us to stop them (write to us at hello@sheina.ai) — the usage events already recorded are then deleted — and change any other choice you made in the app's privacy settings.

To make a request, write to hello@sheina.ai from the account's email address. We will answer within 30 days. If you believe we have not handled your request or your information properly, you may complain to the Privacy Protection Authority at the Israeli Ministry of Justice. If you live outside Israel, you may also have rights under the law where you live, including the right to complain to your local data-protection authority.

If you are one of two parents, deleting your account does not delete the other parent's account or the record that stays with them.

20. Security

• All communication between the app and our servers is encrypted in transit (TLS).
• Data is encrypted at rest by Google Cloud's infrastructure.
• Access to a baby's record is enforced on the server by security rules: only the parents of that family can read or write it.
• The app uses Firebase App Check (Apple App Attest and Google Play Integrity) to help confirm that requests come from the genuine app.
• We limit the identifying details written to server logs and crash reports.
• Access to production systems is limited to the people who operate the service.

These are measures, not a promise of outcome: no online system can be guaranteed absolutely secure.

21. Processing outside Israel

The main database is in Israel. Some of our providers process information outside Israel as well, including in the United States and in the European Union: Google (Firebase Authentication, Crashlytics, Cloud Messaging), Apple, RevenueCat, Resend and Netlify. They do so as our service providers, for the purposes in section 16.

22. Children

Sheina is for parents and carers, to record information about their own children. Information about the baby is entered by the parents. The app is not designed for children to operate, is not marketed to children, and we do not knowingly collect information directly from children.

By entering information about a child you confirm that you are their parent or legal guardian, or that you have that person's permission.

23. Research data from earlier versions

Between September and October 2026, some versions of the app asked parents for consent to keep a pseudonymised copy of the journal events they recorded, for research. We have stopped this collection, and current versions of the app no longer ask for this consent. What was collected (journal events without names, some of which included notes you had written) is kept apart from the journal, is not used for analysis, and is held while we decide whether to delete it. Pseudonymised means the information is not anonymous: it can still be linked to a family by someone who holds the key.

If you gave this consent, you can withdraw it at any time in Settings → Privacy & research. Withdrawing deletes the research events you recorded. Deleting your account deletes them too, and so does deleting the baby's record.

24. Changes to this policy

We update this policy from time to time. A material change will be brought to your attention in the app or by email, and where a change requires your consent, we will ask for it. The version and date appear at the top of this page.

25. The website and the download page

sheina.ai is hosted by Netlify. It has no ads, no cookies and no third-party analytics.

On the download page (sheina.ai/download), which our QR codes point to, we count visits to learn which source they came from: the time, the source named in the link (for example src=tipat_halav), the device type only (iPhone, Android or computer), and whether you were sent to a store automatically or by tapping. We do not store your IP address, your full browser identification, a device identifier or anything that identifies you, and visits cannot be linked to one another. In the same way, on sheina.ai/pro we count visits, taps on the download button and forms that were received, with only the source named in the link (for example utm_source=faceforward2026) — never anything typed into the form. Netlify, as the host, processes technical request data under its own policies.

Once you go to the App Store or Google Play, that store's privacy policy applies. The Google Play link includes the source name so that Google Play can report to us how many installs came from each source, in aggregate only.

Partners' link pages (sheina.ai/r/…) are described in section 13A.

26. Contact

Privacy questions and requests: hello@sheina.ai · PALATNIKS LTD