Forklore privacy policy
Version: 20261119-privacy-v6. Date: 19 November 2026.
Controller and scope
Orlando de Jesús Hurtado Valdés, a sole trader established in Spain, trading as WhisperDev and Forklore. Spanish tax ID: Z1390335J; VAT ID: ESZ1390335J. Address: Salgueira, 36204, Vigo, Pontevedra, Spain. Email: forklore@whisperdev.es. Public customer service telephone: +34 614 70 61 20. Product website: https://forklore.whisperdev.es/.
This policy explains how we process your data when you use Forklore on Android and on the web.
Data and purposes
To create and protect your account, we process your email, identifier, credentials managed by Supabase, declared date of birth and region, session and preferences. Your date of birth is used for minimum ages and filters; it is not published in your profile. Age is not generally verified through identity documents. Your profile may include your chosen display name, username, avatar, biography and tags.
We process your stories, scenes, proposals, comments, images and other contributions to save them, display them according to their visibility, attribute them and enable collaboration. Drafts and personal libraries are private; workshops are shared with their guests. Published content and your visible profile may be seen and copied by their recipients. Do not publish other people's personal data without a lawful basis.
Votes, favourites, follows, searches, progress and reading events help recover your activity and order content according to your choices. Searches are sent to the service to resolve them and may appear in technical logs; they are not promised never to be stored. Editorial statistics are aggregated and do not display groups of fewer than five readers. Feed personalisation does not make solely automated decisions with legal or similarly significant effects.
We process support messages, reports, moderation decisions and necessary technical information, such as IP address, device and error or access logs, to handle requests, prevent abuse and protect accounts and content. Authorised operators access only what their role needs. We do not ask for passwords or security codes by email.
For purchases, we process provider identifiers, account, plan, interval, status, amounts and contractual documentation. Stripe processes web purchases, including Link for Managed Payments transactions; Google Play processes Android purchases. Link handles its checkout, transaction documents, account and payment support under its own policy. Forklore does not receive or store your full card number. Payment providers also process data under their own policies for payment, security and compliance obligations.
When someone invites you to a workshop, we process the email or username supplied, host identity, workshop, personal link, expiry and your response to handle the invitation. We send a transactional email and, if you already have an account, an Inbox notice and push when enabled. Inviting by @username does not reveal your email to the host. The link does not grant access without verifying the intended account; acceptance is explicit. Invitations and their delivery records are periodically deleted after 30 days. Accepted membership remains for as long as appropriate for workshop access. We do not use invitations for marketing campaigns.
Legal grounds
Providing the service you request and taking steps before an agreement support account management, publication, collaboration, libraries and subscriptions. Legal obligations support tax documents, data rights and official requests. Our legitimate interests in protecting the service and resolving incidents support proportionate security, fraud prevention and moderation, with particular regard to minors. You can request information and object where the law allows.
Consent is used for optional functions where required, such as device notifications and non-essential advertising, and for AI uses presented with a specific notice. You can withdraw consent prospectively without affecting earlier lawful processing. Necessary access, security, purchase and renewal emails are not optional marketing. Creating an account does not enrol you in marketing campaigns.
External sign-in providers
Choosing Google gives us its account identifier, email and available basic profile, such as name and avatar. We do not receive your Google password or access Gmail, Drive or Calendar. You can use email and password without Google. Apple sign-in will only be offered where enabled; it may use a private relay email and can be revoked through Apple. Different accounts are not linked merely because their emails look similar.
Artificial intelligence
OpenAI API receives the narrative context needed for suggestions, summaries, publication safety review or covers. We do not add your email, date of birth or account profile; personal data you put into a text may nevertheless be included. Avoid doing so. We record the AI notice version and declared region to apply the minimum age: 14 in Spain and 16 in the other regions supported by this flow. Purchases remain restricted to adults aged 18 or over.
Creative assistance is optional. Publication requires safety review; if the provider fails or the result is unclear, content is not automatically published. Filters are not error-free and you can request human review of a moderation decision. AI responses may be incorrect and are not professional advice.
Voluntary training sharing is disabled in the OpenAI organisation and text requests use store:false. This does not mean zero retention: abuse-prevention logs may exist under the relevant service terms. Exclusive EU residency is not claimed. You can read without using AI tools.
Notifications, storage and advertising
Enabling notifications stores a delivery token or address. Android uses Firebase Cloud Messaging; the web uses Web Push where available, and iOS will require its compatible service when enabled. Notifications may display the name of a followed story, event and destination link, including on your lock screen according to system settings. They do not include private draft text. You can disable them in Settings or your operating system; completing removal may require a connection.
Local, session and file storage maintain access, preferences, reading position, drafts, authorised downloads and pending offline actions. Uninstalling or clearing local storage can remove copies not yet synchronised.
Real advertising is disabled. Android includes Google AdMob (Google Mobile Ads) and its UMP consent platform, with test inventory separated from real inventory. If advertising is enabled, requests are limited to Free accounts with a known adult age, safe-content preferences and a returning session. No requests are made for minors, unknown ages or Plus/Creator plans, including complimentary access. Reading and voting do not require accepting advertising.
Consent status is updated before requesting ads. In the EEA, UK and Switzerland you can consent, refuse or manage options; we do not request ads if required consent is declined. Where applicable, you can review or withdraw your choice through “Ad privacy” in Settings. Failure to obtain permission prevents a request. Outside those territories, applicable regional choices and configured restrictive signals are used.
AdMob receives technical data such as IP address —which may be used to infer approximate location—, device information and supported identifiers, ad interactions and diagnostic data to deliver ads, measure their operation and prevent fraud. Requests disable personalisation and use restricted processing; this does not mean that no personal data is processed. This build does not request Android's advertising identifier (AD_ID) or GPS permission; other identifiers, such as App Set ID, may exist. We do not supply your email, date of birth, drafts or story text to AdMob for ad targeting. Google explains its processing at https://policies.google.com/technologies/partner-sites and https://policies.google.com/privacy.
AdSense is a separate web integration, usable only when enabled and after any required consent through a certified platform; it is not embedded in Android's WebView.
Providers, recipients and international transfers
Cloudflare hosts and protects the server; Supabase supplies the database, storage and authentication; Resend delivers email and Zoho Mail manages support; OpenAI supplies AI functions; Firebase/Google delivers notifications, Google Play verifies purchases, and Google AdMob/UMP manages advertising and privacy choices where applicable. Providers act as processors where they follow our instructions and may be independent controllers for services they operate themselves, such as payments or their accounts. Data may be disclosed to authorities where legally required or professionals who need it for tax obligations and legal claims.
The main Supabase database is in its configured European region. This does not mean every provider, subprocessor or support operation is EU-only. Processing outside the European Economic Area requires a valid transfer basis, such as an applicable adequacy decision or standard contractual clauses with the necessary safeguards. You may request information about providers and safeguards applicable to your data. We do not sell personal data.
Retention and deletion
We retain account information and content as needed to provide the service or until deletion under its functions. Draft versions are limited to 90 days and reading activity to 12 months; ad attempts to 7 days; completed AI usage reservations to 2 months; the operational email queue to 30 days; and Stripe technical transport events to 90 days. Periodic cleanup may run after a window expires; immediate deletion from every system is not promised.
These windows do not remove tax transaction documents or evidence needed for claims. Such information is blocked or access-restricted for applicable statutory periods and outstanding liabilities; OSS records may require ten years. This does not extend a public profile or justify retaining all account content for tax purposes. Providers and backups have their own retention and recovery cycles; restored data must reapply relevant deletion requests.
You may request account deletion or deletion of specific data without closing the account, through Settings or the contact address. Ownership is checked proportionately. Pending purchases and subscriptions are coordinated before closure. Parts of collaborative works may remain disconnected from the profile where needed for continuations and other authors' rights; your rights and legal retention grounds will be assessed. A work is not considered anonymous if its content still identifies you.
Rights and complaints
Where applicable, you can request access, rectification, erasure, restriction, portability and objection, and withdraw consent. Email forklore@whisperdev.es identifying your request and account; do not send identity documents unless, after considering alternatives, they are needed to resolve reasonable identity doubts. We normally respond within one month, subject to legally permitted extensions and explanations for complex requests.
You may complain to the Spanish Data Protection Agency, https://www.aepd.es/, or the competent authority where you live. The service is not directed at children under 14. Contact us about an underage account or a risk to a minor so it can be reviewed. The current version and material changes are communicated through appropriate channels. This policy does not grant ownership rights in your works.