Concepts
Data residency and language
Where SignalDock stores and processes data, and how it picks the language and register for every prospect-facing text.
Where data lives
- Compute: every Vercel service runs in
fra1(Frankfurt), set in the rootvercel.json. - Database and auth: Supabase in an EU region. Integration and mailbox credentials are encrypted in Supabase Vault and are only readable with a secret key.
- AI: every model call goes through Vercel AI Gateway with
geoRegion: "eu", so requests are routed to EU inference endpoints where the provider offers them. Prompts never include credentials, and signal text is wrapped as untrusted data. - Mail: messages are sent from the customer's own Gmail or Microsoft 365 mailbox. SignalDock stores the message text and headers it needs for threading, not the rest of the mailbox.
Language and register
Every prospect-facing text (outreach, replies, footers) uses a resolved locale and formality:
- The contact's
localeandformality, when set. - The company's
locale(derived from its country when unknown). - The organization default in compliance settings (
nl-NL, formal).
Supported locales are nl-NL, nl-BE, fr-BE, de-DE, de-AT, and
en-GB. Formal is the default for Dutch, French, and German (u, vous, Sie);
English defaults to a plain register. Belgian Dutch prompts ask for Flemish
phrasing.
Last updated on