Trust and security
What we do with your data, and what we do not.
Tidewater reads metadata about your pipelines. This page lists how we protect it, where it lives, who else touches it and whether the service is up right now.
Tidewater is a fictional company. The practices below show what a trust page should contain and are not certifications or promises you can rely on.
Service status
Updated . Read from status.json.
All systems operational
- API 99.99% over 90 days
- Data ingestion 99.96% over 90 days
- Alert delivery 99.97% over 90 days
- Web application 100% over 90 days
- Webhooks 99.98% over 90 days
12-month uptime: 99.97%. Each bar is one day, oldest on the left.
Recent incidents
- Alert delivery 24 minutes
Delayed alert delivery to some Slack channels
A change to how we batch outgoing messages delayed some Slack alerts by up to 9 minutes. We reverted the change and added a delivery delay check that pages the on-call engineer after 2 minutes.
- API 41 minutes
Elevated API latency
A slow database query raised median API latency from 90 ms to 600 ms. We added an index and a query time limit. No requests failed.
- Data ingestion 1 hour 12 minutes
Ingestion backlog in the EU region
A collector restart left run events queued for about an hour. All events were processed in order and no data was lost. Freshness checks were paused during the backlog to avoid false alerts.
Practices
How we protect it.
Access
- Single sign-on with SAML or OIDC on Business and Enterprise
- Multi-factor authentication required for every employee
- Production access is time-limited, approved by a second person and logged
- API tokens are scoped to one workspace and stored hashed
Data
- Metadata only: names, types, counts and times, never table contents
- TLS 1.2 or newer in transit, AES-256 at rest
- Customer data stays in the region you choose
- Deletion on request within 30 days, backups within 35
Operations
- Daily encrypted backups with a restore test every quarter
- Independent penetration test every year, summary shared under NDA
- Incident response runbook, practised twice a year
- Dependency and container scanning on every change
Assurance
- SOC 2 Type II examination in progress, report expected next quarter
- Data processing agreement on every plan, see the DPA
- Security questionnaire answered within five working days
- Vulnerability reports welcome at security@saas.phoenixcodes.org
Data residency
Your data stays in the region you choose.
Each workspace lives in one region. Metadata is not copied to another region, and support staff outside the region see it only with your approval.
| Region | Location | Plans |
|---|---|---|
| United States | US East, northern Virginia | All plans |
| European Union | EU Central, Frankfurt | Business and Enterprise |
| Asia Pacific | AP Southeast, Singapore | Business and Enterprise |
Subprocessors
Who else touches your data.
We list the kinds of provider we use and what each one sees. We give 30 days notice by e-mail before adding one.
| Provider | Purpose | Location | Data involved |
|---|---|---|---|
| Primary cloud provider | Hosting, compute and object storage for the Tidewater platform | United States, Germany, Singapore | All customer metadata, in the region chosen |
| Managed database provider | Primary relational database for workspaces and alerts | United States, Germany, Singapore | Workspace configuration, alert history |
| E-mail delivery provider | Sending alert e-mails and the morning digest | United States | Recipient address, alert text |
| Chat delivery APIs | Sending alerts to Slack, Teams, PagerDuty and Opsgenie on your behalf | As set by each service | Alert text, only for channels you connect |
| Support desk software | Handling support requests and demo requests | United States | Name, work e-mail, company, message |
| Error monitoring service | Finding and fixing faults in the web application | Germany | Stack traces without customer data |
Common security questions
- What data does Tidewater read from my warehouse?
- Metadata only: table names, column names and types, row counts, last update times, and query logs for lineage. Tidewater does not read the contents of your tables unless you write a custom SQL check, and even then it stores the result of the check, not the rows.
- Where is my data stored?
- Business and Enterprise workspaces can be placed in the United States, the European Union (Frankfurt) or Asia Pacific (Sydney). Free and Team workspaces are in the United States. The region is chosen when you create the workspace.
Send us your security questionnaire
We answer within five working days, and a person on the security team reads every one.