Privacy Policy

Last updated: 2 October 2026

This policy explains what Storias collects, what we do with it, who we send it to, and how long we keep it. It covers the Storias apps for iPhone, iPad and Mac, the web app at edit.storiasai.com, and this website (together, the "Service"). It sits alongside our Terms of Service.

It is written in plain words on purpose. If a line here is unclear, or turns out not to match what the product does, tell us and we will fix it.

1. Who we are

Storias makes an AI video director. You record once, and Storias builds the whole video: captions, pictures, motion and pacing. We are the controller of the personal data described here, which means we decide what is collected and why.

Contact for anything in this policy: privacy@bearishfh.com.

2. What we collect

Your account

• How you sign in. An email address and a password, or a one-time email link, or Sign in with Apple or Google. With Apple or Google we receive the identifier they give us and, if you allow it, your name and email. Apple may give a relay address instead of your real one, and that is fine with us.
• Your profile. A display name, and a role if you pick one. Nothing else.
• Connected assistants. Which assistants you have connected, when you connected each one and when it last used the connection (section 4A).
• Where you came from. When you create an account, the first campaign that brought you, kept on the account: the audience of the landing page (for example real estate), the campaign tags (utm source, medium, campaign, content and term) and the ad platform's click id (section 12).
• Partner program. If you apply to be a partner: your name, links, audience description, how you will promote Storias, country and payout email. If you join through a partner: which partner referred you, how and when (section 5A).
• A temporary account. If you try Storias before you pay: an account with no name and no password, the email address you type, where you came from and your answer about ad measurement (section 5B).

What you make

• Your recording. The video and audio you upload or record in the app. For a film, this is the only file you give us. Everything below, apart from Look Lab references and templates, is derived from it.
• Your transcript. The words in your recording, with timings.
• The footage analysis. A written description of what is on screen and when.
• The film's plan. The shot-by-shot plan written for your film. It contains your captions word for word, so it holds the same words your transcript does.
• Pictures. Images generated for your film, and stock or archive pictures and clips chosen for it.
• The finished film. The rendered video.
• Project details. Title, template, aspect, length, status, and the dates it started and finished.
• Search terms. When the film needs a real photograph or a piece of footage, we record which library was searched, with what words, and which asset was used.
• Look Lab references and templates. The videos and pictures a company uploads to build a template in the Look Lab (its references), the measurements and readings made of them, and the templates built from them.

Payments and credits

• Your plan, your credit balance, and one line for every credit spent or granted.
• Subscription and entitlement status from Apple, Stripe and RevenueCat, and the identifiers those services use for you.
• We never see your card. Card numbers go to Apple or to Stripe and never reach us.

Technical records

• Render records. Which step a film reached, how long it took, and why it failed if it did.
• Abuse prevention. We count requests per account and per network address so one person cannot flood the service. The address is never stored in a readable form: it is grouped and hashed first, and only the hash is kept. We keep a one-way hash of your email address for the same reason, so that trying Storias before you pay cannot be taken over and over, so that the first film you can make before you pay is given only once per person (section 5B) and, if you join through a partner, so that the welcome bonus is given only once (section 5A).
• Server logs. Ordinary operational logs from our hosting providers, kept for a short period.
• How the website and the web app are used. The pages you open, the links to the web app that you click, the site that sent you, the campaign tags, ad click ids and partner code in the address, your device type and language, and the steps you reach in the web app, including before you have an account (section 12).

We do not collect your contacts, your location, your device's advertising identifier, or health data. The iPhone, iPad and Mac apps contain no analytics and no tracking SDK at all — not ours, not anyone's.

3. What we use it for

• To make your film. Everything under "What you make" exists for this one purpose, apart from Look Lab references and templates, which exist to build a company's templates and to make its films with them.
• To run your account. Signing you in, your project library, your credits, your plan.
• To take payment and to give you what you paid for.
• To keep the Service working and safe. Finding failures, stopping abuse, preventing fraud.
• To improve Storias. We analyse the templates companies build, the references they upload to build them and how those templates perform — and nothing else of what you make — to improve our template engine and the Look Lab: for example, which building blocks templates need and how to read references better. We do this only in aggregated or de-identified form (section 6A of the Terms of Service), and a company admin can turn it off at any time in Settings ("Help improve Storias"). We never use templates, references, brand assets or films to train AI models, ours or anyone else's.
• To measure our advertising. To learn which of our ads bring people who actually use Storias and, only if you accept our cookie banner, to tell Meta, TikTok and Google when you sign up, finish your first film or buy, so that we can measure and improve our advertising (section 12).
• To run the partner program. To review applications, show a partner's name to the people they invite, give the welcome bonus, count referrals and pay commissions (section 5A).
• To let you try Storias before you pay. To make your film, send you the email about it and give a trial only once per person (section 5B).
• To obey the law where we have to.

We do not use your recordings, transcripts or films to train any model of our own. We do not sell your personal data. We share nothing for advertising except what section 12 describes, and only if you accept our cookie banner. We do not build a profile of you, and we do not make automated decisions that have a legal or similarly significant effect on you.

4. How a film is made, and who sees your recording

This is the part most policies leave out. Here is what actually happens to your recording, and what leaves our systems. What we do not set out is which supplier performs which individual step of making a film — that is how the product is built, and it is ours to keep. Everything any of them may receive is listed below and in section 5.

You upload

Your recording goes from your device straight into private storage. It is scoped to your account: no other customer can read it, and the database enforces that rule on every request.

Your recording leaves our systems to be understood

Turning one recording into a finished film takes several kinds of work: the speech has to be transcribed, the footage has to be watched and described shot by shot, and the film has to be planned — its shape, its headlines, its captions, which pictures belong where and when to cut to your own footage.

To do that, your whole video file, its audio, and the words in it are sent to our AI service providers. Depending on the film you asked for, any one piece of that work may be carried out by one, by several, or by all of them, and which of them does which piece changes as we improve the product. They are named in section 5. We would rather say this plainly than bury it: there is no way to build a film of this quality without your footage leaving our systems.

Pictures are made, or found

Where the plan calls for a generated picture, a short text description of that picture — a few words, never your recording — is sent to a provider that draws it. Where the plan calls for real footage or a real photograph, a search term of a few words is sent to stock and archive libraries: Pexels, Pixabay, Openverse, Coverr, Storyblocks, Wikimedia Commons, the Internet Archive, the Metropolitan Museum of Art, NASA and the Library of Congress. Those libraries receive the search term and nothing else. They never receive your recording, your transcript or your film.

The pictures a film ends up using are copied into our own storage so the film can be built reliably. That picture store is served without sign-in, at long random addresses that cannot be guessed or listed. Your recording and your finished film are never kept there.

The film is made

The film's plan, and a link to your recording that expires, are handed to our rendering infrastructure, which produces the finished MP4 and writes it to private storage along with its own working records for that render.

It comes back to you

You download the finished film through a signed link that expires. Once you have saved it to your Photos, your Files or your computer, that copy is yours and this policy no longer reaches it.

How a template is built

When a company builds a template in the Look Lab, the videos and pictures it uploads go into private storage, and are converted to a standard format and measured on our own servers at Amazon Web Services. Google's Gemini watches the videos and looks at the pictures, and Anthropic's Claude reads still frames from them and writes the template's design. Neither of them may train its models on these files. The template that results belongs to the company (section 6 of the Terms of Service).

4A. Connected assistants

You can connect Storias to an AI assistant, such as ChatGPT from OpenAI or Muse from Meta, and ask it to make a film for you. You connect it once, from the assistant: you sign in to your Storias account and approve the connection. This section says what passes between Storias and the assistant. Everything else in this policy applies to a film you make this way exactly as if you had made it in the app or on the website.

What the assistant sends us

• The video, or a link to it. A video you attach in the assistant reaches us as a temporary download link, or you can give the assistant a link yourself. We fetch the video once and keep a copy in private storage, as we do for a video you upload yourself.
• Your request. What the assistant passes on to do what you asked: which look you want, whether the film is vertical or widescreen, which of your films you are asking about, or that you want to know your credit balance.

We do not receive your conversation with the assistant or your chat history, and the assistant does not send us your name or your email address. It sends us only what it needs to do what you asked.

What we send back

To do what you ask, the assistant receives from us: the looks you can choose from; how far a film has got; a finished film's look, length and the credits it used, with links to watch and download it, which stop working after about two hours; a reference such as "Green 7F3A" if a film could not be finished; a list of your recent films; and your credit balance. It never receives from us the material a film is made from: your recording, your transcript or the footage analysis.

What the assistant does with it

Each assistant is run by its own company, under that company's own terms and privacy policy: ChatGPT by OpenAI, Muse by Meta. What it keeps of your conversation, including a video you attach there and the links and details we send back into it, is governed by that policy, not this one, and Storias cannot change it. If you would rather a film's links did not appear in a conversation with an assistant, do not connect one.

The connection itself

For each assistant you connect, we keep a record of the connection: the name the assistant gives itself, when you connected it and when it last used the connection. We also keep the key that lets it act for your account, stored only as a secure hash, or encrypted so that only that connection can unlock it.

Removing a connection

In Storias on the web, at edit.storiasai.com, open Settings → Connected apps. It lists each assistant you have connected, when you connected it and when it last used the connection. Choose Disconnect and the connection stops working at once: the assistant can no longer make films, see your films or read your credits. To use Storias from it again, you connect it again. Deleting your account (section 7) removes every connection.

How long we keep it, and your rights

The same as the rest of this policy. A film you make through an assistant is kept like any other film (section 6): the video, everything made from it and the finished film are deleted 90 days after we receive the video, and the record an assistant reads to find a film you have just made is kept for 48 hours after work on the film ends. The record of a connection, including one you have removed, is kept until you delete your account. Your rights are the same as for everything else we hold (section 9), including deleting your account (section 7).

5. Who we share your data with

We share only what each company needs to do its job, and only so it can do that job for you. Each is bound by its contract with us and by its own terms, and none of them is permitted to use your content to train its models. We pay for the plans that say so, including Google's.

Each of these companies uses its own infrastructure providers to run its service. We may also disclose data where the law requires it, or to protect our rights or someone's safety. If Storias is ever sold or merged, your data may move with the business, and this policy travels with it until it is replaced by one you are told about.

An assistant you connect yourself is different. If you connect Storias to an assistant such as ChatGPT (OpenAI) or Muse (Meta), it receives what it needs to do what you ask: the looks, how your films are going and their links, a list of your recent films, and your credit balance. It receives them because you asked it to, not to do a job for us, so what it does with them is governed by its own terms and privacy policy, not by this one (section 4A).

The advertising platforms are different too. Meta, TikTok and Google receive the events in section 12 only if you accept our cookie banner, and they receive them to help us measure our own advertising, not to do a job for you. Each handles them under its own terms and privacy policy (section 12).

5A. Partner program

Storias has a partner program: people who bring others to Storias can earn a share of what those people pay. Its terms are in section 5A of the Terms of Service. This section says what it means for your data; everything else in this policy applies as usual.

If you apply to be a partner

• What we collect. The name the people you invite will see ("Invited by" and your name), links to your profiles or pages, a description of your audience, how you will promote Storias, your country, and the email address we pay you at. We also keep our decision on your application.
• What we use it for. To review your application, to show your name to the people you invite, and to pay your commissions. No one outside Storias sees your application; the people you invite see only your name.
• How long we keep it. Until you delete your account. Then your name, links, audience description, promotion text and payout email are cleared. The record of what you earned and were paid stays, with your country but without those details, for as long as the law requires us to keep financial records (section 7).

If you arrive through a partner

• In your browser. A partner's link, storiasai.com/?ref= followed by their code, carries that code. storiasai.com keeps the last code in your browser's storage for up to 60 days, and passes it on in the links from the site to the web app, which keeps the last code in its own browser storage for up to 60 days too. A code is the partner's, not yours: it says nothing about you. Choosing "Only necessary" erases the copy storiasai.com keeps and stops it keeping another, so the code then travels only with a click on the page whose address carries it. The web app is a different site: its copy stays until it expires or you clear your site data.
• On your account. When you create an account, we record on it which partner referred you, whether by link or by a code you typed, and when. If you delete your account, this record goes with it.
• What the partner sees. Only counts and amounts: clicks (the visits our own measurement, section 12, saw arrive with their code in the last 90 days), sign-ups, paying customers and earnings. Never your name or email address.

The welcome bonus

A person who joins through a partner gets 120 bonus credits once their email address is confirmed. To give it only once per person, we keep a one-way hash of the normalized email address (in lower case, with any +tag removed and, for Gmail, the dots removed), like the one-way hash we keep for trying Storias before you pay. This one is kept even after you delete your account, because otherwise deleting an account and joining again would pay the bonus again. It holds no readable address.

Commissions

We work out a partner's commission from the payments the people they referred make, and from refunds of those payments. We pay by hand, by bank transfer, PayPal or a similar service, using the payout email the partner gave us. The partner never sees who paid. If the person who paid deletes their account, their payments stay in the partner's records without naming anyone. Your rights in section 9 apply to all of this.

5B. Trying Storias before you pay

Before you make an account, you can try Storias by making one film: a gift of 60 credits covers one film of up to 60 seconds. This section says what that trial means for your data; everything else in this policy applies as usual. This policy and our Terms of Service apply from the moment you upload, as the upload screen tells you.

What happens to your video

It is processed exactly as for any other film (sections 4 and 5): your video, its audio and the words in it go to the same AI service providers and the same rendering service. Until you pay, you can watch only a lower-quality copy with a Storias mark on it, made from the film on our own servers at Amazon Web Services and played from a link that stops working after about two hours. The film without the mark stays in private storage, where no link to it is made, so it cannot be downloaded. The link in the email works on any device, so anyone who has it can watch the preview and move the film to an account of their own: keep it to yourself.

What we keep

• A temporary account. You try Storias as a visitor, so we create an account for you with no name and no password. It holds your film, where you came from (the campaign, and the partner if there was one) and your answer about ad measurement (section 12). If you then make an account, it is this same account, and all of that goes with it. If the address you typed already has an account, you sign in to it and the film moves there instead. Nothing about a temporary account is sent to Meta, TikTok or Google.
• Your email address. You must give one. We keep it on the temporary account to send you one email about your film, saying that it is ready or, if it could not be finished, that it was not, with a signed link that works for 7 days, and to fill the address in when you make your account. We also keep a one-way hash of it (in lower case, with any +tag removed and, for Gmail, the dots removed), so that a trial is given only once per person. The hash holds no readable address.
• Your network address, grouped and hashed, never readable, so that we can limit how many trials are started from one network in a day.
• The steps you take. The look you chose, the language of the page, when you uploaded, when the film was ready, whether you watched it and picked a plan, and when you made an account or paid. We use them to see where people get stuck.

How long we keep it

• If you never pay, the video you uploaded, the film and its preview are deleted 7 days after you start. The deletion runs every hour. Whatever else was made from your video follows section 6. If you pay, the film moves to your account and is kept like any other film (section 6).
• The address you typed stays on the temporary account until you finish making an account, when it is removed. If you never make one, the temporary account and the address on it are deleted 7 days after you start, together with the files.
• The two hashes and the record of the steps stay after the files go, and after you delete your account, with no readable address and no longer tied to the account, so that deleting it and starting again cannot give you a second trial (section 7).

To see, correct or delete what we hold from a trial, write to privacy@bearishfh.com. Your rights in section 9 apply to all of it.

6. How long we keep things

Ninety days is the standard window. Everything a film is made from, and the film itself, is deleted automatically 90 days after you upload. You do not have to ask, and there is nothing to switch on.

The sweep runs automatically, several times an hour. After it, a project stays in your library as a record of what you made, but its recording, its plan and its film are gone: it cannot be re-rendered, and it cannot be copied into a new project.

If you delete a project yourself, its files go then, not in 90 days.

7. Deleting your account

Open Settings → Delete account, in the app or on the web. Everything goes at once: your profile, your projects, your recordings, transcripts, analyses, plans, pictures, finished films, your credit balance, your credit history, and your sign-in itself. There is no waiting period and no soft delete.

Cancel your subscription first. Deleting your account does not always stop the billing. On the web, we cancel a subscription we can reach before anything is erased, and we tell you if it was bought somewhere we cannot reach. Deleting from the iPhone, iPad or Mac app cancels nothing — so if you pay through the App Store, or through our web checkout, cancel there before you delete, or you will keep being charged for an account that no longer exists.

What is kept, and why. We keep the record that a payment happened — which purchase, when, how much. Tax and accounting law requires a business to keep its financial records, normally for seven years. Your account identifier is stripped out of those rows when you delete, so what is left is a transaction, not a person.

Partners and the welcome bonus. If you were a partner, the record of what you earned and were paid stays, without your name or contact details. If you received the welcome bonus, a one-way hash of your email address stays, so that the bonus cannot be paid twice (section 5A).

Trying Storias before you pay. If you made a trial film, the one-way hash of your email address, the grouped hash of your network address and the record of the steps you took stay, with no readable address and no longer tied to your account, so that deleting it and starting again cannot give a second trial (section 5B). A temporary account that never became an account deletes itself, with the address you typed, 7 days after you start (section 5B).

Two short-lived copies are not reached by the deletion itself and expire on their own instead: the working copies inside our render service, within 7 days, and any copy an AI service provider holds while it works on your film, which expires on their side.

Apple, Stripe and RevenueCat keep their own records of your purchases, under their own policies and their own legal obligations. Deleting your Storias account does not delete those, and we cannot delete them for you.

8. Where your data is processed

Storias runs in the United States. Rendering runs in Amazon's US West (Oregon) region. Our database, uploads and sign-in are hosted by Supabase; finished films, and the working copies of recordings used while a film is made, are stored with Cloudflare in the United States; and this website and the web app are hosted by Cloudflare. The AI providers named above process data in the United States and, depending on the provider, in other countries.

If you are in the European Economic Area, the United Kingdom or Switzerland, your data is transferred out of your region to be processed. Where we do that, we rely on the European Commission's Standard Contractual Clauses together with the UK Addendum, or on another lawful transfer mechanism the provider offers. Ask us and we will tell you which one applies to which provider.

9. Your rights, and how to use them

Two of these you can do yourself, right now, without asking anyone:

• Get a copy of your data. In the web app at edit.storiasai.com, Settings → Download my data gives you a JSON file holding your profile, your projects, your transcripts, your footage analyses, your film plans, your credit history and your billing events. It does not contain the video files themselves — those you download from Projects. This button is on the web only today; email us and we will send you the same file.
• Delete everything. Settings → Delete account, in the app or on the web, as described in section 7.

You also have the right to:

• Know what we hold about you and why. This page is the answer, and we will confirm the specifics of your own account on request.
• Correct anything wrong. Your name is editable in Settings; email us about anything else.
• Object to, or restrict, processing we base on our legitimate interests.
• Withdraw consent where we asked for it. We ask in one place, the cookie banner on storiasai.com (section 12).
• Take your data elsewhere. The JSON export above is built for exactly this.
• Complain to your data protection authority — your national authority in the EEA, the Information Commissioner's Office in the UK. We would rather you came to us first and gave us the chance to fix it.

For anything that is not already a button in the app, email privacy@bearishfh.com. We answer within 30 days, and we will tell you if we need longer and why. It costs nothing, and we will not treat you differently for asking.

10. Our legal bases (EU, EEA and UK GDPR)

• Performing our contract with you. Making your film, building and providing your company's templates, running your account, taking payment. Without this data there is no Service.
• Our legitimate interests. Keeping the Service secure, preventing abuse and fraud, fixing what breaks, and improving Storias by analysing the templates companies build, in aggregated or de-identified form (section 3). We have weighed this against your rights and kept the data to the minimum that does the job. You have the right to object to that analysis: a company admin can turn it off at any time in Settings ("Help improve Storias"), or you can write to us at privacy@bearishfh.com.
• Your consent. Optional website analytics, and telling Meta, TikTok and Google about your sign-up, first film and purchases (section 12), and nothing else. You can say no, and you can change your mind later.
• Legal obligation. Keeping financial records, and answering lawful requests.

Your recording, and everything made from it, will contain sensitive information if you choose to talk about sensitive things. We do not ask for it, we do not search for it, and we do not categorise it. But you decide what you record, so it is worth keeping in mind.

11. California (CCPA/CPRA)

If you live in California you have the right to know what personal information we collect and why, to get a copy of it, to correct it, to delete it, and to limit how sensitive personal information is used.

We do not sell personal information. We do not share it for cross-context behavioural advertising, as California defines those terms, with one exception: if you accept our cookie banner, we tell Meta, TikTok and Google when you sign up, finish your first film or buy (section 12), and California may count that as "sharing". If you decline or never choose, nothing is sent, and you can stop it at any time with "Change your privacy choices" in section 12.

The categories we collect are: identifiers (your account id and email); commercial information (your purchases and credits); internet activity (how you use our website and web app, the campaign and ad click id that brought you and, only if you agree, optional analytics); audio and visual information (your recordings and your films); and the content you create. We collect them for the purposes in section 3, from you and from our payment providers, and we keep them for the periods in section 6. If you apply to be a partner, we also collect the details of your application (section 5A). If you try Storias before you pay, we also collect a hash of your network address and the record of the steps you take (section 5B). We do not knowingly collect or sell the personal information of anyone under 16.

Use the buttons in Settings, or email privacy@bearishfh.com. We verify a request through the email address on the account. We will not discriminate against you for making one.

12. Cookies and analytics

The iPhone, iPad and Mac apps have no analytics. No tracking SDK, no advertising identifier, no session replay. The only storage they use on your device is what keeps you signed in and remembers your settings.

We measure our own website and web app. Our own measurement runs on every visit, without asking, to storiasai.com and to the web app at edit.storiasai.com, including sign-up pages such as /start, before you have an account. It needs no consent and uses no advertising cookies. It records:

• the pages you open and in what order, how far down you read and how long you stay;
• the links to the web app that you click;
• the site that sent you (its name only, never the full address), and the campaign tags (utm) and ad click ids that an ad adds to the address you arrived by, such as fbclid, ttclid or gclid, and, if you came through a partner's link, the partner's code (section 5A);
• the language of the page, a device type (phone, tablet or computer), a browser family (never its version) and a country;
• in the web app, the steps you reach: an upload started, a template chosen, a film rendered, watched or downloaded, a price screen opened. Once you are signed in, these are tied to your account, so we can see where the product fails people.

A visit is recorded under a random identifier, not your name or email address, and that identifier is kept in your browser's storage. We do not keep your IP address, and there is no session replay. We do not keep your browser's user-agent string either, with one exception: only if you chose "Accept all", we keep it for at most 7 days, together with the address of the page where you signed up, finished your first film or bought, and only to send them to Meta (below). We delete them as soon as your answer turns to no. All of this stays on our own servers and no third party receives it, except the one thing described below, and only if you accept. Visits and the steps in the web app are deleted after 90 days; the random identifier that ties a visit to the web app is kept for a year.

Where you came from. When you create an account, we keep on it the first campaign that brought you: the audience of the landing page (for example real estate), the campaign tags (utm source, medium, campaign, content and term) and the ad platform's click id (fbclid, ttclid or gclid). Links from storiasai.com to the web app carry a random identifier of your visit (and, on our ad landing pages, the campaign tags), which is how a visit and an account are tied together; the web app keeps the first campaign in your browser's storage, for up to 30 days, until it is written onto your account. We use it to learn which of our ads bring people who actually use Storias. It stays on your account until you delete the account (section 7).

Telling Meta, TikTok and Google about your sign-up and purchases, only if you accept. If you choose "Accept all" on our cookie banner, our server tells Meta (Facebook and Instagram), TikTok and Google when you create an account, when you finish your first film and when you make a purchase. It sends: a one-way hashed (SHA-256) version of your email address, a hashed version of your account id, the ad click id from your visit, the time of the event and, for a purchase, its value and currency. It also sends Meta, and only Meta, the address of our page where the event happened (without anything after a question mark) and your browser's user-agent string (the browser and device type it reports), because Meta requires both on an event from a website. We do this to measure and improve our advertising. A hash is not anonymous: a platform can hash the email addresses it already holds and compare. Each platform handles what it receives under its own terms and privacy policy: Meta's, TikTok's and Google's. If you declined, or have not chosen, nothing is sent. To stop it later, change your choice with the button at the end of this section, or write to privacy@bearishfh.com. What a platform has already received stays with it.

PostHog and Microsoft Clarity ask first. On your first visit a banner asks whether optional analytics may run. Until you say yes, neither of these loads and neither sends anything:

• PostHog — page views, clicks, scrolling, and which campaign link brought you here, so we can see which pages actually work.
• Microsoft Clarity — the same, plus session replay, which records how a page was used. Form inputs are masked, so what you type is not captured, and advertising storage is switched off.

Choose "Only necessary" and neither of them runs. We use no advertising cookies and load no ad-network scripts or pixels on any of our sites. The only thing we send to advertising platforms is the server-side message described above.

You can stop all of it on this website, including ours. Change your privacy choices. Choosing "Only necessary" stops, on the page you are reading, our own measurement of this website, PostHog and Clarity; it erases the identifier this site had stored in your browser and any partner code it kept (section 5A), and keeps all of it off on every later visit too — without that identifier, what was measured before cannot be tied back to you. It also stops the messages to Meta, TikTok and Google, from the moment your answer reaches your account (below). Your choice is stored in your own browser, and clearing your site data clears it. The web app at edit.storiasai.com receives your answer when you arrive from a link on storiasai.com, and keeps the latest answer on your account. It has its own switch too: Settings → Privacy → Ad measurement. To stop the sharing later, choose "Only necessary" on storiasai.com (it reaches your account the next time you open the web app from this site), turn off Ad measurement in the web app's Settings, or write to privacy@bearishfh.com. For what the web app records, your rights in section 9 apply.

13. Security

• Everything travels over HTTPS.
• Your files live in private storage, and the database enforces row-level security, so a record can only be read by the account that owns it.
• Links to your media are signed and expire.
• Sign-in tokens are held in your device's secure storage — the Keychain on Apple devices — never in plain files.
• Network addresses used for abuse prevention are hashed before they are stored, so we hold no readable list of them.
• Access to production systems is limited to the people who need it.

No system is perfectly secure and we will not pretend otherwise. If a breach affects your personal data, we will tell you and the relevant authority as the law requires.

14. Children

Storias is not for children. You must be at least 13 to use it, and at least 16 in the European Economic Area, the United Kingdom, and anywhere else that sets a higher age. We do not knowingly collect data from anyone younger. If you believe a child has given us data, email privacy@bearishfh.com and we will delete it.

15. Changes to this policy

We update this page when what we do changes. The date at the top says when we last did. If a change matters to you — a new company that receives your content, a different retention window, a new purpose — we will tell you in the app or by email before it takes effect, not after.

16. Contact

Privacy questions, requests, or anything on this page that reads wrong: privacy@bearishfh.com.

Questions about the Terms of Service: legal@storiasai.com.