Privacy Policy
How Waggle collects, uses, and protects your data.
Effective on publication · Version 2026-09-01
1. The short version
- We do not read your writing. No employee, no contractor, no automated system that reports back to us.
- We do not train AI on it. We do not send it to any AI company. Ever.
- We do not sell your data. Not to anyone, for any price, in any form.
- We do not run ad trackers. No Google Analytics, no Meta pixel, no advertising networks.
- We collect a small amount of product usage data, which features get opened, not what you wrote, and in the EU and UK we ask permission first.
- You can export and delete everything in your own projects, yourself, from inside the app. Work you add to a project someone else owns lives in that project.
The detail is below, and the detail is the part that counts.
2. Who is responsible for your data
Del Rey LLC, a limited liability company organized in Tennessee, United States, operating as Waggle, is the controller of the personal data described here.
Privacy contact: privacy@getwaggle.app
3. What we collect, (a) Account data
When you create an account we collect your email address and a securely hashed password (we never see or store the password itself). Authentication is operated for us by Supabase. If you sign in with a third-party provider, we receive your email address and basic profile identifier from that provider, never your password there.
We also store your display name if you set one, your plan, and the version of our Terms you accepted and when.
3. What we collect, (b) Your content
Everything you write and upload: manuscripts, notes, worldbuilding, characters, links between pages, images, files, version snapshots, and the settings and themes of your projects.
We store it. We do not read it. It is stored so that we can give it back to you. It is covered by the strict, limited license in Section 6 of the Terms, and by the commitments in Section 5 below.
Uploaded files are held in private storage. They are not publicly readable; the app generates short-lived signed links so your browser can display them, and those links expire.
3. What we collect, (c) Billing data
Paid plans are processed by Stripe. Stripe collects and holds your payment card details directly, we never receive or store your card number. We store the identifiers Stripe gives us (a customer ID and a subscription ID), your plan, and its status, so we know what you are entitled to. Stripe handles that data under its own privacy policy, as an independent controller for fraud-prevention and legal-compliance purposes.
3. What we collect, (d) Product usage analytics
This is the only behavioral data we collect, and it is deliberately thin.
On the marketing website, before you have an account, we store a random identifier (a "visitor ID") in a first-party cookie on your device, and against it we record:
| What | Example |
|---|---|
| Which pages were viewed, and how many | /pricing, 4 page views |
| When you first and last visited | timestamps |
| Where you arrived from | referring site, utm_source / utm_medium / utm_campaign if present, and the first page you landed on, captured on your first visit only |
| Your browser’s user-agent string | Mozilla/5.0 … |
| Your country | US, derived at request time from network routing, not from a stored IP address |
| Whether you later signed up | if you create an account, we connect the visitor ID to your user ID so we can tell which marketing actually worked |
Inside the app, once you are signed in, we record product events. An event consists of: a name drawn from a fixed internal list (for example `notes.page_created`), which surface of the app it happened on, how long an action took, which project it belonged to, and your user ID. We also record session heartbeats so we can measure how long the app was actively in use.
What app analytics never contains: the text you wrote, page titles, character names, file names, search queries, or any free-form string of any kind. The event name must match a strict pattern and comes from a closed list in our code; arbitrary values are rejected by the server.
We do not store your IP address in our analytics records. Your IP is necessarily visible to our servers in transit, and is used transiently for rate-limiting and abuse prevention, but it is not written into our analytics tables.
3. What we collect, (e) Share-link view counts
When you publish a page to a public link, we count how many times it was opened and when it was last opened, and show you those numbers. We record no information about who opened it, no identifier, no IP, no location, no device details. We filter out obvious bots and link previewers so the number reflects people.
3. What we collect, (f) Support, feedback, and email
If you email us or use in-app feedback, we keep what you send and our reply so we can help you and remember the context. We send transactional email, password resets, receipts, security and policy notices, through Resend, which processes the recipient address and delivery status on our behalf. We record delivery failures and spam complaints so we can stop emailing addresses that bounce.
3. What we collect, (g) Technical and security logs
Our hosting provider generates server logs (request paths, status codes, timing, IP address, user agent) as an ordinary part of running a web service. We use them to diagnose faults and investigate abuse. They are short-lived and are not used to build a profile of you.
4. Cookies and similar technologies
| Cookie | Purpose | Category | Expires |
|---|---|---|---|
| Supabase auth tokens | Keeps you signed in; without them the app cannot work | Strictly necessary, no consent needed | Session / on sign-out |
| Waggle visitor ID | Distinguishes one website visitor from another for the analytics above | Analytics, consent-based | 12 months |
| Analytics consent record | Remembers your choice so we stop asking | Strictly necessary | 12 months |
We use no advertising cookies, no third-party trackers, and no cross-site tracking. We do not participate in any advertising network and we do not run Google Analytics.
Consent. In the EEA, the UK, and Switzerland, we ask for your consent before setting the analytics cookie, and analytics does not run unless you say yes. Elsewhere, analytics is on by default and you can turn it off at any time in the app. Wherever you are, you can change your choice at any time, and turning it off stops collection immediately.
5. What we never do
These are commitments, not descriptions of current practice that we might quietly change:
- We never use your content to train, fine-tune, or evaluate any AI or machine-learning model, ours or anyone else’s.
- We never send your content to a third-party AI service.
- We never sell your personal data, and we never "share" it for cross-context behavioral advertising as those terms are defined under U.S. state privacy laws.
- We never let our staff read your writing, except when you specifically ask us for support and only as far as that request requires. Access is logged.
- We never use your content for marketing, no quoting it, no screenshots of it, no showcasing it, unless you specifically and separately give us permission.
If we ever intend to change one of these, we will give you at least 30 days’ advance notice by email and you may close your account first. We will not apply any such change to content created before the change took effect.
6. Why we process it, and our legal basis
| What we do | Why | Legal basis (GDPR) |
|---|---|---|
| Run your account, store and serve your content | To provide the service you asked for | Performance of a contract |
| Take payment, manage subscriptions | To bill you for a plan you chose | Performance of a contract |
| Send transactional email | To operate the account and tell you about changes | Contract; legal obligation |
| Product analytics | To understand which features are used and improve them | Consent |
| Security, abuse prevention, rate limiting | To keep the service and its users safe | Legitimate interests |
| Respond to support requests | To help you | Legitimate interests; contract |
| Keep tax, accounting, and legal-claim records | Because we are required to | Legal obligation |
Where we rely on legitimate interests, we have weighed them against your rights, and you can object, see Section 10.
7. Who we share it with
We use a small number of service providers ("subprocessors"). Each is bound by a data-processing agreement, may use your data only to provide their service to us, and may not use it for their own purposes.
| Provider | What it does | Data it touches | Where |
|---|---|---|---|
| Supabase | Database, authentication, file storage | Account data, your content, uploaded files, analytics records | United States |
| Vercel | Application and website hosting | Requests in transit, server logs | United States |
| Stripe | Payment processing | Name, email, payment card, billing address, transactions | United States |
| Resend | Transactional email delivery | Email address, message content, delivery status | United States |
We will keep this list current. When we add a subprocessor that processes your personal data in a materially different way, we will update this page and, for material changes, notify you.
We also disclose personal data when: the law requires it (a valid subpoena, court order, or lawful request, and we will tell you unless legally forbidden); it is necessary to establish or defend legal claims; it is necessary to prevent imminent harm; or as part of a merger, acquisition, or sale of assets, in which case we will notify you and the acquirer remains bound by this policy or gives you notice before changing it.
We do not disclose your content in response to informal requests. We require lawful process.
8. When you publish
Publishing a page to a share link is a decision you make, and it takes that page outside the protections above: anyone with the URL can read it, and we cannot control what they do with it. We ask search engines not to index share links, and we serve them with instructions not to archive or snippet them, but we cannot guarantee every crawler complies. Revoking a link stops us serving it; it cannot retrieve copies other people already have.
Saving pages as a template. Anyone who may export a project can save pages from it as a template in their own account: the owner and Editors always, and Viewers only when the owner has allowed Viewers to export. A template is a copy. It holds the pages’ text and structure and, when a page has a Sheet, that sheet’s design and the values filled into it. It lives in the account of the person who saved it, not in the project, so it stays with them if they later leave the project or lose access to it, and removing a page from the project does not remove it from their template. Their saved templates are theirs to delete, and they are deleted with their account.
9. How long we keep it
| Data | Retention |
|---|---|
| Your content | Until you delete it, or 30 days after you close your account. What you add to a project someone else owns stays with that project until its owner deletes it (see Section 10). |
| Saved templates | Until the person who saved them deletes them, or 30 days after they close their account |
| Backups containing deleted content | Expire within 35 days on a rolling schedule |
| Account record | Deleted within 30 days of account closure |
| Website visitor analytics | 12 months from last visit |
| In-app product events | 24 months, then deleted or irreversibly aggregated |
| Share-link view counts | For as long as the link exists |
| Transactional email logs | 90 days |
| Server/security logs | 30 days |
| Billing and tax records | 7 years, as required by law, the one category we cannot delete on request |
| Support correspondence | 24 months |
10. Your rights
Everyone, wherever you live, can: export your own projects from inside the app at any time; turn product analytics off; correct your account details; and delete your account, which deletes the projects you own and everything in them.
Projects you don’t own. If you work in a project someone else owns, what you add there (pages, and your character sheet in a game master’s campaign) lives in that project. If its owner deletes the project, it is deleted right away. If its owner deletes their account, the project is deleted after a 30-day grace period. Either way, everything in it is deleted, including what you added, and we don’t notify members separately. If you delete your own account, you are removed from other people’s projects, and what you added there stays with each project until its owner deletes it. To keep your work, export it while you have access. Owners and Editors can export a project at any time. Viewers can export only when the project’s owner has turned that on.
If the GDPR or UK GDPR applies to you, you also have the right to: access your data and receive a copy; have inaccurate data corrected; have data erased; restrict processing; port your data to another provider in a machine-readable format; object to processing based on legitimate interests; and withdraw consent at any time (which does not affect processing already carried out). You may lodge a complaint with your national supervisory authority, in the UK, the Information Commissioner’s Office.
If you live in a U.S. state with a comprehensive privacy law, California, Colorado, Connecticut, Virginia, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Minnesota, Maryland, Tennessee, Indiana, Kentucky, Rhode Island, and others, you have the right to know what we collect, to access and delete it, to correct it, to obtain a portable copy, to opt out of sale, targeted advertising, and profiling with legal effects (we do none of those three in any case), and to appeal if we refuse a request. We will not discriminate against you for exercising any of these rights.
Global Privacy Control. We honor the GPC browser signal as an opt-out of analytics.
Sensitive data. We do not knowingly collect the categories that U.S. state laws or GDPR Article 9 treat as sensitive, and we do not ask for them. If you choose to write sensitive information into your own content, we hold it as we hold everything else, stored, never read, but please note that it is you, not us, choosing to place it there.
How to exercise a right. Email privacy@getwaggle.app from your account address, or use the in-app tools. We respond within 30 days (extendable once by 60 days where the law allows, and we will tell you if we need it). We may need to verify your identity, and we will ask for the minimum needed to do so. An authorized agent may act for you with written proof.
11. International transfers
We operate in the United States and our providers store data there. If you are in the EEA, the UK, or Switzerland, your data is transferred to the U.S. We rely on the European Commission’s Standard Contractual Clauses (and the UK Addendum, and the Swiss equivalent) with each provider, together with the technical measures described in Section 12. You can request a copy of the relevant transfer mechanism at privacy@getwaggle.app.
12. Security
We protect your data with: encryption in transit (TLS) and at rest; row-level database security so one account cannot reach another’s data; private file storage with expiring signed links; hashed passwords; least-privilege access for the very small number of people who administer the system, with content access excluded by default; and an automated test suite that checks these boundaries on every release.
No system is perfectly secure, and we will not pretend otherwise. If a breach affects your personal data and creates a risk to you, we will notify you and the relevant regulator within the time the law requires, 72 hours to the regulator under GDPR, and we will tell you what happened, what we know, and what to do.
13. Children
Waggle is for adults. You must be 18 or older to use it. We do not knowingly collect personal data from anyone under 18. If you believe a minor has given us personal data, email privacy@getwaggle.app and we will delete it and close the account.
14. Changes to this policy
We will update this policy as the product changes. For material changes, a new category of data, a new purpose, a new kind of recipient, we will give you at least 30 days’ notice by email and in the app before it takes effect. For minor corrections we will update the page and the effective date above. Previous versions are available on request.
15. Contact
Del Rey LLC
- Privacy: privacy@getwaggle.app
- Everything else: hello@getwaggle.app
If you are in the EEA or the UK and we are required to appoint a local representative, their details will be listed here.