In short
A production Talevara service will need account, reading, creator, community, device, and transaction data to provide its features. This policy identifies how Talevara handles account, reading, creator, community, device, and transaction data for the service.
1. Data controller
The controller for Talevara user data is the Talevara operator identified through the legal-notice and support routes shown on this site. If a data-protection officer or EU/UK representative is legally required, those details must be added here.
2. Scope
This policy covers Talevara websites, applications, creator tools, community features, support interactions, and other services that link to it. Separate privacy notices may be used where a feature has materially different processing.
3. Information Talevara may process
| Category | Examples |
|---|---|
| Account & profile | Email, username, display name, avatar, language, age/eligibility confirmations, account settings. |
| Reading activity | Library items, reading progress, follows, bookmarks, ratings, discovery preferences, interactions with recommendations. |
| Creator activity | Draft and published content, story metadata, content labels, publishing history, creator settings, monetization status. |
| Community | Comments, reviews, forum or discussion posts, reports, blocks, moderation history. |
| Transactions | Purchase/subscription identifiers, amount, currency, tax location where required, refund and payout records. Full payment-card details should be handled by the selected payment provider rather than stored by Talevara unless strictly necessary. |
| Technical & security | IP address, device/browser data, log events, timestamps, crash information, authentication and security signals. |
| Support & legal | Messages to support, privacy requests, rights-holder notices, illegal-content notices, appeal records, supporting files you choose to provide. |
| Cookies & similar tech | Authentication/session data, preferences and, only where permitted and configured, analytics or advertising identifiers. |
4. Why Talevara may use information
| Purpose | Typical legal basis where GDPR applies |
|---|---|
| Provide accounts, libraries, reading, publishing, purchases, and creator tools | Performance of a contract / steps requested before a contract. |
| Secure the service, prevent abuse, maintain logs, and investigate fraud | Legitimate interests; legal obligation where applicable. |
| Moderate content, handle reports and appeals, and comply with lawful orders | Legitimate interests, contract, and/or legal obligation depending on the action. |
| Personalize discovery and recommendations | Legitimate interests or consent depending on the data and local law. The final implementation must document the actual basis. |
| Send marketing newsletters | Consent where required. Users must be able to unsubscribe easily. |
| Optional analytics or advertising technologies | Consent where required for access/storage on a user’s device and for subsequent processing. |
| Process payments, tax records, refunds, and creator payouts | Contract and legal obligations. |
5. Sources of information
Information may come directly from you, from your use of Talevara, from service providers acting on Talevara’s behalf, from payment providers, or from other users when they report content or interact with public features. If Talevara obtains personal data from a third party in a way that requires additional notice, the production service must provide that notice.
6. Public content and creator visibility
Material you publish publicly can be viewed, shared through service features, indexed by Talevara discovery, and potentially indexed by external search engines depending on page settings. Drafts should remain non-public unless you explicitly publish or share them through a feature designed for that purpose.
7. Recommendations and profiling
Talevara may use reading history, follows, ratings, selected genres, format preferences, and similar interaction signals to order discovery results or recommendations. The production product should provide meaningful information about the main recommendation parameters and relevant controls. Talevara should not make solely automated decisions that produce legal or similarly significant effects on a person unless a lawful basis and required safeguards are in place.
8. Sharing information
Talevara may share personal data with contracted providers that perform hosting, storage, authentication, email, analytics, customer support, moderation, security, payments, tax/KYC, and similar functions. The final policy must identify material provider categories and, where appropriate, a current subprocessor list.
Information may also be disclosed to authorities or other parties when required by law; to protect rights, safety, or security; in connection with a corporate transaction subject to applicable safeguards; or at your direction.
9. Creator analytics
Creators may receive statistics about readership and engagement with their work. The production design should prefer aggregate or appropriately pseudonymised metrics and should not expose unnecessary personal data about individual readers.
10. International transfers
If personal data is transferred outside the EEA, UK, or another jurisdiction with transfer restrictions, Talevara must use an applicable lawful transfer mechanism, such as an adequacy decision or approved contractual safeguards, and document the relevant measures.
11. Retention
Talevara should keep personal data only for as long as needed for the purpose for which it was collected, including account operation, contractual obligations, security, fraud prevention, legal claims, tax/accounting, moderation records, and statutory requirements. Retention periods are maintained according to account operation, contractual obligations, security, fraud prevention, legal claims, tax/accounting, moderation records, and statutory requirements.
12. Your privacy rights
Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, receive portable data, withdraw consent, and complain to a supervisory authority. Where GDPR applies, requests are generally handled without charge and within the statutory timeframe, subject to permitted extensions or identity checks.
Talevara now includes an authenticated Privacy & Data area with self-service JSON export, optional-consent controls and the existing account-deletion request. Correction, restriction, objection and other legal requests route through the Step 26 privacy support-case workflow. Support and statutory notice routes are available through the linked support forms.
13. Cookies and similar technologies
See the Cookie Policy. Talevara now defaults optional analytics, marketing, recommendation personalization and personalized advertising to off until the user makes a choice. Withdrawal clears queued local analytics and prevents new optional analytics events from being created.
14. Children and teenagers
Talevara must apply an age approach appropriate to the final service and markets. Children’s data requires additional protection, and privacy information addressed to young users should be especially clear. Profiling-based advertising to minors must not be used where prohibited by applicable law.
15. Security
Talevara should use technical and organizational measures appropriate to the risks of the service, including access controls, secure authentication, logging, backups, vulnerability management, and incident response. No system can guarantee absolute security.
16. Changes to this policy
Material changes should be communicated in a way appropriate to their impact. Version dates and prior versions should remain available where practical.
17. Contact and complaints
Privacy requests, controller questions, complaints, and representative inquiries can be submitted through the linked privacy support route.
Questions about this policy?
Use the privacy support case form. The case system records the request and its history; support and statutory notice routes are available through the linked support forms.