Skip to content
Privacy

What we collect, what we don't, where it lives.

Signal Studio is built by a small team. The data discipline matches the brand discipline: less, named, accountable. This page tells you what we hold, who else touches it, and how to take it back.

Last updated 2026-08-12

What we collect

Signing in to a Signal Studio product creates an account through Clerk, our authentication provider. Clerk stores your email, name (if you provide one), and an opaque user identifier. We never see your password.

Inside each product, we store the work you create: tasks, notes, timeline items, briefing preferences. We store who made what, who shared what with whom, and when. We do not store anything you didn't enter yourself.

Planning Period and Workspace context stores the label, context type, calendar dates, timezone and archive/order state you choose. Context changes the language and grouping; it is not a permanent account role.

Where a school or venue sponsors access, we keep entitlement, invitation and activation records. Sponsorship does not give the sponsor access to private Notes, Tasks or unpublished Timeline material. Optional Workspace metadata is shared with a sponsor only through a separate, field-level consent you can revoke.

The school design-partner experience does not require or store pupil accounts, pupil names, pupil emails, grades, attendance or pupil identifiers.

If you reach out to hello@signalstudio.ie, we keep the message in a standard email inbox.

AI actions

A few places in the products offer an AI action you can choose to run: drafting a reply, summarising a thread, separating a dictated note into its parts, reading text out of a photo you attached. Nothing runs on its own. Nothing runs in the background.

When you run one, the specific text or resized image shown in the review step is sent to Anthropic to answer that single request, and nothing is sent before you confirm it. If you never run an AI action, nothing you write ever reaches a model.

Voice dictation uses the speech recognition service built into your browser or device, not one of ours. That service may process the microphone audio outside Signal Studio, under its provider's terms rather than ours. Signal Studio receives the transcribed text and never receives or retains the audio.

What we don't collect

No third-party advertising trackers. No fingerprinting. No session replay. No marketing pixels. No behavioural profiling.

Nothing you write is used to train a model, ours or anyone else's. Notes, tasks, timeline items and dictated text are not training data. The AI actions above run against Anthropic's commercial API, which does not use API inputs or outputs to train models.

We use Vercel Analytics for anonymous traffic counts (which pages got visited, from which country, on which device class). It does not set cookies and it does not see your account.

Product-learning events use counts, enums and booleans. We do not send Note or Task text, class/module/couple names, pasted values, pupil data or public-link tokens. Audience Timelines do not carry third-party behavioural tracking.

Where data lives

Account records: Clerk (United States). Workspace and product data: Turso (managed libSQL, primarily Frankfurt). Error reports: Sentry (United States, with personal data scrubbed before send). Static hosting and serverless functions: Vercel (United States and edge regions).

Product-event counts: PostHog EU cloud (European Union). AI actions: Anthropic (United States), per request, for that request only.

Outbound mail (briefing emails and operator notifications) is sent through Resend.

Our subprocessors are listed below. We will update this list before adding a new one.

Subprocessors

Clerk, authentication.

Turso, application database.

Vercel, hosting, edge functions, anonymous analytics.

PostHog (EU cloud), product analytics. Events are sent from our servers and keyed to your account identifier. No PostHog script runs in your browser and no PostHog cookie is set.

Anthropic, the model behind the AI actions. It receives only what you confirmed for that action, only when you run one.

Sentry, error monitoring (PII scrubbed at the SDK before transmission).

Resend, outbound email delivery.

Stripe, payments for paid plans, when applicable. Stripe stores card details; we never see them.

Google Workspace, operator email at hello@signalstudio.ie.

Cookies

We set cookies for sign-in sessions and first-party product preferences such as the active Workspace. No marketing cookies. No third-party trackers that need consent banners.

Analytics run server-side, so they set no cookie at all. There is no analytics tag on any page of this site.

Your rights

If you are in the EU, EEA, or UK, the GDPR gives you the right to access, correct, export, restrict, or delete the personal data we hold about you. Send a request to hello@signalstudio.ie from the address on the account. We respond inside thirty days, usually faster.

If you are in California, the CCPA gives you parallel rights. Same address, same response time.

You can also close your account at any time and your data will be deleted within sixty days, except records we are required to retain (billing, fraud prevention).

Data retention

We keep your data while your account is active. When you close the account, we delete it within sixty days. Backups age out inside ninety days.

Billing records and tax records are retained for as long as Irish tax law requires.

AI actions keep nothing on our side beyond the result you asked for and the record that a request was made.

Changes to this policy

If we change this policy, we will say so on the changelog at signalstudio.ie/dispatch and date the change here. Material changes will be announced by email to active accounts.

Contact

Questions, complaints, data requests: hello@signalstudio.ie. The address is read by a person.

The data controller is Ethan McNamara, Limerick, Ireland.

No dark patterns, no buried clauses. If something here is unclear, that’s a bug, write to hello@signalstudio.ie and we’ll fix the wording or the system.