Skip to content
Signal
How it works
Use cases
Online shopsAnswer the question before they leaveAgencies and servicesTurn visits into discovery callsLocal tradesUrgent jobs and quotes, each their waySoftware companiesDemos with the people who fitClinics and practicesNew patients, bookedEstate agentsFind the sellers among the browsersAccountants and lawyersThe urgent matters first
Resources
BlogGuides for small businessesCompare toolsSignal next to Leadfeeder, RB2B and othersWhitepaperThe whole product, to read or printDeveloper docsThe script, configuration, API and webhooks
Pricing
Sign in Get early access
How it works Pricing
Use cases
Online shopsAgencies and servicesLocal tradesSoftware companiesClinics and practicesEstate agentsAccountants and lawyers
Resources
BlogCompare toolsWhitepaperDeveloper docs
Get early accessSign in
Home/Privacy

Privacy Policy

This policy explains how We Do Dev Work Co., Ltd. ("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

We Do Dev Work Co., Ltd., 219/22 Sukhumvit 21 Road, Khlong Toei Nuea, Watthana, Bangkok 10110, Thailand, company registration and tax ID 0105568022029. Contact for privacy questions: hello@try-signal.com. 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

When you click "Start free trial", the site puts that same random ID in a cookie (signal_sv) for try-signal.com and its subdomains, kept for one day. The sign-up page reads it and stores it with your account, so we can see which visit led to your sign-up, your trial and your first payment. It holds nothing else, and nothing is set if Signal hadn't stored an ID. Legal basis: our legitimate interest in knowing which parts of our website bring customers.

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

From your IP address, at the moment of your visit, Signal estimates your rough location (country, region and city) and who owns your network, using a database on its own servers; the address isn't sent to anyone else. It uses this to tell people from automated traffic. If you allowed analytics, it also stores the rough location and, when the network belongs to an organisation (for example a company, bank or university, but never a home or mobile internet provider), that organisation's name, so the website's owner can see which organisation a visit came from.

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 as long as 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 United States
Stripe Payments Ireland / US
TypeSafe AI The model that estimates which visitors are ready. It gets pages, answers and facts, never the name, email or phone number we collect. United States
Mistral AI Wording of questions and offers (no visitor data); summaries of customers' public web pages during setup; matching a visitor's typed answer, or (if the customer turns it on) chat message, to the customer's options, with contact details masked EU (France)

The full list, with what each one handles, is at try-signal.com/subprocessors.

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.

Google Calendar

If you connect your Google Calendar to Signal (Settings → Team calendars), Signal uses it only to book calls with visitors to your organisation's website:

  • it reads when you're busy, to offer visitors free times; it doesn't read the titles, guests or contents of your events, and doesn't store your busy times
  • it creates the event a visitor books, with a Google Meet link and the visitor as a guest, and later checks only that event, to see whether it was moved or cancelled
  • it stores a token to do this, encrypted; you can disconnect at any time from Team calendars or from your Google account, and the token is deleted

Signal's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We don't use Google user data for advertising, don't sell it, and don't use it to train AI models.

AI assistants (Claude, ChatGPT)

An account holder can connect Signal to an AI assistant of their own, such as Claude or ChatGPT ("Sign in with Signal"). They choose the projects it may see, and can disconnect it at any time under Account → Connected apps.

  • The assistant gets what that person could see in Signal for those projects (numbers, what visitors did, and what they wrote, with email addresses and phone numbers masked), but never a visitor's email address, phone number, full name, company or postcode. It gets a first name at most.
  • It can prepare drafts in Signal. It can't publish them, send emails or chat replies, or change settings.
  • What the account holder asks, and what Signal answers, goes to that assistant's provider (for example Anthropic or OpenAI) under the account holder's own agreement with them. That provider isn't one of our sub-processors: the account holder chooses to use it.

Your rights

You can ask to see, correct, delete or export your data, or object to or restrict how we use it. Email hello@try-signal.com; we answer within one month. You can also complain to the data protection authority where you live or work.

Security

  • Passwords and sign-in links are stored only as one-way hashes.
  • Stored data is encrypted at rest by our database host (AES-256). Integration secrets are also encrypted separately.
  • Connections use HTTPS.
  • Access to production is limited to the people at We Do Dev Work who run the Service.

Changes

We'll post changes here and email account holders about important ones.

Last updated: 4 November 2026

Signal

Hosted in the EU (Frankfurt).

Product

How it worksPricingEarly accessWhitepaperDeveloper docsBlogAboutContact

Use cases

Online shopsAgencies and servicesLocal tradesSoftware companiesClinics and practicesEstate agentsAccountants and lawyers

Topics

Website visitor identificationLead qualificationHot leads from your websiteA popup that qualifies leadsGDPR-friendly visitor tracking

Compare

All comparisonsSignal vs LeadfeederSignal vs RB2BSignal vs SnitcherSignal vs AlbacrossSignal vs IntercomSignal vs Chili Piper
© 2026 Signal
TermsPrivacyData processingEditorial policyhello@try-signal.com
Proudly powered by We Do Dev Work