Data Processing & Residency

This deployment runs against a single PostgreSQL database, in whatever region the operator has provisioned it — there is no per-organization or per-region data placement in the codebase today. Every organization’s data is logically isolated (scoped by organizationId on every real table) within that one database, not physically separated by region.

Query text and analyzed content sent to a configured AI provider (see /legal/subprocessors) is processed by that provider under its own infrastructure and region, which SignalOS does not control.

Real EU-region processing would require, in order:

• An EU-region PostgreSQL instance (or a second, EU-region deployment of this same application) — a genuine infrastructure decision, not a code change.
• A real mechanism to assign an organization to a region at signup and route its data there — this does not exist in the schema today (no Organization.dataRegion field, no per-region connection routing in src/lib/db.ts) and would be new work.
• Confirming which configured AI providers and data connectors (see /legal/subprocessors) offer their own EU-region processing option, since SignalOS calling a non-EU provider’s API would still move data outside the EU regardless of where SignalOS’s own database lives.
• Standard Contractual Clauses or an equivalent transfer mechanism for any remaining non-EU subprocessor, drafted by counsel.

None of this is built. This is a scope statement for a real future project, not a claim that it exists.

A signed-in organization owner can see the deployment’s real retention window and request permanent deletion of their organization’s content from Setup → Export Data → Data retention & deletion. See that page for the real, current retention period and exactly what permanent deletion covers.

A signable Data Processing Agreement, Standard Contractual Clauses for international transfers, the specific legal basis for each processing activity under GDPR/CCPA, and a data-subject-request process (access, rectification, erasure requests coming from an end consumer rather than the organization itself) are not present here and should not be assumed. Those require a licensed attorney.