Privacy
What is collected, why it is used, who receives it, how long it stays, and the choices and rights available to you.
Effective 10 September 2026 · version 2026-09-10
1.0 Scope, controller and definitions
1.1 This Privacy Policy applies to Telleny applications for phone, tablet, desktop and browser, the application programming interfaces and other services behind them, and the Telleny website. It applies whenever you create an account, visit the website, purchase or manage a subscription, write or upload material, use the assistant, contact support, or otherwise interact with Telleny.
1.2 Telleny is operated by Xavier Alexander Torres Calderón, a sole trader, of Bolívar 501 y 5ta. Esq., Ciclo 1, Quevedo 120306, Ecuador. The operator is the data controller for the processing described here. References to “Telleny”, “we”, “us” or “our” mean that individual operator and do not imply that Telleny is a separate corporation. Operating as a sole trader does not reduce any privacy right available to you under applicable law.
1.1 Meaning of personal data and processing
1.3 “Personal data” means information that identifies you or can reasonably be linked to you, directly or indirectly. “Processing” includes collecting, storing, organising, using, sending, receiving, restricting and deleting that information. Story content may be personal data even when it uses fictional names if it identifies or describes a real person.
1.4 This policy describes current production behaviour. It does not grant Telleny permission to collect a category merely because the category is mentioned, and it does not replace a separate notice or consent where applicable law requires one.
2.0 Personal data we collect and its sources
2.1 Most personal data comes directly from you: when you register, write, upload a document, speak with the assistant, configure a preference, report a problem, request support or exercise a right. Other limited data comes from the sign-in, subscription and device services you choose, and from technical records created as the service responds to a request.
2.1 Account and authentication data
2.1.1 We collect your email address, username, account identifier and authentication status. If you choose Google or Apple sign-in, we receive the provider identifier, email address and profile fields that provider makes available under your chosen settings. We do not receive your Google or Apple password.
2.1.2 We keep session identifiers, refresh-token records, device descriptions, sign-in times and revocation status so that authenticated sessions work and you can sign out a particular device or every device. Passwords created directly with Telleny are stored only as cryptographic hashes, not as readable text.
2.2 Creative content and communications
2.2.1 We store the stories and worlds you create, including people, places, rules, relationships, timelines and recorded changes; volumes, chapters, scenes, drafts, revisions, saved versions and review decisions; conversations, notes, preferences and board content; and the files and extracted text you attach.
2.2.2 Your manuscript may contain sensitive information or information about another person. Submit only material that you have the right to process, and avoid credentials, financial details, health information, private communications or other secrets that are unnecessary for the request. Telleny does not need those categories merely because the assistant accepts free-form text.
2.2.3 When you contact support, privacy or safety, we process the address you use, the contents and attachments of the message, related account details and the steps taken to investigate and answer it. Do not send more information than is needed to describe the issue.
2.3 Usage, subscription and technical data
2.3.1 We record assistant requests, the model and tools used, the records they accessed or changed, token or text quantities, cost, completion state and errors. We record your plan, entitlement, quota use, store product and transaction references, renewal state and the result of subscription verification. Apple, Google and RevenueCat provide these subscription records; Telleny does not receive your full payment-card number.
2.3.2 Technical records can include IP address, request date and time, application version, operating system, device or browser type, session identifier, requested route, server response, latency and diagnostic information. If notifications are enabled, we keep the device token and delivery preferences required to address them.
2.3.3 Telleny does not use an advertising identifier, third-party behavioural analytics, cross-site tracking, data-broker information or cookies for advertising measurement. We do not combine your writing with an advertising profile.
3.0 How and why personal data is used
3.1 We use account and session data to register and authenticate you, secure the account, synchronise sessions, respond to requests and provide the service you asked for. We use creative content to save, organise, search, display, revise and export your work, and to generate an assistant response only when you choose that feature.
3.2 We use usage and technical records to enforce plan limits, reconcile subscriptions, calculate and verify model cost, operate tools, diagnose failures, prevent fraud and abuse, maintain availability and investigate security incidents. We use support communications to answer you, document the resolution and defend or establish legal rights when necessary.
3.3 Depending on the circumstance and applicable law, processing is necessary to perform the service agreement with you, based on your explicit consent for disclosure of content to AI providers, necessary for compliance with law, or based on legitimate interests in security, fraud prevention, reliability and defending rights. Where consent is the basis, you may withdraw it without affecting processing already completed.
3.4 Telleny does not sell personal data, license your writing as a data product, share personal data for cross-context behavioural advertising, create advertising profiles, or use your stories or conversations to train a model of its own. It does not make solely automated decisions about your legal rights, credit, employment, health, insurance or access to an essential service. Assistant output is a creative suggestion for you to assess.
4.0 Processing by service providers and AI systems
4.1 Telleny uses service providers only for defined operational purposes and gives each provider the categories reasonably necessary for its task. The current categories, locations and purposes are also maintained on the subprocessors page.
4.1 DeepSeek for conversation and story assistance
4.1.1 After you explicitly accept the current policy, an assistant request may send DeepSeek your message; the story title, genre, tone and point of view; relevant entity names; up to four related passages; chapter text that the assistant opens to read or revise; and text extracted from a supported document attachment. Image attachments are rejected in this conversational path rather than sent to DeepSeek.
4.1.2 DeepSeek processes this material to generate the response you requested. The commitments that govern a request are those applicable to Telleny’s API account. DeepSeek’s published material describes processing and storage in the People’s Republic of China and permits some information to be used for service operation, security and improvement. Telleny therefore does not promise immediate provider-side deletion or a restriction that the applicable provider agreement does not guarantee.
4.2 OpenAI for private semantic search
4.2.1 After your acceptance, Telleny may send unsummarised plain text from your story or conversation to OpenAI’s API to create an embedding: a numeric representation used to find relevant parts of your own writing. OpenAI returns that representation, and Telleny stores it with the source story or conversation so it is covered by account deletion.
4.2.2 OpenAI states that API data is not used to train its models by default. Unless a stricter data-control setting applies to Telleny’s account, limited request information may be retained for abuse monitoring for up to thirty days. The embedding endpoint does not maintain conversational application state on Telleny’s behalf.
4.3 Hosting, identity, delivery and commerce providers
4.3.1 Hetzner hosts application services in Germany. Supabase provides the managed PostgreSQL database and private attachment storage. Google and Firebase support selected sign-in and device notifications. RevenueCat reconciles subscription entitlements received from Apple and Google. Apple and Google operate their stores and process billing under their own account and privacy terms.
4.3.2 Cloudflare provides domain-name, website routing and role-email infrastructure. Telleny sends account verification and password-reset email from infrastructure it operates. Contracted infrastructure providers may process account, content or technical data only to the extent their assigned function requires; none is engaged to advertise to you or build an advertising profile.
4.4 Legal, safety and organisational disclosures
4.4.1 We may disclose the strictly necessary information when required by applicable law, a binding court order or a valid governmental request; to investigate fraud, abuse or a security incident; to protect a person from serious harm; or to establish, exercise or defend legal rights. We assess the scope and authority of a request where the law permits and do not voluntarily disclose more than is reasonably necessary.
4.4.2 If the service or its assets are sold, reorganised or transferred, relevant data may be disclosed under confidentiality for evaluation and transferred as part of that transaction. A successor to the sole trader must honour this policy for the data it receives and provide notice before materially different processing. This clause does not permit the sale of personal data as a standalone product.
5.0 Consent and your choices
5.1 AI features remain unavailable until you receive the current disclosure and affirmatively accept it. Acceptance authorises the content disclosures to DeepSeek and OpenAI described in section 4 for the stated purposes; it is not general permission to sell the material, use it for advertising or send it to an unnamed AI provider.
5.2 Declining keeps functions that require those providers switched off. It does not close your account or block access to existing stories, manual editing, exports, subscription management, account settings, privacy controls or account deletion. A paid subscription does not remove the need for a valid privacy decision.
5.3 The decision record contains acceptance or refusal, the policy version, a fingerprint of the disclosed content, locale, time and one-use request identifier. You may withdraw consent later. Withdrawal stops future AI disclosures but cannot recall a request that has already been processed or invalidate processing lawfully completed before withdrawal.
5.4 A material change to an AI provider, purpose or category of disclosed data makes the earlier acceptance out of date. The application must present the updated disclosure and obtain a new affirmative choice before sending new material. Editorial corrections that do not change processing may update the published text without disabling an otherwise valid decision.
5.5 Device permissions and store settings are separate choices. You may disable notifications in the operating system, revoke active sessions in the app, manage or cancel the store subscription through Apple or Google, and request account deletion. Some choices limit the related feature because the data is technically necessary to provide it.
6.0 Retention, deletion and backups
6.1 Account information, creative work, consent records and ordinary operational records are generally retained while the account exists because they are needed to provide, secure and account for the service. We may retain a record for longer when law requires it, including tax, accounting, transaction, dispute or fraud-prevention records, and then only for the applicable purpose and period.
6.2 To start deletion, open Settings > Delete account and confirm. The account is immediately disabled, its email and username are replaced with non-personal placeholders, and all sessions are revoked. You are signed out everywhere and the account cannot be used to sign in again.
6.3 A scheduled cleanup then removes stories, world data, recorded changes, volumes, chapters, drafts, saved versions, review decisions, conversations, attachments, extracted and searchable text, embeddings, assistant preferences and execution records, subscription and usage records, notification addresses, settings, privacy decisions and the remaining account record.
6.4 The scheduled phase handles deletion requests in batches. Its completion time depends on the queue and successful completion of the cleanup, so this policy does not present an unverified best-case interval as a guaranteed deadline. You may ask for confirmation of completion. Operational or diagnostic records outside the automated cleanup can be reviewed and erased manually on request unless a lawful retention exception applies.
6.5 Encrypted backups expire according to their protected rotation cycle. They are isolated from ordinary production access and are not restored to answer a user request. If disaster recovery temporarily restores data already scheduled for deletion, the deletion record must be reapplied before that data returns to ordinary use.
6.6 The account deletion page describes the user-facing and technical sequence in more detail.
7.0 Your privacy rights and requests
7.1 Subject to the law that applies to you, you may request confirmation of processing and access to personal data; correction of inaccurate or incomplete data; deletion; restriction; objection; portability in an available structured format; and withdrawal of consent. You may also ask for information about the categories, sources, purposes and recipients of your data.
7.2 The app exports a chapter as Word or PDF but does not currently provide a one-click archive of every account record. An email request is available for broader access or portability. Exercising a privacy right will not result in discriminatory treatment, although deletion, restriction or withdrawal can make a feature unavailable when its required data can no longer be processed.
7.3 To protect you and other users, we may request information reasonably necessary to verify identity, account control and a representative’s authority before disclosing, correcting, transferring or deleting data. Verification information is used for the request and security record, not for advertising.
7.4 A request may be limited or refused where an applicable exception permits it, including where it is manifestly unfounded or excessive, would reveal another person’s data, conflicts with a legal retention duty, prejudices an investigation or legal claim, or would undermine security or fraud prevention. We will explain the decision and the available review route unless law prevents that explanation.
7.5 Requests are ordinarily answered within one month. A legally permitted extension may be used for a complex request, with notice of the reason. You may ask for a second review, contact the privacy authority with jurisdiction where you live, or pursue another remedy available under applicable law.
8.0 Security, international transfers and children
8.1 Telleny uses technical and organisational safeguards appropriate to the service, including password hashing, encrypted transport, private storage access controls, revocable sessions, least-purpose provider access, operational logging and account deletion controls. Safeguards are reviewed as the service changes, but no network, device, database or provider can be guaranteed completely secure.
8.2 If a personal-data incident occurs, we will investigate its nature, affected data and likely consequences, contain and remediate it, preserve necessary evidence, and notify affected people and competent authorities when and within the time applicable law requires. A report can be sent to the safety or privacy contact without waiting for certainty.
8.3 Telleny is operated from Ecuador and uses providers in other countries. DeepSeek may process in the People’s Republic of China; other providers may process in Germany, the United States and other locations where their contracted infrastructure operates. The privacy laws and public-authority access rules in those locations may differ from yours.
8.4 Where applicable law requires a transfer mechanism, Telleny relies on the relevant provider agreement and available contractual or legal safeguards, and assesses provider, purpose and location before enabling the transfer. You may request information about the safeguards that apply, subject to confidentiality and security limits.
8.5 Telleny is not directed to anyone under 16 and accounts are not knowingly created for them. If you believe a child has provided personal data, contact us with enough information to locate the account; we will investigate and delete it when appropriate. Do not send unnecessary information about the child in the report.
9.0 Policy changes, complaints and contact
9.1 The effective date and version at the top identify the current policy. Earlier published versions may be retained for accountability. When a change materially alters a purpose, provider, data category or user consequence, Telleny will provide an appropriate notice; where consent is required, the change will not authorise new AI disclosure until you accept it.
9.2 We may make clarifying, formatting or contact-detail corrections that do not materially change processing. Continued use of non-consent-based features after notice of another lawful update may be subject to the updated policy, but silence or continued use is not treated as explicit consent for a new AI disclosure.
9.3 Questions, privacy requests, consent concerns and complaints may be sent to the address below. Include the account email where relevant and a clear description of the request, but do not include a password or more personal data than necessary.
9.4 Contact Xavier Alexander Torres Calderón, a sole trader at kinder-world-telleny@outlook.com. That address reaches the individual responsible for Telleny and its privacy responses.
9.5 If a concern is not resolved, you may request internal reconsideration and complain to the data-protection or consumer authority that has jurisdiction over you. Nothing in this policy waives a mandatory right or remedy that applicable law gives you.