Privacy Policy
Effective Date: November 20, 2026
Svila.io ("we," "our," "us") is committed to protecting your privacy. This Privacy Policy explains what personal information we collect, how we use it, who we share it with, and your rights regarding your data.
1. Information We Collect
a) Account Information
When you create an account, we collect your email address. This is used to create your account, send you secure magic link login emails, and communicate account-related information.
b) Persona & Conversation Data
We store the AI personas you create (name, tone, mood, description, and related settings) and the conversation history between you and your personas. This data is necessary to provide the Service and is stored in our secure database.
c) Payment Information
We do not store your payment card or wallet details. Payments are processed by our third-party payment providers, which handle card and wallet data under their own PCI-compliant security policies. See section 3 for what they handle. We receive and store only non-sensitive transaction metadata (such as subscription status, product type, and transaction identifiers) necessary to manage your account.
d) Usage Data
We may collect basic usage information such as when you log in and how features are used. This helps us maintain and improve the Service. The only advertising measurement we use is the Meta Pixel, on our Readings pages and our love-interest story pages (/companions) only (see section 3, “Advertising measurement”). We also measure how fast our pages load and respond: Google Analytics receives the measurement, the kind of page (its address with any identifiers removed) and a short description of the page element involved — nothing you typed.
e) Guest Preview & IP Address
You can try a short preview conversation without creating an account. When you do, we store the messages exchanged in that preview together with your IP address.
The IP address is collected for one purpose: preventing abuse of the free preview. We limit the number of preview sessions that can be started from a single IP address in a day, and without the address that limit cannot be enforced. It is not used for advertising, profiling, or analytics, and it is not shared with third parties.
A preview session expires 24 hours after it starts. Expired sessions — including the stored messages and the IP address — are deleted automatically by a daily job, after a short grace period that exists so that a preview conversation can be carried over if you decide to create an account. If you create an account, the preview conversation is migrated to it and is then covered by section 5.
f) Safety and Moderation Records
Where a message or a generated reply is blocked by our safety controls, we record that the block occurred: the account (if any), the category, and the time. For a short period we also retain a fragment of the text involved, so that the decision can be reviewed or contested. After 30 days that text is replaced with a one-way hash and the readable content is destroyed; the record that the block happened is kept, because it is what allows us to identify repeated attempts.
Every message you send is checked automatically for signs that you may be thinking about suicide or self-harm (see our Safety page). When a message shows such signs, or signs of distress, we store a flag on that message in your conversation history, recording the level detected; the character's replies written while the conversation is in crisis mode are flagged too. Unlike the anonymous referral counts described on the Safety page, this flag is part of your conversation and so is linked to your account (or, in a guest preview, to that preview session). It is used only to keep the replies safe — so that the character stays out of roleplay and romance for the next few messages, the crisis information stays visible in the conversation, and message limits do not cut you off — and to keep crisis messages out of your companion's memory: a message flagged as a crisis, and the replies to it, are never turned into memories, recalled, summarised or included in recap emails. It is not used for advertising, profiling or analytics, it is not shared, and it is deleted together with the message it belongs to.
g) Ratings and Comments
If you rate a reading or a companion, we store the rating and any comment you write, not the conversation. We only show a comment publicly if you ticked the box to allow it, with the name you chose, and you can ask us to remove it at any time. You can also remove it yourself from your account page.
A companion story you try without an account can be rated with a thumbs up or down and up to two reasons chosen from a list; there is no comment box. That rating is stored with the story and deleted with it (see 1(i)).
h) Your Sign and Your Story (Readings)
If you choose to tell Mira your first name, a topic, someone's first name or your birthday (before your first reading, or on our horoscope pages, where you can also choose your star sign), we store it to personalise your readings and your horoscope. You can edit or clear it any time from “Your story” in the reading room's menu. Someone else's name is a first name only. A short note you give Mira is checked by our crisis-safety screen like any question, and is not kept if it suggests you may be in danger. Your birthday is never used to check your age. Your sign is also kept in a cookie on your device. It is all deleted with your account, and none of it is ever sent to analytics or advertising partners.
i) Companion Stories Without an Account
You can start a story with one of our companion characters without an account. We store the messages of that story — what you write, including anything you tell the character such as your name, and the character's replies — together with your IP address, the safety flags described in 1(f), and a one-word note of the kind of link that brought you (see section 4, svila_src). Each character's story is held in its own session, identified by a cookie that lasts 24 hours. Your name, if you give it, is kept only as part of that story's messages. If you create an account, the story's messages and their safety flags move to it and are then covered by section 5; the rating and the link note do not move. Otherwise the story is deleted automatically 7 days after it expires.
If you ask a character for something sexual, the story notes the first such request, and we add one to a daily count, kept by character and by the kind of link that brought you. The counts contain no text and nothing that identifies you; what you wrote stays only in the story.
j) Mira Cards
When you send a card, we store:
- your name as you sign the card, and the recipient's first name;
- the recipient's email address, if you send it by email, and a one-way hash of it;
- your note, and for a video message its title;
- the secret word, if you add one — only as a one-way hash, never the word itself;
- when it should be sent, and the recipient's time zone;
- a one-way hash of your IP address;
- whether you allow replies, and whether Mira may read your note aloud;
- when it was paid for, sent, opened and thanked, and, if you are signed in, your account.
We use this to deliver the card, to show you whether it has been opened, to let the recipient thank you, and to prevent abuse. The hashes of your IP address and of the recipient's address enforce our limits: 20 cards a day from one sender, 3 a day to one address, and the free-card limits. To keep the free card to one per person, we also keep a one-way hash of the verified email address it was given to, which remains if the account is deleted, and, for a free card sent without an account, a random device identifier in a cookie (see section 4). Before a card is made, your names, note and secret word are checked automatically: by our own lists, by an AI model through OpenRouter (see section 3) for the note and title, and by our crisis-safety screen.
The recipient. We email the recipient only the card you sent. The email carries your name, theirs and a link to the card; for a video message it also carries its title, your words and the code to play it. We never add the recipient to our mailing lists or use their address for marketing. They can block further cards from the card itself or from any card email; we then keep only a one-way hash of their address, so that no further card is sent to it, for as long as the block applies. When they open the card we record when, and show it to you; if they tap “Thank you”, we email you. If you allow replies, a reply from the recipient goes from their email address to yours, so each of you sees the other's address.
Read aloud. If the recipient presses play, the card's words — with your name and note only if you allowed Mira to read your note — are sent to ElevenLabs to make the audio, which we store privately and keep with the card.
Payments. A card is paid for through our card payment provider, as for other purchases (see section 3); we keep the payment record, not your card details.
k) Video Messages
Recording and storage. A video message is recorded in your browser, with its sound, or chosen from your device, and uploaded directly to our private storage with a still image taken from it. Only someone with the code from its email can watch it, through links that expire after two hours.
The automatic check. Before a video is sent, three still images from it — two taken in your browser and the still image stored with it — are checked automatically by an AI model, OpenAI's GPT-4.1 mini, through OpenRouter, for sexual content, anything sexual involving a minor, and graphic violence or threats. No sound, title or words are sent. We do not keep the two images taken in your browser. A video that does not pass is deleted and not sent; we keep only a count that a video was stopped, with nothing about it. If the check cannot be completed within a few seconds, the video is sent without it.
Your confirmation. Before sending you confirm that you are in the video, or that everyone in it has agreed to be in it. We record the time you confirmed.
The code. Each email carries a new code, and we store only a one-way hash of it. To stop codes being guessed, 5 wrong codes from one address pause attempts for 15 minutes, counted in memory against a one-way hash of the address; after 20 wrong codes the video locks until the sender sends a new code. Once the right code is entered, a cookie on that device keeps the video unlocked for 7 days.
Watching. Each time the video is played we record the time, and nothing about who watched it or from where.
Reports. If the recipient reports a video, we store the reason they chose and any words they add, the video is paused at once, and the report is emailed to our support team.
How long. The video and its still image are deleted 30 days after the video is first watched, 90 days after it was sent if it is never watched, or at once if the sender deletes them; a video that is never paid for is deleted after 24 hours. A reported video is kept until we have reviewed it. See section 5 for what stays with the card.
2. How We Use Your Information
- To create and manage your Svila.io account
- To authenticate you via secure magic link login
- To store your personas and conversation history so you can access them across sessions
- To process payments and manage your subscription, credits, and day pass status
- To generate AI responses to your messages (via our AI provider)
- To generate voice audio from AI responses (via ElevenLabs), only for accounts that already hold voice credits and turn voice on — voice credits are not on sale at the moment
- To send transactional emails related to your account (e.g. login links, billing notifications)
- To deliver the Mira Cards you send, and to let their recipients thank you or block further cards
- To detect and prevent abuse, fraud, or violations of our Terms of Service
3. Third-Party Service Providers
We use trusted third-party providers to operate Svila.io. These providers may process some of your data as necessary to deliver the Service. We list them by function so you can see exactly what each one handles.
Authentication and database
- Supabase — Authentication and secure database storage for your account, personas, and conversations, and private file storage for reading audio, the audio of cards read aloud and video messages.
Payment processing
- Our card payment provider — Card payments for subscriptions, day passes and one-off purchases such as readings and Mira Cards, including card details, billing and renewals. We never receive your full card number.
- Our cryptocurrency payment provider — Cryptocurrency payments.
We may add or change payment providers over time. Payment providers handle wallet and transaction data under their own privacy and security policies; Svila.io does not store payment card numbers or wallet credentials.
AI and voice
- Our AI language-model provider — The content of your messages is sent to the AI provider to generate responses. The provider processes this data under their own privacy policy.
- OpenRouter — Routes some automatic checks to AI models: the note and title on a Mira Card, to an OpenAI safety model, to check it is not abusive; and, for checking video frames, three still images from a video message to OpenAI’s GPT-4.1 mini. See section 1(j) and 1(k).
- ElevenLabs — Voice synthesis. Voice is not available to new accounts at the moment, because voice credits are not on sale. For an account that already holds voice credits and turns voice on, the text of AI responses is sent to ElevenLabs to generate audio; otherwise nothing is sent.
- Mira Cards read aloud — When the recipient of a card presses play, its words (with the sender's note only if they allowed it) are sent to ElevenLabs to make the audio, which we keep with the card.
- Readings voice — When you press play on a reading, its text (never your own words) is sent to ElevenLabs to make the audio, which we keep so the same reading is not made twice. Voice messages are converted to text and the audio is deleted immediately: it is sent to ElevenLabs once to be written down, never stored by us, and only the text is kept, as your question.
Hosting and infrastructure
- Vercel — Cloud hosting for the Svila.io web application.
- Google Analytics — How the site is used, and how fast its pages load and respond (see section 1(d)), subject to your choice in the cookie banner.
- Sentry — Error monitoring, with data stored in the United States. When something breaks, Sentry receives a technical report: the type of error, where in our code it happened, which page or route was involved, your browser and device type, and a random account identifier (not your name or email). We strip message text, conversation content, request bodies, cookies and sign-in tokens from every report before it leaves our servers or your browser.
Advertising measurement
- Meta Platforms (Pixel and Conversions API) — Used on our Readings pages (palm, dreams, tarot and the daily horoscope) and our love-interest story pages (/companions), and nowhere else on Svila.io, to measure our ads on Facebook and Instagram. On the Readings pages, Meta receives page views, the type of reading you started or completed (palm, dream or tarot — never what you wrote, your reading or your palm photo) and purchases made from Readings. On the love-interest story pages, Meta receives page views, which character's page you viewed, that a story was started and that the paywall was shown, and purchases made there — never what anyone writes in a story. For a purchase, Meta receives the amount, the plan, and a hashed (scrambled, one-way) copy of your email address so Meta can match the purchase to its ad. Meta sets its own cookies for this. In the UK and the EEA it only runs if you accept cookies; elsewhere you can decline in the cookie banner or, later, through Cookie Settings at the bottom of the page, and it stops.
- We use Resend, a transactional email provider, to send account-related emails such as login links and purchase confirmations, and the Mira Cards you send: Resend receives the recipient’s address and the card’s email.
- Emails you ask for. If you ask for them — for example with “Email me tomorrow's card” under a daily card, or by ticking a box — we send you occasional emails: your card for the day (most mornings around 8 am your time, at most six a week if you asked for it that way, otherwise at most four), your horoscope if you have told us your sign, a short Sunday note about the week's cards when you have drawn at least two, and similar reminders. When you ask with just your email address, we first send one confirmation email, and nothing else starts until you tap its link (if you don't, we send one reminder a day later, then stop, and delete the request within three days). Confirming makes a free account with your email address, so your cards are saved, and moves the readings you had made on that device onto it. A morning email may greet you by the first name you gave Mira, and may include one short line written by our AI provider from your story's topic, the first names in it and your last card — never the note you wrote, and never after a reading flagged by our crisis-safety screen. We send fewer emails if you stop opening them, and stop altogether if you don't come back. We only record whether you followed a link in an email (no open tracking), and if an email bounces or is reported as spam we stop sending. Every email has a one-click unsubscribe link that works without signing in, and you can turn these emails off in your account at any time.
- A checkout you didn't finish. If you have asked for emails from us and leave a payment page without paying, we may send you one email about it an hour or so after it closes, with a link back to it — at most one in any seven days, with no discount and nothing more after it.
Payment-method interest list
Before card payments were available, you could ask us to notify you when they launched. If you did, we recorded:
- the email address you enter;
- optionally, which plan or product you were looking at and where on the site you asked from;
- your account identifier, only if you were signed in at the time.
We use this solely to email you once to say card payments are available. It is not used for marketing, is not sold or shared, and it did not create an account. We keep it until we have sent that email, or until you ask us to remove it — whichever comes first. To have your address removed at any time, email support@svila.io and we will delete it.
We do not sell, rent, or trade your personal information to third parties for marketing purposes.
4. Cookies & Sessions
Svila.io uses cookies and browser storage to maintain your login session. These are essential for the Service to function and are not used for advertising. By using Svila.io, you consent to this use of cookies.
We also use analytics cookies to understand how the site is used and, on our Readings pages and our love-interest story pages (/companions) only, Meta's advertising cookies to measure our ads (see section 3). You can decline these in the cookie banner, or change your choice at any time through Cookie Settings at the bottom of the page. In the UK and the EEA the advertising cookies are only set after you accept.
Some of the cookies we set ourselves:
svila_consent— your choice in the cookie banner. 1 year.ageConfirmed— that you confirmed you are 18 or over, so we do not ask again. 1 year. For an account, the confirmation is also kept with the account.readings_terms— that you accepted the Readings terms, and which version. 1 year. For an account, it is also kept with the account.svila_src— one word for the kind of link that first brought you (for example “google” or “direct”), used in our counts and attached to a purchase's record. 90 days.svila_ft— that your first visit came from a Mira Card. 90 days.wsession,wgsessionandwrom_<character>— identify a guest preview or a companion story without an account (see 1(e) and 1(i)). 24 hours.svila_card_device— a random identifier, so a free Mira Card sent without an account is limited to one per device every 30 days. 1 year.svila_cv_…— a signed note that a video message was unlocked with its code on this device, so the code is not asked for again. 7 days.
5. Data Retention
We retain your account data, personas, and conversation history for as long as your account is active. If you request account deletion, we will remove your data within 30 days. Payment records may be retained for longer where required by law or for financial compliance purposes.
Seven categories have their own periods:
- Guest preview sessions (messages and IP address) — deleted automatically once the session has expired and a short migration grace period has passed. See section 1(e).
- Companion stories without an account (messages, IP address, rating) — deleted automatically 7 days after the 24-hour session expires, unless you create an account. See section 1(i).
- Readings made without an account (palm, dream and tarot readings, and the questions and dreams you wrote, and the sign or birthday you told us) — kept for up to 7 days and then deleted, unless you sign in, in which case they move to your account. A reading our crisis-safety screen flagged is kept for up to 30 days, so that it can be reviewed, and then deleted the same way.
- Comments on ratings — cleared after 24 months, unless you allowed the comment to be shown and we are showing it; the rating itself is kept. A rating made without an account is deleted with the readings made without an account. See section 1(g).
- Readable text in safety records — replaced with a one-way hash after 30 days. The record of the event is retained; the text is not. See section 1(f).
- Mira Cards — an unpaid card is deleted after 48 hours. The recipient's email address is deleted 90 days after the card is sent, or 90 days after it was made if it never went; a one-way hash of it is kept. A card stops opening 365 days after it is sent, and 30 days after that it is deleted: the names, your note, the hashes of the secret word, of the recipient's address and of your IP address, and its times, with its video, if any is left, and the record of when it was watched. Its read-aloud audio is deleted once it has gone unused for 60 days. A free card leaves only one-way hashes of the address it was given to and of the address it went to, so that each still has its one free card. Until then, if you delete your account, the cards you sent are unlinked from it rather than deleted; to have a card deleted sooner, email support@svila.io. A block on an address is kept, as a hash, for as long as it applies.
- Video messages — the video and its still image are deleted 30 days after the video is first watched, or 90 days after it was sent if it is never watched, or at once if the sender deletes them; a video that was never paid for is deleted after 24 hours. A reported video is kept until we have reviewed it. The title and words, the time of your confirmation, the times it was watched and any report stay with the card's record, as above. See section 1(k).
6. Security
We implement industry-standard security measures including encrypted connections (HTTPS), row-level database security, and secure authentication. However, no system is completely secure, and we cannot guarantee absolute security of your data.
7. Children's Privacy
Svila.io is strictly for users aged 18 and over. We do not knowingly collect personal information from anyone under 18. If we become aware that a minor has created an account, we will terminate it and delete their data immediately.
8. Your Rights
Depending on your location, you may have rights under applicable data protection laws (such as GDPR or CCPA) including the right to:
- Access the personal data we hold about you
- Request correction of inaccurate data
- Request deletion of your account and associated data
- Object to or restrict certain types of processing
- Withdraw consent where processing is based on consent
To exercise any of these rights, please contact us at support@svila.io.
9. Changes to This Policy
We may update this Privacy Policy from time to time. When we make material changes, we will update the effective date at the top of this page. We encourage you to review this page periodically. Continued use of the Service after changes are posted constitutes acceptance of the updated policy.
10. Contact
For privacy-related questions, requests, or concerns, contact us at support@svila.io.
Updated 2026-11-18: video messages (section 1(k)) — how a video is stored, the automatic check of three still images through OpenRouter, your confirmation, the code and the unlock cookie, the record of each watch, reports, and deletion 30 days after it is first watched. Updated 2026-11-20: the Meta Pixel and Conversions API extended to the love-interest story pages, for advertising measurement; nothing anyone writes is sent. Updated 2026-11-18: Mira Cards (section 1(j)) — what we collect when you send a card, what the recipient receives, blocking, read-aloud, and how long it is kept; companion stories without an account (section 1(i)), including their ratings and the count of sexual requests; page-speed measurement (section 1(d)); the cookies we set, by name (section 4); providers named: OpenRouter, Resend and Google Analytics (section 3); retention periods (section 5). Updated 2026-10-27: emails you ask for (the Email section), including the morning card email and the Sunday note, the confirmation email before they start, and one email about a checkout you didn't finish. Updated 2026-10-26: your sign and story (section 1(h)), including what you may tell Mira before a first reading; the daily horoscope pages added to the Readings pages that use the Meta Pixel. Updated 2026-10-08: Meta Pixel and Conversions API added for advertising measurement on Readings pages. Updated 2026-09-16: Sentry added as our error-monitoring provider. Updated 2026-05-11: third-party-providers list restructured by function and updated to include additional payment providers.