Privacy
Last updated 19 November 2026
The short version
- Tela keeps what it needs to run your reading list, and nothing for advertising.
- We don't sell your data, show ads or use analytics.
- What you read, like and highlight stays private unless you choose to show it. Your profile, your recommendations, the blogrolls you make public and the blogs you claim are public, and search engines can find them.
- You can take your subscriptions and your data with you whenever you like, and delete your account in Settings → Account.
What we collect
Your account
- Your email address.
- Your handle, and if you add them, a display name, a bio and a picture.
- If you set a password, only a hash of it, never the password itself.
- If you sign in with Google or GitHub, which account there is yours. We keep no tokens from them, and not the name or picture they send.
- If you joined with an invite code, that code, and so who invited you. If you hand out codes, the codes you made and who joined with them.
- If you start to join with a code and don't finish, your email address is held against the code for a day.
Your reading
- The blogs you subscribe to, the folders you put them in, the feeds you add, and any an import is still adding.
- Which posts you've read, liked and recommended, and the notes on your recommendations.
- Your highlights and the notes on them.
- The people you follow.
- Your blogrolls: their names and descriptions, the blogs in them, your notes on those blogs, and whether each is public.
- Your settings: languages, theme, text size and the like.
- The translations you ask for and what each cost, and how many blogs new to Tela you add each day, to keep everyone within the daily limits.
- Which posts you open in full from blogs you don't subscribe to, counted for the daily limit and kept for two days.
Blogs you claim
- Which blogs you claim, how you proved it, and the result of each check.
Reports you send
- What you reported, why, anything you wrote with it, and the address of the page you reported it from.
Translations you flag
- Which post and which part of its translation you flagged, the translation as you read it, and anything you wrote with it.
Apps you connect
- Each app you connect: what you allowed it, when you connected it, and when it last acted for you (below).
Apps you register
- If you register an app: its name, developer name, homepage, privacy policy, redirect addresses and the most it may ask for; the contact address you give for it; when you accepted the developer rules; and any review you asked for, with your note (below).
Technical records
- Each signed-in session keeps the IP address and browser it started from.
- In the admin console, Tela’s operator sees the day each account last used Tela, taken from its sessions, and how many members changed something each week, such as marking a post read. Your reading history, subscriptions, the people you follow and your likes are not in it.
- To stop abuse, sign-in attempts, codes and joins are counted per IP address and per email address, whether or not that address has an account, and some actions per account.
- Cloudflare, which runs Tela, logs each request: the address asked for, the time, your browser, and network details such as your IP address.
- Tela uses no analytics.
What's public
Anyone can see your profile at telaread.com/@yourhandle. It shows your handle, display name, bio and picture, the month you joined, how many people you follow and how many follow you, how many posts you've recommended, the blogs you've claimed, the posts you recommend with your notes, and your public blogrolls. It also carries the random account number Tela uses for follows.
- Your recommendations also reach the people who follow you, and appear in Discover beside the posts you recommend, notes included. A recommendation with a note also appears on the blog's page on Tela and in its writer's Dashboard, with your name and handle.
- Once you recommend posts, or show the blogs you read, Discover may suggest you as a reader to follow, to anyone browsing it, saying why: a post you recommended, or a blog you show. Tela matches suggestions to what each member likes and reads on their own device; nothing private of yours is used to suggest you.
- A blogroll is private until you make it public. A public blogroll, with its name, description, blogs and your notes on them, is open to anyone: on its own page, on your profile, and in Discover once it has three blogs others can see. A private blogroll only you see. Tela’s operator can hide a public blogroll from Discover; it keeps its page and its place on your profile.
- The posts you like and the blogs you read are shown only if you turn them on in Settings → Privacy. Then they appear on your profile and to the people who follow you, including on a blog's page as a reader they follow.
- Your picture is the one you upload. Without one, it's your Gravatar, which stays on until you turn it off in Settings → Profile. Without either, it's your initial.
- A picture you remove or turn off can stay in browser and network caches for up to 30 days, at an address nothing links to any more.
- How many members read a blog is public once three of them do; below three, no number is shown. How many liked or recommended each post is public. A blog that three members read is listed in Discover.
- Tela’s operator reviews the blogs members add, and may list them in Discover. The review shows each blog and how many members read it, never who.
- Writers see counts in their Dashboard, not names. Who read or liked something shows only where that member made it public.
- Never public: your email address, what you've read, your highlights and their notes, and your settings.
- Public pages can take a few minutes to catch up with a change, and search engines can find them (below).
Search engines and AI
- Tela's public pages can be indexed by search engines: the front page, Discover, blogs' pages, public blogrolls and members' profiles.
- AI tools that search the web to answer a question may read those pages too, and quote them or link to them.
- Tela asks AI crawlers that collect training data to stay off the pages that show writers' work. It asks in its robots.txt, and can't make every crawler listen.
- A new profile isn't offered to search engines for its first days.
- Nothing that needs you to sign in is public: your reading list, your settings and everything private stay out of every crawler's reach.
- A search engine keeps its own copy for a while, so a change or a removal can take time to reach its results.
How we use it
- To run Tela: fetch your feeds, keep your reading list in step across your devices, and show your profile.
- To translate posts (below).
- To email you, only about your account: to sign you in, to confirm what you asked for, or to keep it safe.
- To stop abuse, and to look into reports.
We never show ads, sell or rent your data, or use it to profile you. Tela doesn't train AI models.
- A sign-in code, with a link, when you ask for one.
- An invitation, if Tela’s operator invites you.
- A code to reset your password, when you ask for one.
- A code to confirm, when you ask to delete your account.
- A notice when your sign-in methods change.
No newsletters, no digests.
Translation
- Tela translates posts into the language you read in: Simplified or Traditional Chinese, English or French. Titles and excerpts are translated as posts arrive, and the full text when someone opens the post or asks for it. Traditional Chinese is converted from the Simplified translation, not translated again.
- What is sent is the post's own text, with the post's title and the blog's name for context. Nothing about you is sent: not your name, email address, handle or what you read.
- Translation is done by Alibaba Cloud Model Studio (Bailian, dashscope.aliyuncs.com), in mainland China.
- A translation is kept and shared: everyone who reads that post in that language sees the same one.
- Each account has a daily number of new translations, and Tela a daily budget for the whole site. Past either, a translation waits for the next day (Terms).
- A writer who claims their blog can turn translation off for it in the Dashboard.
Who else handles your data
Cloudflare
Runs Tela: its Workers, its database (D1, in Singapore), its file storage (R2), its queues and its request logs.
Resend
Delivers Tela's emails, so it handles your address and what each email says.
Alibaba Cloud Model Studio (Bailian)
Receives blog text to translate, and never anything about you.
Gravatar
While your Gravatar is on, Tela's servers ask Gravatar for your picture using a hash of your email address. Your browser never contacts Gravatar, and the hash is never published.
Google and GitHub
Only if you sign in with them. They will know you signed in to Tela. When you claim a blog with GitHub on your account, Tela's servers also ask GitHub for that account's public username and website, and where its GitHub Pages site points, and keep none of it.
Blogs
Tela fetches feeds and post images itself, so a blog doesn't see you when you read it on Tela. Opening the original, or a link in a post, takes you to that site directly, and tells it only that you came from telaread.com, not from which post.
Tela’s operator can see the database, to keep Tela working and to act on reports. No one else does, unless the law requires it.
Apps you connect
Apps made by other developers can connect to your Tela account if you let them. Any member can register an app, and Tela may review it (Terms). You connect one on a page of Tela's own, which shows what the app asks for, and the app never gets your password.
That page shows the app's name, who made it, and links to its homepage and privacy policy. For an app Tela hasn't reviewed, it says so, and shows its developer's Tela handle rather than a name they chose.
What an app sees
- Read only: your subscriptions and folders, posts and their full text, your likes, recommendations and highlights, your reading history, the people you follow, your reading preferences, and Tela's public pages. It can't change anything.
- Read and write: all of that, and it can make changes for you: mark posts read, like, recommend, highlight, subscribe, add feeds, file blogs in folders, follow people, change your reading preferences, and ask for translations, which count toward your daily translations (Terms).
- Your email address, only when the app asks for it, Tela has reviewed the app and allows it, and you agree when you connect it.
- No app can delete your account, change how you sign in, download your data, or do anything only Tela’s operator can.
What Tela keeps, and what the app keeps
- Tela keeps a record of each connection: the app, what you allowed it, when you connected it, and when it was last used. Tela records the hour it was last used; Settings → Connected apps, where you can see each connection while it lasts, shows the day.
- The record is kept until the connection ends, when you disconnect the app or for one of the reasons below, and deleted 30 days after that.
- What an app stores is that app's responsibility, under its own privacy policy, which the page you connect it on links to.
- Disconnecting an app stops it at once, on all your devices. It doesn't delete what the app has already stored: ask the app to delete it.
- Every connection ends when you set, change or reset your password, link Google or GitHub, sign out everywhere, or delete your account. Tela’s operator can also end an app's connections, or stop an app for everyone.
If you register an app
- Members who connect your app see its name, the developer name you gave it or your @handle, and links to its homepage and privacy policy.
- Tela keeps the contact address you give for the app, to write to you about it, and never shows it to anyone.
- Settings → Developer shows how many members are connected to your app, never who they are.
- What your app keeps about the members who connect it is your responsibility, under your app's privacy policy (Terms).
- Members can report an app, and Tela can cut it off.
How long we keep it
- When a session ends, its record, with its IP address and browser, is deleted within a day. A session ends when you sign out, or after 60 days without use.
- The counters that stop abuse, which hold an IP address, an email address or an account number, are deleted after a day.
- Cloudflare keeps its request logs for 7 days.
- A recommendation, highlight or blogroll you remove, or a blog you take out of a blogroll, stays in the database marked as removed, with its text, so your other devices catch up. Deleting your account removes them (below).
- The record of which posts you opened from blogs you don't subscribe to is deleted after two days.
- The record of an app you connected is kept until the connection ends, and deleted 30 days after that. Its tokens are kept only as hashes, and deleted once they can never be used again.
- An app you register is kept until you delete it.
- Cloudflare keeps a 30-day restore point of the whole database, and Tela copies the database every night, keeping each copy 30 days. Something you change or remove can stay in either that long. The nightly copy leaves out sessions, sign-in codes, abuse counters, app tokens and the posts you opened.
Deleting your account
You can delete your account in Settings → Account. Tela emails you a code to confirm it, and once you enter the code, the account is closed. That can't be undone.
- At once, or within minutes, Tela removes your email address, your sign-in methods, your profile and pictures, your subscriptions and folders, what you've read, your likes, recommendations and notes, your highlights, your blogrolls, and your follows both ways.
- Every device you use is signed out, and the copy of your reading list in a browser is cleared the next time Tela runs there.
- Your handle is kept, unused, so nobody can take it to pass as you.
- Blogs you claimed are released. Their switches, such as translation, stay as they were.
- Invite codes you made stop working. Anyone who joined with one keeps their account.
- Apps you registered stop working for everyone: their connections end, and the contact addresses you gave for them are deleted.
- Records of what translations cost are kept, no longer tied to you. Blogs you added stay on Tela for the people who read them.
- Backups keep a copy for up to 30 days (How long we keep it). Caches can show your old picture for up to 30 days, and your profile page for a few minutes.
Your choices
- Export your subscriptions, with their folders, as OPML in Settings → Subscriptions.
- Download your data as one file in Settings → Privacy → Your data: your profile, settings, subscriptions, reading history, likes, recommendations, highlights, blogrolls, the people you follow, the blogs you claimed and your invite codes.
- Choose what others see in Settings → Privacy. Your picture and Gravatar are in Settings → Profile; an uploaded picture you remove is deleted.
- Set or change a password, link or unlink Google and GitHub, and sign out everywhere in Settings → Account.
- See the apps you have connected, and disconnect any of them, in Settings → Connected apps.
- Register apps, see how many members each has, and delete them, in Settings → Developer.
- While joining Tela needs an invitation, see the invite codes you made and who joined with them in Settings → Invites, and revoke one nobody has used.
- Change your handle, name and bio whenever you like.
- Remove a recommendation, highlight, like, follow or blogroll at any time. It disappears from Tela at once, and from public pages within a few minutes. Making a blogroll private takes it off public pages the same way.
- Release a blog you claimed, from the Dashboard.
- Delete your account in Settings → Account (what happens).
- For anything else about your data, write to me@hutu.si.
Age
Tela is for people aged 16 and over. If you know of an account that belongs to someone younger, write to me@hutu.si and we'll delete it.
Changes
The date at the top changes when this page does.
Contact
Tela is a personal, non-commercial project run by one person, hutusi (AI Naive). For anything about your data, write to me@hutu.si. Bugs and ideas are welcome as issues on GitHub, but those are public.