1. Who is responsible for your data
The controller of the personal data described here is the operator of Lustales.
Privacy requests go to the privacy mailbox on the contact page.
2. What this policy covers
This policy covers the website, the reader and author areas, the coin and subscription features and the e-mail we send. It does not cover a payment provider's own pages, where that provider acts as its own controller, nor a site we link to.
We do not sell personal data, we do not build advertising profiles, and we do not use your reading history to target ads. Advertising placements on the platform are editorial, not behavioural.
3. The data we collect
We collect only what running the service requires.
| Category | What it contains | Where it comes from |
|---|---|---|
| Account | Username, e-mail address, display name, biography, date of birth, role, password hash (bcrypt — the password itself is never stored), the terms version you accepted and when, the moment your address was verified, account status and timestamps. | You, at sign-up and in account settings. |
| Content | Stories, chapters, comments, and the taxonomy you attach to them. If you use AI-assisted generation, the brief you write and the chapters it produced. | You. |
| Engagement | Favourites, follows, blocks, tips and notifications. | Your use of the platform. |
| Money | Orders (amount, currency, coins, provider identifiers, status, what the provider reported as paid), the coin ledger, subscriptions and payout requests (amount, chosen payment method, status, operator notes). | You and the payment provider's callback. |
| Reports and moderation | Content and error reports you file; copyright notices, including the name, address, signature and description a notice requires; reviewer notes on your submissions; sanctions on your account. | You, moderators and the automated reviewer. |
| Technical | IP address and user-agent on requests (used for rate limiting and abuse control), request identifiers, and the sessions and verification challenges kept in Redis. | Your browser and our servers. |
We do not ask for an identity document, we do not run a credit check and we never store a card number or a wallet key: the payment provider handles those on its own page.
4. Why we process it, and on what basis
Where the GDPR or UK GDPR applies, each purpose below rests on one legal basis. Where it does not apply, the same table describes what we do and why.
| Purpose | Data | Basis |
|---|---|---|
| Creating and securing your account, signing you in, recovering access | Account, technical | Performance of a contract (Art. 6(1)(b)) |
| Publishing your work, counting engagement, showing your profile | Content, engagement | Performance of a contract |
| Taking and crediting payments, keeping the coin ledger, paying authors | Money, account | Performance of a contract; legal obligation for accounting records |
| Reviewing submissions, handling reports and copyright notices, applying sanctions | Reports and moderation, content, technical | Legitimate interests (a lawful, safe platform) and legal obligation for illegal content |
| Rate limiting, abuse prevention, security logging | Technical | Legitimate interests (protecting the service and its users) |
| Transactional e-mail: verification codes, moderation outcomes, payment and payout notices | Account, content, money | Performance of a contract |
| Aggregate page-view statistics | Technical, without cookies or a persistent identifier | Legitimate interests (understanding what is read) |
We do not rely on consent for these purposes, so withdrawing consent is not a separate switch: closing your account ends the processing that depended on the contract, and the legitimate-interest purposes stop with it.
6. Analytics
Page views are measured with Umami, a privacy-oriented analytics tool that is designed to work without cookies: it counts a visit by a short-lived, salted hash derived from the request rather than by a stored identifier. It records the page, the referrer, the browser and the country, and it does not follow you to other sites.
The script is loaded from the analytics provider's domain (Umami Cloud by default, or the operator's own instance) and is the only third-party script on the site. The content security policy restricts what it may load and what it may connect to. Staff areas of the site are not measured.
7. Payments and e-mail
A payment leaves the platform before it is made. You are redirected to the payment provider's hosted page, where the provider collects what it needs and processes the transaction under its own privacy policy. It tells us the order reference, the status and the amount that actually arrived; we never receive a card number or a wallet secret.
We send transactional e-mail only: the code that completes a sign-up or an address change, the code that resets a password, moderation and payment outcomes, and renewal reminders for a plan you bought. There is no newsletter and no marketing list to unsubscribe from. Messages are rendered from templates and delivered through the mail relay configured by the operator.
9. Where the data is processed
The service runs on servers chosen by the operator, and the processors above may operate outside your country. Where data leaves the European Economic Area or the United Kingdom, the transfer relies on an adequacy decision or on the standard contractual clauses of the recipient, together with the technical measures described in the security section.
10. How long we keep it
| Record | Kept for |
|---|---|
| Account and profile | While the account exists, then through the deletion grace window (30 days by default) and anonymisation |
| Stories, chapters, comments | While published; after deletion they leave the catalogue and age out of backups |
| Orders and the coin ledger | As long as accounting and tax law requires |
| Payment provider events | A short period, kept to prove a callback was handled once |
| Copyright notices and moderation decisions | Long enough to show how a complaint was handled and to identify repeat infringement |
| Sessions, verification codes, rate-limit counters | Minutes to days; they expire on their own |
| Aggregate page-view statistics | In aggregate only; no profile is retained |
After the grace window the account is anonymised: the profile, the address and the content are removed or detached, and what remains is the record the law or an audit needs.
11. Your rights
Where the GDPR or UK GDPR applies you may ask for a copy of your data, correct it, delete it, restrict or object to its processing, and receive it in a portable format. Two of those are self-service and take effect immediately:
- Export — account settings downloads one JSON file containing your profile, your stories and chapters, your comments, your engagement, your money records and your notifications.
- Deletion — the same page closes the account. It needs your password and the word "delete"; see the Terms of Service for what closing removes and what it keeps.
For anything else — rectification of a record you cannot edit, restriction, an objection, or a request on behalf of somebody else — write to the privacy mailbox on the contact page. We answer within one month, and we may ask you to prove that the account is yours.
You may also complain to the data protection authority in your country. We would rather hear from you first.
12. How we protect it
- Passwords are stored as bcrypt hashes and are never logged or returned by the API.
- Session tokens live in httpOnly cookies, so a script on the page cannot read them, and the content security policy blocks inline and third-party script injection.
- The browser never calls the API directly: everything goes through the web layer that owns the cookies, and state-changing requests are checked for a same-origin origin and a JSON content type.
- Rate limits apply to sign-in, sign-up, codes, reports, tips and checkout, so a stolen address cannot be hammered.
- Integration credentials are encrypted at rest with a key that exists only in the deployment environment.
- Staff actions are written to an audit log, and privileged reads are recorded.
- Every response carries security headers; HSTS is sent when the deployment runs over HTTPS.
No system is perfect. If a breach affects your data, we notify the authority where the law requires it and tell affected accounts what happened and what to do.
13. Children
The service is for adults. We do not knowingly collect data from anybody under 18. Registration refuses a date of birth under that age, and an account that turns out to belong to a minor is closed and its data deleted. If you believe a minor has an account, tell us through the contact page.
14. Automated decisions
An automated reviewer may score a submission or a report and propose a decision. In the default mode its output is a recommendation that a human applies; only in the most permissive mode can it record the decision itself, and a human may reopen any case it decided. Copyright notices are never decided automatically. You can ask for a human review of any decision that affected your account through the contact page.
15. Changes to this policy
This policy is republished with a new version number and effective date when it changes. A material change is announced inside the service. The version you accepted when you created the account remains recorded.
16. Contact
Privacy questions and requests: the privacy mailbox on the contact page. Security reports: the security mailbox on the same page.