Policies & support · Updated 29 October 2026

Privacy policy

Who is responsible

VeilPlume is an independent product operated in Sweden under the VeilPlume brand. The VeilPlume operator is responsible for personal information used to run the website, accounts and product support. Contact veilplumebookauthor@gmail.com for privacy questions or requests.

Your manuscripts and local storage

The writing workspace saves books, character notes, images and project history locally in your browser using browser storage. Imported manuscripts are processed on your device. VeilPlume does not provide cloud manuscript storage or automatic book syncing. The public demo uses temporary sample edits. If you choose to email material to support, that material becomes part of your support correspondence.

Your browser also stores preferences such as the selected theme. Offline setup can save app files on your device. Local books remain until you delete them or browser/device storage removes them. Export a backup before clearing site data. Account deletion does not itself remove files or browser data on your devices.

Accounts and sign-in

When you sign in with Google or Discord, our authentication provider, Supabase, processes your account identifier, email address, verification status and profile information supplied by the sign-in provider, such as a display name or avatar. We use your verified identity and session to authenticate you and check workspace access. We do not receive your Google or Discord password.

Session cookies and sign-in verification cookies support secure login. Blocking them can prevent sign-in. Signing out ends the local session; it does not delete your local books. Account information is kept while needed to provide your account and access, and deleted on a valid deletion request unless a legal obligation or unresolved dispute requires limited retention.

To document your agreement, we store your account identifier, the Terms version accepted and the acceptance timestamp in private Cloudflare storage. We retain this record while needed for your account and any related legal obligations or disputes. Contact us to request a copy or deletion.

Cart cookies

When you add VeilPlume to your cart, we set an essential cookie named __Host-vp_cart. It remembers only that product selection for up to 30 days in this browser. It does not contain a name, email address, manuscript or payment details. Removing the item deletes this cookie. Secure, HttpOnly and SameSite settings protect it. Sign-in cookies are managed separately; removing your cart does not sign you out or delete your books.

Optional visitor analytics are not currently enabled. If introduced, they will require a separate choice from accepting our Terms.

Website operation and security

Cloudflare hosts and protects the website. Website requests necessarily involve technical information such as IP address, requested URL, browser details, timestamps and error or security events. This information is used to deliver pages, investigate failures and prevent abuse. Operational records are retained only as needed for those purposes and any applicable legal obligations; provider retention depends on the service involved. Contact us for information about records associated with your account.

Support and payments

If you email us, we receive your email address, message and any attachments. We keep correspondence while needed to resolve the issue and handle related follow-up or disputes, then delete information no longer needed.

Purchases are currently disabled. When purchases through Paddle open, Paddle will process checkout, billing, tax, fraud-prevention and refund information under its own privacy notice. VeilPlume’s purchase system is designed to use account identifiers, transaction identifiers, purchase status and access records to grant or revoke workspace access. We do not store full card details. Transaction records may need to remain for accounting, dispute resolution and legal obligations after an account closes.

Why we process information

We rely on performance of a contract, or steps you request before a contract, for accounts, access and purchase support. We rely on legitimate interests in operating a reliable service, preventing abuse and responding to general enquiries for proportionate security and support processing. Legal obligations apply to required financial records. If we introduce optional processing that requires consent, we will request it separately. Accepting terms does not give blanket consent to unrelated uses.

Providers and international processing

Our providers include Cloudflare for hosting and security, Supabase for authentication, your chosen Google or Discord sign-in provider, and Gmail for email support. Paddle will handle payment transactions when enabled. These services may process information outside Sweden or the EEA. Where GDPR requires safeguards for international transfers, the relevant provider arrangements must provide an applicable transfer mechanism, such as an adequacy decision or standard contractual clauses. Contact us for details of safeguards relevant to your information.

Provider notices: Cloudflare, Supabase, Google, Discord and Paddle. Sign-in providers and Paddle also process information for their own purposes under their notices.

Your choices and rights

We do not sell your personal information or use your manuscripts for advertising. This site does not use advertising cookies. You can manage local preferences and cookies in your browser, but deleting site data can erase books permanently.

Depending on applicable law, you may request access, correction, deletion, restriction or a portable copy of personal information, and object to processing based on legitimate interests. Where processing is based on consent, you can withdraw it. Email veilplumebookauthor@gmail.com; we may need proportionate identity verification. You can complain to Sweden’s Authority for Privacy Protection (IMY) or your local supervisory authority. We do not use personal information to make automated decisions with legal or similarly significant effects; access checks enforce account permissions.

Changes

Last updated 29 October 2026. We will update this notice when our data practices change, including before new payment or optional tracking features are enabled.