Privacy Policy
Draft for legal review, 2026-09-30. Not yet in force. Placeholders are in [square brackets].
This policy explains how [WDDW legal name] ("we") handles personal data for Signal ("the Service"):
- the dashboard and accounts
- billing
- Signal's own website
If you visited a website that uses Signal: that website's owner decides how your data is used. Read their privacy policy. We process that data only on their behalf and on their instructions, under a data processing agreement. See "If you visited a website that uses Signal" below.
Who we are
[WDDW legal name], [address], [Chamber of Commerce (KvK) number]. Contact for privacy questions: [privacy@domain]. We have [not] appointed a data protection officer.
What we collect and why
| When | What | Why (purpose) | Legal basis (GDPR art. 6) |
|---|---|---|---|
| You create an account | Name, email address, password (stored only as a one-way hash), which version of the terms you accepted and when | To give you an account and keep it secure | Contract (6.1.b) |
| You use the dashboard | One sign-in cookie (signal_admin, 14 days, HttpOnly), sign-in sessions, your projects, team memberships and roles, settings |
To provide the Service | Contract |
| You're invited to a team | Your email address, who invited you, for which project | To let you join | Contract, and our customer's legitimate interest (6.1.f) |
| You create your first project | A 14-day trial starts | To let you try Signal | Contract |
| You choose a plan | Plan, trial dates, Stripe customer and subscription IDs. Card details go directly to Stripe; we never see them. | To bill you | Contract; legal obligation for invoices (6.1.c) |
| You use "Read my website" in setup | We fetch up to 20 public pages of the address you enter. A summary (emails and phone numbers masked) goes to our text-model provider to suggest your setup. Nothing fetched is stored. | To set up the Service | Contract |
| We email you | Confirmations, password resets, invitations, usage and trial notices | To run your account | Contract |
| Something goes wrong | Error reports without request contents, cookies or user data, with emails and phone numbers masked | To keep the Service working | Legitimate interest |
| You visit Signal's website or ask for early access | See "Signal's own website" below |
We don't sell personal data, and we don't use your data to train AI models.
Signal's own website
Signal's website runs on Signal itself. While you browse, it records:
- the pages you view and how long you stay
- where your visit came from (for example a search engine or a link)
- your answers to its questions
- a random visitor ID in your browser's session storage, forgotten when you close the tab
It doesn't write your IP address to its database or logs. It uses the address for the moment of your request (to estimate your country and city, and to check for spam), and keeps it in memory for up to an hour only to stop abuse. When you send a form, it keeps a one-way code made from your IP address for two days, only to stop spam; the code can't be turned back into your address.
When you request early access, we receive your name, email address, website and answers. We use them only to contact you about early access and to set Signal up with you. Legal basis: your request (pre-contract, 6.1.b), and our legitimate interest in answering it.
If you visited a website that uses Signal
The website's owner (our customer) is the controller. Signal, on their behalf:
- records your visit
- may ask you a short question
- stores contact details only if you give them
Signal doesn't write your IP address to its database or logs. Under our agreement with them, we don't use this data for anything else. To exercise your rights, contact the website's owner. If you contact us, we'll pass your request on to them.
How long we keep it
- Account data: while your account exists. You can delete your account yourself in the dashboard (Account → Delete account). It's removed at once with the projects you pay for. A running plan is cancelled first, after you confirm, and your customer record at Stripe is deleted. Stripe keeps payment and invoice records for 7 years, as Dutch tax law requires.
- Sign-in sessions: 14 days.
- Links in emails: they work for 24 hours (email confirmation), 1 hour (password reset) or 7 days (invitations).
- Early-access requests: page views and other events 3 months; your contact details and the outcome 12 months; everything else about your visit is deleted once you haven't visited for 12 months, or sooner if you ask.
Who else receives data
We use these service providers (sub-processors). Each is bound by a contract that protects your data:
| Provider | For | Location |
|---|---|---|
| Amazon Web Services | Hosting | EU (Frankfurt) |
| Supabase | Database | EU (Frankfurt) |
| Resend | Sending our emails | [to confirm] |
| Stripe | Payments | Ireland / US |
| Sentry | Error reports (optional) | [EU] |
| Typesafe | The model that estimates which visitors are ready. It gets pages, answers and facts, never the name, email or phone number we collect. | [to confirm] |
| [Text model provider] | Wording of questions and offers (no visitor data), and summaries of customers' public web pages during setup | [to confirm] |
The current list is also at [link to sub-processor list].
When data goes outside the EU/EEA, we rely on an adequacy decision (such as the EU-US Data Privacy Framework) or the EU's standard contractual clauses.
Your rights
You can ask to see, correct, delete or export your data, or object to or restrict how we use it. Email [privacy@domain]; we answer within one month. You can also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or the authority where you live.
Security
- Passwords and sign-in links are stored only as one-way hashes.
- Stored data is encrypted at rest by our database host [to confirm in Supabase's DPA]. Integration secrets are also encrypted separately.
- Connections use HTTPS.
- Access to production is limited to [who].
Changes
We'll post changes here and email account holders about important ones.
Last updated: [date]