Your script is not used to train AI models
What you write in Telos — projects, characters, scenes, authorial voice, comments — is yours, and stays yours. We do not use your material to train models of our own, and we do not pass it to third parties for them to train theirs. Both providers Telos calls undertake not to train their models on content sent through the API: Anthropic (Claude models), under its published commercial terms, and OpenAI (voice transcription in the Creation Room and reference embeddings), under its published platform documentation.
Under the API’s published retention policy, content sent is deleted within 30 days — subject to the exceptions Anthropic itself states: a submission flagged by its automated trust and safety systems may be retained for up to 2 years, and the classification score for up to 7 years; retention may be longer to comply with the law or enforce its Usage Policy. Telos holds no zero-retention (ZDR) agreement with Anthropic; that arrangement is approved by Anthropic on a case-by-case basis. OpenAI keeps abuse-monitoring logs that may contain the content sent; Telos holds no zero-retention agreement with OpenAI either, an arrangement likewise subject to case-by-case approval.
You can export everything you created in Telos at any time, as structured JSON, or delete your account — irreversible after a 30-day recovery window.
This policy describes what personal data Telos processes, for what purpose and on what legal basis, with whom it is shared, how long it is kept, and how you exercise your rights. The LGPD (Law 13.709/2018), the GDPR (Regulation (EU) 2016/679) and applicable U.S. state privacy laws (CCPA/CPRA and equivalents) apply.
1. Who the controller is
Telos is operated by Oger Sepol Produção e Comércio Audiovisual Ltda., a company incorporated in Brazil under registration (CNPJ) no. 07.567.854/0001-01, with establishment at R. Saint-Hilaire, 380, apto. 102 — Água Verde — Curitiba/PR — CEP 80.240-140 — Brasil. The company is the controller of the personal data processed in the product (GDPR art. 4(7) / LGPD art. 5, VI).
Data Protection Officer: privacidade@telos.guru. You may lodge a complaint with the ANPD (Brazil) or, if you are in the European Union, with the supervisory authority of your country of residence.
2. What data we collect
Waiting list (before an account exists):
- E-mail — what let us invite you when access opened
- The language of the page where you signed up, so the invitation arrives in your language
- Truncated IP address (e.g. 200.158.xxx.xxx) and browser, only to tell a person from a bot and to see where sign-ups come from
- Whether and when you were invited, and whether you asked to leave the list
Until September 2026 access was by invitation, and the waiting list was the way in. Sign-up is now open and the list takes no new sign-ups. Any invitation we sent stores the same e-mail, an expiry date and a record of use — never the link itself, which exists only in the message you receive.
Account and authentication:
- Name and e-mail (required)
- Tax registration (CNPJ, VAT, EIN or equivalent) — only if you declare that you are contracting on behalf of a legal entity. That number determines which of the two tracks of the Terms governs the contract; without it, the consumer track applies. We do not collect an individual taxpayer number (CPF); the field rejects one.
- Password, stored as a bcrypt hash — never in plain text
- E-mail confirmation: when you create an account without an invitation, we send a confirmation link to the address you gave. We keep the date of confirmation and, while the link is valid (24 hours), only a cryptographic digest of it — never the link. Confirmation is required before subscribing because the contract, receipts and renewal notices are sent to that address (legal basis: performance of a contract and pre-contractual steps — LGPD art. 7, V; GDPR art. 6(1)(b)).
- Sign-up attempt with an e-mail that already has an account: if someone tries to create an account with an address that already has one, we send the holder of that address a security notice, with no data about who tried. We do not reveal on screen whether the address has an account (legal basis: legitimate interest in account security — LGPD art. 7, IX; GDPR art. 6(1)(f)).
- To curb sign-up abuse, we count attempts per IP address and per e-mail in short-lived counters stored only as an irreversible code (HMAC), never the IP or e-mail in clear.
Support and relationship:
- To support you, the team sees in an internal record of your account what we already process for the purposes in this section — subscription, charges, credit usage, AI cost, projects (name and format, never the content) and messages you sent us.
- Internal notes and tags the team records about the account — for example, a request you made or a problem you reported. They never include the content of your works, and you receive them in your data export.
Authorial content:
- Projects, characters, scenes, hooks, comments, analyses and compiled authorial voice — everything you write or generate with AI inside Telos.
- Project versions and branches.
- Material you bring to the Creation Room — a document, image, audio, page link or a conversation pasted from another tool. The AI reads that material to reply to you, and Telos keeps only the text that comes out of it: the document’s text, the audio transcript, a description of the image, the text of the page or conversation. The original file is not kept. When you paste a link, it is the Telos server that fetches the page — public pages only; the site sees our server’s address, not yours.
- Reference images you ask for in the Creation Room for a character or for the project’s world, generated from the visual description written in the profile.
- Ratings of the Room’s replies (helpful / not helpful, and why, if you say), with the beginning of the rated reply — up to 300 characters —, used to adjust the next replies to you in that same project.
- Shared Creation Room. Room conversations belong to the project: whoever you invite to the project with edit permission sees those conversations and can take part in them, with the name of who wrote each message; while someone is in the Room, the others see their name (kept for 2 minutes).
- Presence in the script editor. While you have a script open, the other people on the project (and you yourself, in another tab) see your name and the scene you are in — so nobody writes over anybody. We keep only the name, which script or episode is open, the scene (by its internal identifier, never the text) and whether you are editing, for 2 minutes.
- An invitation to collaborate, if you do not have an account yet. When a project owner invites your e-mail and you do not use Telos yet, we keep the e-mail, the project and the role of the invitation, and send you a message explaining how to join. The project owner is the one who gave us your e-mail. The invitation only takes effect once you create the account with that e-mail and confirm it.
- Record of the creative process (Terms, §6), while it is on for the project: every version of the screenplay text, in full, with who wrote it, the server time and the link to the previous record; the text of AI suggestions you accept or reject; and that of passages you paste into the editor (25 characters or more), marked as coming from Telos’s AI or from outside. Third-party text you paste stays in the record as pasted from outside. You can turn the record off for each project.
- Learning from your corrections (optional, off by default, turned on per project by the project owner): while it is on, we read the versions of the screenplay that the process record already keeps — the text Telos’s AI wrote and the version left after the correction, yours or that of anyone who edits the project with you — to find what repeats in the corrections. When the project owner asks for the search, the lines that changed go to Anthropic (section 4), which drafts up to five proposed voice rules. We keep the proposed rules, the decision on each (accepted, rejected or pending) and, as evidence for each rule, short excerpts of the lines that changed, before and after, from up to three corrections. Accepted rules guide the AI’s writing in that project and go along with each writing request to Anthropic. No model is trained on this material. If the process record is off, no new correction is kept, and only those already recorded can be read. We also keep when learning was turned on and off, by whom and under which version of this Policy, as proof of consent.
- Style profile of your voice (for as long as the project exists): we compute, inside our systems and without sending it to third parties, a statistical profile of your style from your voice samples and the lines the process record attributes to whoever writes by hand, to measure whether the AI’s text sounds like you. We keep only the profile (scrambled character fragments and rhythm measures) and, for each text the AI writes, the score and the measures, never the text.
Usage and billing:
- Credit usage history (operation, date and cost), processed for fraud prevention and support.
- Payment data is processed directly by Paddle, which is the seller of the transaction. Telos receives only the customer identifier, the billing country and the subscription status; we do not store card numbers.
Technical:
- Application access records — date, time and source IP, kept for six months under confidentiality and in a controlled environment, under art. 15 of Law 12.965/2014 (Brazilian Internet Civil Framework). Legal basis: compliance with a legal obligation (LGPD art. 7, II). After that period, the record is deleted.
- In the product’s other records (account auditing), the IPv4 address is truncated at write time — the last two octets are discarded and cannot be reconstructed. IPv6 addresses are truncated equivalently, keeping only the prefix.
- User-agent (browser and operating system), processed for error diagnosis and compatibility checks.
- Cookies and browser local storage — the full list, with the purpose of each, is in section 11.
What is required, and what happens if you do not provide it. Name, e-mail and an access credential are a contractual requirement: without them the account cannot be created and we cannot perform the contract. Access records are imposed by law and do not depend on your choice. Tax registration is optional, and not providing it means the consumer track of the Terms governs your contract (GDPR art. 13(2)(e) / LGPD art. 18, VIII).
3. Why we collect it (legal bases)
- Performance of a contract (LGPD art. 7, V / GDPR art. 6(1)(b)): without an account there is no way to deliver the tool you subscribed to. This includes the record of the creative process (Terms, §6), which you can turn off for each project, and the style profile of your voice (section 2), which measures the AI’s writing against your text. We keep the full text of each version because a record made only of digests does not prove what was written.
- Compliance with a legal obligation (LGPD art. 7, II / GDPR art. 6(1)(c)): tax records, retention of access logs, and responses to lawful requests from public authorities.
- Legitimate interests (LGPD art. 7, IX / GDPR art. 6(1)(f)): fraud prevention, platform security, and product usage measurement — the latter from events carrying a pseudonymous identifier and no authorial content, to establish which features are used and where in the writing flow use stops. You may object at any time, through the control in section 11. Also support and relationship: bringing the account’s status together in an internal record and reaching out when there is a problem — for example, a declined charge or an unused subscription close to renewal.
- Consent (LGPD art. 7, I / GDPR art. 6(1)(a)): marketing communications; in the European Union, the United Kingdom and Switzerland, usage metrics; and learning from your corrections, in each project where you turn it on (section 2) — turning it off stops the reading immediately. Consent may be withdrawn at any time, and withdrawal does not affect the lawfulness of processing carried out before it (GDPR art. 13(2)(c)).
4. Who we share with
Only with the processors strictly necessary for the service to work. Each processes data under its own published data-processing terms, which bind whoever contracts its service — and those terms are what we are subject to as a customer. Some of those terms are incorporated automatically into each service’s agreement; others require a separately signed instrument. For the status of a specific processor, write to privacidade@telos.guru.
- Anthropic PBC (Claude API, USA): processes prompts and returns responses, on the terms described in the highlight above. This includes the images you attach in the Creation Room, which the AI reads to reply to you.
- Paddle.com Market Ltd (United Kingdom): sells and processes the transaction as merchant of record. Paddle is NOT a processor acting for Telos — it decides on its own how it handles your payment data, in order to charge, account for tax, prevent fraud and meet obligations of its own. In the language of the GDPR and the LGPD it is an independent controller, not someone processing on our behalf. That processing is described in its own privacy policy. Telos receives back only the customer identifier, the subscription status and the billing country; the card number never passes through here.
- Paddle Retain (formerly ProfitWell, a Paddle group product; script served from
public.profitwell.com): runs in your browser when you open the checkout, and exists to recover failed payments and measure cancellation. We send it the Paddle customer identifier — the same opaque code we already use to charge you — never your email address and never any part of your work. Like any page script, it also sees the page address, the IP and the browser. Paddle describes that processing in its own privacy policy. We record here a limit we would rather declare than hide: Paddle’s public documentation does not say which of its four group entities operates Retain. We are asking them, and will update this line as soon as we have the answer in writing. - Vercel Inc. (USA): web application hosting. The functions that run the product execute in the default region of our Vercel account; Vercel’s delivery network serves static files from points of presence in several countries, with no authorial content. Large files you attach in the Creation Room (above 4 MB) pass through private Vercel storage until they are read — usually minutes — and are deleted right after. The reference images generated in the Room are kept in that private storage and served only to people with access to the project.
- Neon, LLC, a subsidiary of Databricks, Inc. (USA, AWS US East region): managed Postgres database, running on Amazon Web Services infrastructure. AES-256 encryption at rest and TLS in transit.
- Upstash Inc. (USA): used for two distinct purposes. For abuse control, the counting keys leave us hashed: your account identifier, the request’s IP address and the e-mail entered in the password-reset flow are converted into an irreversible code before being sent, and expire with the rate-limit window. For caching, we keep already-computed analysis results for a few minutes — the key identifies the project, and the value may contain material derived from your work, such as diagnostics and quoted evidence. And we keep for 2 minutes who is in each part of a project — in the Creation Room (the name and the open conversation) and in the script editor (the name, the open script or episode and the scene, never the text) —, so the people on the project can see who is there.
- PostHog Inc. (USA, US Cloud): product usage measurement. See section 5.
- Functional Software, Inc. (Sentry) (USA): error monitoring, with personal-data scrubbing enabled on both client and server.
- Resend, Inc. (USA): delivery of the product’s transactional e-mail (order confirmation, password reset, account notices). It receives your e-mail address and the message content.
- Cloudflare, Inc. (USA): authoritative DNS for the domain and routing of inbound e-mail. If you write to an @telos.guru address, the message passes through it before reaching our mailbox.
- OpenAI, L.L.C. (USA): three functions, and all three receive material of yours. Semantic search turns your scene text into numerical representations, so the AI can find the relevant scene instead of re-reading the whole project. And voice transcription in the Creation Room receives the audio you record or attach and returns text — what travels there is your recording. And reference image generation in the Creation Room, when you ask for it, receives the visual description written in the profile (the character’s appearance; for the world, the era, place and aesthetic) — never the screenplay or the conversation — and returns the image.
Voice through the browser. In the Creation Room, the microphone has two paths, and you choose the first time you use it. Through Telos, the audio goes to the OpenAI transcription described above. Through the browser, which costs no credits, speech recognition is done by the browser itself, and the audio goes to its maker’s speech service (Google, in Chrome and Edge; Apple, in Safari), under that maker’s rules. That service is neither contracted nor controlled by us, and Telos receives only the text it returns. Your choice is stored in your browser and can be changed at any time.
Requests from authorities. We disclose data to third parties only under a court order or a lawful request from a competent authority, within the limits the law authorises.
Who answers for what. We determine the purposes and means of the processing, and it is us you hold accountable. The processors above handle your data on our behalf and on our instructions, within the limits of what we contracted, and may not use it for their own purposes (LGPD art. 9, VI).
Timestamping of the record. Once a day, a single cryptographic digest (hash) covering the records of all projects with the record turned on is sent to timestamping authorities — DigiCert, Inc. (USA) and FreeTSA (freetsa.org) — and to the public OpenTimestamps servers, which write it into a block of the Bitcoin network. No text, name, e-mail or identifier of yours leaves Telos. The digest is irreversible, and not even we could tell from it whose it is or what it contains without the records kept here: it is anonymised data (LGPD art. 12). We disclose it anyway, for transparency. A Bitcoin record is public and permanent: the digest stays there after the project is deleted, linked neither to you nor to the content. If you ask for a timestamp of the PDF on export, the same applies to the PDF’s digest (DigiCert, or FreeTSA if it does not respond).
International transfer mechanisms are set out in section 9.
5. Usage metrics (PostHog)
We collect usage events to establish which features are used and at what point in the writing flow use stops. Collection is done through PostHog, on the following terms:
- Identifier: your account’s internal code, random and meaningless outside Telos. It is pseudonymous, not anonymous — because it is linked to your account it remains personal data, and every right in section 7 applies to it. We do not send your e-mail, your name or any text from your work.
- Events: project creation, scene writing, acceptance or rejection of an AI suggestion, credit consumption and payment. Metadata only — date, time, identifiers, format and amounts — never scene text.
- IP address: used to derive the approximate country and region of the visit, then discarded — PostHog is configured not to store the address. What remains is the derived location and the event, not the IP.
- Cohort: sign-up week, for aggregate retention analysis.
- Off by default: autocapture of clicks, session recording, form-field capture, and cross-site tracking cookies.
- GPC and DNT, and how far the signal reaches: browsers sending Global Privacy Control or Do Not Track turn collection off — both the events from the browser and those our server records during your use. Events originating outside a visit of yours (the payment confirmation Paddle sends us, for example) carry no signal from your browser, and the signal does not apply to them. To reach those events as well, use the e-mail request described below.
- Prior consent in the European Union, the United Kingdom and Switzerland: in those territories nothing is collected until you allow it. In other countries collection starts on and you switch it off whenever you want.
To switch usage metrics off, choose Do not allow in the footer notice, or use the control in section 11 at any time — both take effect immediately, in this browser. To record your objection in writing, or to reach the events that originate outside your browser, write to privacidade@telos.guru (LGPD art. 18, § 2 — objection to processing carried out on a basis that dispenses with consent; GDPR art. 21(1)).
6. How long we keep it
- Account and authentication (name, e-mail, password hash, tax registration): for as long as the account exists and for 30 days after a deletion request, after which it is erased — except what the tax obligation below requires us to keep.
- Account with an unconfirmed e-mail: if the e-mail is not confirmed within 14 days of sign-up, the account is erased in full, with no further notice — the address may not belong to whoever signed up, which is why we do not send it another message. Such an account holds no content or credits; to use Telos later, just sign up again. For accounts created before this version, the 14 days run from the effective date at the top of this page.
- Internal support notes and tags: for as long as the account exists; they are erased with it.
- Waiting list and invitations: 12 months from sign-up, after which they are erased automatically, whether or not they became an account. If you asked to leave the list, we keep only your e-mail and the date of that request, for an indefinite period — that is what stops a new sign-up, or a batch send, from bringing you back against your wishes. Deleting your account also takes you off the list. E-mail confirmation links expire in 24 hours and are erased when used or replaced.
- Invitations to collaborate sent to people without an account: up to 30 days. They go earlier if the person creates the account (the invitation becomes a collaboration), if the owner cancels it, or if the project is deleted.
- Authorial content: while your account is active. After a deletion request, a 30-day recovery window and then irreversible erasure.
- Material brought to the Creation Room: the extracted text stays with the conversation where you attached it and goes when you remove it or delete the conversation or the project. A large file that passes through temporary storage is deleted as soon as it is read; if the reading is interrupted, a daily automatic clean-up deletes it — it never stays there more than a day.
- Room reference images: while they are the character’s or the world’s image in some version of the project. One no profile uses anymore — replaced, from a deleted character or from a deleted project — goes in the daily automatic clean-up, a day after it stops being used.
- Ratings of the Room’s replies: until you delete the conversation, the project or the account.
- What you write in the Room of someone else’s project: it stays in the project’s conversation, which belongs to the project owner. If you delete your account, your messages there lose their link to you (the name goes away); the project owner can delete the conversation.
- Tax and billing data: the payment records Brazilian tax law requires to be kept for 5 years are held by the payment processor and in the operator’s accounting records — outside Telos. Inside Telos, the credit ledger is deleted along with the account.
- Access records (date, time and IP): six months, as a legal obligation (art. 15 of Law 12.965/2014). Then deleted.
- Account audit records: 24 months, with the IP already truncated, then deleted. They survive account deletion with the link to the user severed, because they document operations that must remain verifiable.
- Record of the creative process: for as long as the project exists. It goes in full when you delete the project’s record, delete the project, or when the account is deleted (after the 30-day recovery window). Like all authorial content, it is also in backups for up to 30 days. The digest written to the Bitcoin network cannot be deleted and is linked neither to you nor to the content (section 4).
- Rules proposed from your corrections: until you delete them (there is a button to delete them all) or until the project or the account is deleted; like all authorial content, they are also in backups for up to 30 days. Turning learning off stops the reading but does not delete what was already proposed — use the button for that.
- Backup copies: up to 30 days. They are encrypted before leaving our systems and replaced on the following cycle. Data erased from the live database remains in that day’s copy until it expires — that is the safety net against accidental loss, and it is why the definitive erasure period in section 7 counts those 30 days on top of the recovery window.
- PostHog usage events: for PostHog’s standard retention period for our account. Withdrawing consent stops collection; to erase history already sent, use the contact in section 5.
- Technical logs: for the standard periods of the providers that host them (Vercel, for execution logs; Sentry, for error reports). We set no period of our own and do not control those periods.
7. Your rights
This section sets out the rights granted to you by art. 18 of Law 13.709/2018 (LGPD) and arts. 15 to 22 of Regulation (EU) 2016/679 (GDPR). Exercising them is free of charge and requires no justification.
- Confirm whether we process data about you and obtain access to it, including by exporting everything as structured JSON (LGPD art. 18, I and II; GDPR arts. 15 and 20).
- Rectify incomplete, inaccurate or out-of-date data. You can correct your screenplay text whenever you want; the process record keeps earlier versions as they were, because a record that can be edited proves nothing. At any time you can turn it off for the project (nothing new goes in), delete it in full (the project stays), or delete the project or the account.
- Delete your account. After a 30-day recovery window we erase your authorial content and account data from the live systems. The backup copies from those days expire on their own retention cycle, within up to 30 further days — after that the erasure is irreversible. Inside Telos only the following remain: audit records, with the link to the user severed; and access records, for the six months that art. 15 of Law 12.965/2014 imposes on the provider — deleted once that period ends. The payment records required by tax law are held outside Telos, by the payment processor and in the accounting records. All as described in section 6.
- Request restriction of processing, or the blocking, anonymisation or erasure of data that is unnecessary, excessive, or processed in breach of the law (LGPD art. 18, IV; GDPR art. 18).
- Object to processing carried out on the basis of legitimate interests, stating your reason (LGPD art. 18, § 2; GDPR art. 21).
- Know which public and private entities we share your data with — section 4 carries the full list (LGPD art. 18, VII).
- Withdraw consent at any time, without affecting the lawfulness of processing carried out before the withdrawal.
- Lodge a complaint with the ANPD (Brazil) or with the supervisory authority of your country of residence (EU).
Direct marketing. You may object at any time, and without giving a reason, to the use of your data for direct marketing. Once you object, we stop that use immediately. Use the unsubscribe link in any promotional e-mail, or write to privacidade@telos.guru (GDPR art. 21(2) and (3)).
If you reside in California or another U.S. state with a privacy law, see section 8 — there are additional rights and a specific response deadline.
8. Your U.S. privacy rights (CCPA/CPRA and other states)
If you are a resident of California or another U.S. state with a consumer privacy law, you have the right to know what personal data we collect and why, to access and correct that data, to request its deletion, to portability, and to opt out of the "sale" or "sharing" of your personal data.
We do not sell your personal data and we do not share it for cross-context behavioral advertising. Our usage analytics is first-party and is not used for ad targeting. We honour the Global Privacy Control (GPC) signal as a valid opt-out request.
We use any sensitive information only to provide the service you request and never to infer characteristics about you. We will not discriminate against you for exercising these rights. To make a request, contact privacidade@telos.guru; you may use an authorised agent. We respond within 45 days, extendable once. California residents may also request the disclosures under California Civil Code § 1798.83 ("Shine the Light").
Residents of other U.S. states with equivalent laws — including Virginia, Colorado, Connecticut, Texas and Oregon — have equivalent rights and may contact us in the same way.
9. International data transfers
Our infrastructure and processors are located in the United States. There is no European Commission adequacy decision for Brazil or for the United States generally; for the U.S. there is only the partial adequacy of the EU–US Data Privacy Framework, which covers certified entities alone.
The mechanism applicable to each processor is as follows:
- Upstash, PostHog and Sentry (Functional Software) — certified and active under the EU–US Data Privacy Framework; each one’s agreement adopts the Framework as the primary mechanism and the Standard Contractual Clauses as a fallback.
- Anthropic — not certified under the Framework; the transfer is governed by the European Commission’s Standard Contractual Clauses (Decision 2021/914, Modules 2 and 3) in its data processing addendum.
- Vercel — certified under the Framework, but its data processing addendum governs the transfer through the Standard Contractual Clauses; those are what we rely on.
- Neon / Databricks — the transfer is governed by the Standard Contractual Clauses in Databricks’ data processing addendum.
- OpenAI — not certified under the Framework; the transfer is governed by the Standard Contractual Clauses in its data processing addendum.
- Cloudflare and Resend — the transfer is governed by the Standard Contractual Clauses in the data processing addendum each of them publishes.
- Paddle — a case apart, because it is not a processor: it is an independent controller (§ 4), and what leaves here for it is only your e-mail and an identifier, so that the purchase can exist. Paddle is established in the United Kingdom, which the European Commission recognises as providing adequate protection — a decision renewed in December 2025 — so a transfer from the EEA requires no additional safeguard. What Paddle does with the payment data is its own decision, described in its own policy.
For transfers out of Brazil, the basis is LGPD art. 33, II, (a) — transfer-specific contractual clauses, in the processing agreements entered into with each processor — and, for payment processing, performance of a contract at the data subject’s request (art. 33, IX). We have not entered into the standard clauses of Annex II of ANPD Resolution CD/ANPD no. 19/2024 with our processors: those require adoption in full and unaltered, agreed with each importer, and none of our processors offers them in its standard agreement.
The safeguards are the standard clauses in each processor’s data processing addendum, published by them and available at any time (GDPR art. 13(1)(f)): Anthropic, Paddle, Vercel, Neon/Databricks, Upstash, PostHog, Sentry, Cloudflare, Resend and OpenAI.
10. Security
- HTTPS required, with two-year HSTS including subdomains.
- Passwords stored with bcrypt, cost factor 12.
- Database encrypted at rest (AES-256).
- Access to personal data restricted and recorded in an audit log.
- In the event of a security incident that may result in relevant risk or damage, we notify the ANPD and, where applicable, the competent supervisory authority in the European Union, within the statutory deadlines, and inform affected data subjects without undue delay.
Found a security flaw? Write to privacidade@telos.guru. We take no legal action against anyone who researches in good faith and tells us before disclosing.
11. Cookies and local storage
Strictly necessary (always on, not subject to choice): the authentication session and CSRF protection written by NextAuth (next-auth.session-token, next-auth.csrf-token and next-auth.callback-url, with the __Secure- or __Host- prefix over HTTPS); the language preference (telos-locale); the home page style you picked in the style bar (telos-estilo, only the style’s name, for 90 days); and the record of your choice in this section (telos-consent and telos-consent-regime).
Browser local storage (always on, not subject to choice). Unlike a cookie, it does not travel with requests: it stays in this browser, and Telos only uses one of its values in a request when the screen needs it to do what you asked (the version of the project you left open, for example). It is strictly necessary to provide the service you request, under the second exception in art. 5(3) of Directive 2002/58/EC. By purpose, we keep there:
- Interface preferences and state: theme, collapsed sidebar, distraction-free writing mode, single-key shortcuts (
telos:atalhos-uma-tecla), open panels and display mode on each screen, PDF page format, writing goals, the version of the project you left open, the notices you have dismissed, the last value shown for indicators such as your balance and the project’s health (so that only changes are flagged), and the list of most recently opened items. - What you typed and is not saved yet: drafts of long forms; the copy of your screenplay text while the server has not confirmed the save, deleted once it does; the passage you take from the editor to the Creation Room, deleted when the Room reads it (one that is not read expires after 30 minutes); the contact details you write for the PDF title page (name, e-mail, phone and address); and, on a shared project’s page, the name and e-mail you comment with — the last two so you do not have to type them again.
- The path you started: the format chosen on the home page before signing up, so that creating the project already starts with it (
telos:formato-da-porta, only the format’s name, deleted when a project is created with it); the page you asked for before confirming your e-mail, so you return to it afterwards (telos:destino-pedido, for up to 24 hours, deleted once used); and the time a payment was completed, so the screen does not offer the charge again while the confirmation arrives (telos:pagamento-em-confirmacao, only the time, for up to 30 minutes).
Clearing the site’s data in your browser removes all of it.
Usage metrics (subject to your choice): when you allow it, PostHog writes its own first-party cookies (ph_*) to distinguish sessions. They hold a random identifier — not your name, e-mail or any text from your work. See section 5. The home page has four ways of presenting Telos, and each visitor lands on one of them at random; when metrics are allowed, the same telos-estilo cookie keeps the style drawn, so the next visit shows the same one and we can measure which presents Telos best. Without metrics, nothing is stored and each visit draws again.
We do not use advertising cookies, cross-site tracking cookies, or social network pixels.
How you choose: in the European Union, the United Kingdom and Switzerland no usage metric is collected before you allow it. In other countries collection starts on. The footer notice asks once; after that, the control below turns it on and off whenever you want, for this browser. In every case, your browser’s Global Privacy Control and Do Not Track signals turn collection off on their own and prevail over any choice recorded here. Clearing site data in your browser removes all of these cookies, and the choice is asked again.
Métricas de uso estão desligadas neste navegador.
12. Children and adolescents
Telos is a professional tool and is not directed at children. You must be at least 18 to create an account. We do not knowingly collect personal data from children under 13 (USA, COPPA) or below the applicable digital consent age in the EU (16, unless a Member State sets a lower age). In Brazil, processing data of children (under 12) requires specific and prominent consent from a legal guardian, and processing data of adolescents follows their best interest. If we identify an account held by a minor without qualified guardian consent, we remove the account and the data.
13. Changes to this policy and corporate succession
Each version of this policy carries a number and an effective date. Substantial changes are announced on this page before they take effect, and you may object to the change and close your account at no cost until the effective date.
In a merger, acquisition, corporate reorganisation or sale of assets, personal data may be transferred to the successor, which is bound by this policy until it replaces it. In that case you are notified by reasonable advance notice and may, within that period, export your content and close your account at no cost. If operations cease, we give the same notice so that you can export your content before erasure.
Contact and DPO
Questions, requests or complaints: privacidade@telos.guru. Requests to confirm processing and for access are answered within 15 days of the request (LGPD art. 19, II). Other requests are answered without undue delay and within one month at the latest (GDPR art. 12(3)). Requests from U.S. residents are answered within 45 days (CCPA/CPRA). Handling is free of charge; we charge a reasonable fee, or refuse the request, only where it is manifestly unfounded or excessive, in particular because of its repetitive character, and the burden of demonstrating that is on us (GDPR art. 12(5); LGPD art. 18, § 5).