Privacy policy

What Storiteca learns about you, who it shares that with, and how to make it forget.

In effect since October 18, 2026.

Reading needs no account

You can read articles without signing in or telling us anything about yourself. The site has no analytics, no advertising and no tracking scripts.

Like any web server, ours keeps a log of requests: the page address, the time, your IP address and what your browser says about itself. We use it to keep the site running, to find errors and to count how often articles are read. The log is kept for up to 90 days.

Two things on an article page come from YouTube. Video covers load from YouTube's image servers. The player loads only when you ask for it — with the “Watch the video” button or a click on a fact — and comes from youtube-nocookie.com, YouTube's privacy-enhanced mode. From that moment Google receives your requests and handles them under the Google Privacy Policy.

Cookies

• rv_lang — the interface language, if you chose one yourself. Kept for a year.
• rv_session — keeps you signed in. Set only when you sign in with Google, removed when you sign out, and lasts no longer than 30 days.

There are no other cookies, and nothing else is stored in your browser.

An article from a link

An article is made from a public video: its title, description, captions or speech, and frames. It gets its own address and is open to everyone, like the video — unless the channel's author hides it. If you aren't signed in, we don't know who asked for it.

Signing in with Google

Storiteca uses YouTube API Services. Signing in is only needed to manage articles about your own videos or to browse your subscriptions. This is everything we get and what it's for.

• Your Google account ID and email address. To recognise you the next time you sign in, to check an invitation while sign-up is by invitation, and to answer if you write to us. We don't send newsletters.
• “View your YouTube account”. Your channel's ID and name and the list of your uploads: each video's title, date, length and cover. This is how Storiteca shows you your videos and knows which articles are yours. When you refresh your subscriptions, also the list of channels you follow and their public videos, so you can choose what to read.
• Access tokens. Google issues them so we can do these reads without asking you to sign in every time.

Storiteca never changes anything on YouTube: it has no call that uploads, edits or deletes. To learn about new videos on your channel, it subscribes to YouTube's public notification hub with your channel ID — no token is used for that.

What we never do

• We don't sell your data, give it to advertisers or data brokers, or use it for advertising.
• We don't use data received from Google to train AI models — ours or anyone else's.
• People at Storiteca don't read your YouTube data, unless you ask us to look into a problem, it is needed to protect the service from abuse, or the law requires it.

Data received from Google is used only to provide and improve the features of Storiteca described on this page. We don't transfer or disclose it to anyone except the services listed below, and they handle it only on our behalf and only for that purpose.

How Storiteca uses information received from Google APIs, and passes it to any other app, follows the Google API Services User Data Policy, including its Limited Use requirements.

Who else handles the data

• An AI service writes the article. The words of the video — captions or a transcript of its speech — and its public details go to a language model's API. None of it comes from your Google account, and under its terms the provider does not train its models on this data.
• Hosting. Our server and database are in the USA; article frames are stored in the Netherlands.
• A domain and mail service runs the site's domain name and forwards mail sent to our address.
• A video data service fetches the public details, captions, sound and frames of public videos. Nothing about you goes there.
• Google provides sign-in, the YouTube API and the video player.

Each of them gets only what its part of the work needs. Before using your data for anything new, we'll ask you.

Want to know which company does which part? Write to hi@storiteca.com and we'll tell you.

How we protect your data

• Encryption in transit. The site works only over HTTPS, and browsers are told to use nothing else for it. Our server talks to Google, the AI service and the storage over encrypted connections too.
• Encrypted tokens. The access tokens Google issues — the most sensitive data we hold — are stored in our database encrypted (AES with an HMAC signature). The key is not kept in the database, so a copy of the database alone gives no access to anyone's YouTube account.
• A closed database. The database can't be reached from the internet: only the site's own processes on the same server connect to it. Keys and passwords are kept apart from the code.
• Sign-in and sessions. The session cookie is HttpOnly and Secure: scripts on the page can't read it, and it is sent only over HTTPS. Signing in is protected against forged requests by a signed one-time parameter.
• Limited access. Only the person who runs Storiteca has access to the server, the database and the backups.
• The least we need. We ask Google only to view your YouTube account, and keep only what the site uses, for no longer than described below.
• Backups. The database is copied daily; copies are kept for 14 days in private storage that can only be reached with a key. In the copies the tokens stay encrypted.
• If something goes wrong. If we learn that your data may have been exposed, we'll revoke the affected access tokens and tell you by email without undue delay.

Articles about your videos

An article about a public video is public by default. If the video is yours, you can take the article, rewrite it, add pictures or hide it. What authors get → What you write and upload is stored with the article and shown to readers in place of the machine version.

How long we keep it

• Account and email — until you delete the account.
• Access tokens — until you delete the account or revoke access. Every day we check that Google still accepts them; tokens it no longer accepts are erased.
• The list of your videos and your subscriptions — refreshed from YouTube or deleted at least every 30 days. Once access is revoked, they're deleted within 30 days.
• Articles — for as long as the site exists, unless the video's author hides them.
• Request log — up to 90 days.

Revoking access and deleting your data

There are two ways, and either is enough.

• Delete your account on Storiteca — the link is at the bottom of your channel page, or go straight to this page. We revoke the access Google gave us and at once erase your account, tokens, the list of your videos and your subscriptions. Articles about your videos stay as you left them — hidden ones stay hidden — and become yours again if you come back.
• Revoke access in Google — on the Third-party apps & services page of your Google account. From that moment Storiteca can't read anything; we erase the tokens within a day and the rest within 30 days.

Deleting your data here changes nothing on YouTube: your channel, videos and captions stay as they are.

Questions and complaints about your data, or a request to delete it for you — write to hi@storiteca.com. We answer, and delete what you ask for within 7 days.

Changes

If this policy changes, the new version appears on this page with a new date. If the change is about data received from Google, we'll ask for your consent again before using the data in the new way.

Terms of use → For authors →