This policy explains what Tidewater Data, Inc. (“Tidewater”, “we”) does with personal data. It covers this website and the Tidewater product. Tidewater is a fictional company, and this page is written as a real one would be, for a demonstration site.
Who we are
Tidewater Data, Inc. is registered at 14 Seawall Lane, Floor 3, Portland, Maine 04101, United States. For questions about this policy write to privacy@saas.phoenixcodes.org. We have no data protection officer requirement under the law that applies to us, but Jonas Weber, our Head of Security, answers privacy requests.
What we collect on this website
Demo requests. When you use the contact form we collect your name, work e-mail address, company, company size, the number of pipelines you want to monitor and your message. We use them to reply to you and to prepare for a conversation. We keep a request for 24 months, or until you ask us to delete it.
Newsletter. If you subscribe, we collect your e-mail address. We use it to send the product newsletter, about once a month. Every message has an unsubscribe link, and unsubscribing deletes your address within 30 days.
Rate limiting. To stop abuse of our forms we count how often a network address submits them. We do not store the address itself. We store a keyed hash of it, together with a time, and delete these records after 24 hours.
Logs. Our hosting provider keeps standard request logs for up to 30 days to run and secure the service. Our own application logs contain a request identifier and an outcome, never names, e-mail addresses or message text.
We do not use advertising cookies, analytics cookies or tracking pixels on this website. The only item this site stores in your browser is your theme choice (light or dark), kept in local storage on your device and never sent to us.
What we collect in the product
When you use the Tidewater product, we process the following on behalf of your organisation:
- Account data: name, work e-mail address, role and sign-in events for each user.
- Metadata about your data systems: pipeline names, run times, table and column names and types, row counts, and the text of SQL statements read from query logs.
- Alert data: which alerts were sent, to whom, and who acknowledged them.
We do not read the contents of your tables unless you create a custom SQL check, and then we store the result of the check and not the rows. Our data processing agreement describes this in detail, and your organisation is the controller of this data.
Why we use personal data
We use personal data to provide and secure the service, to reply to you, to send messages you asked for, to meet legal obligations and to improve the product using aggregated, non-identifying usage figures. We rely on contract, legitimate interests, consent (for the newsletter) and legal obligation as the legal bases, depending on the case.
Who we share it with
We share personal data only with the subprocessors listed on our trust page, and only as needed to provide the service. We do not sell personal data. We may disclose data when the law requires it, and we will tell the affected customer first unless we are prohibited from doing so.
Where it is stored
Product data is stored in the region you choose when you create a workspace: the United States, the European Union or Asia Pacific. Website data is stored in the United States. When data is transferred across borders, we use standard contractual clauses.
Your rights
Depending on where you live, you can ask us to give you a copy of your personal data, correct it, delete it, restrict or object to its use, or move it to another service. Write to privacy@saas.phoenixcodes.org. We reply within 30 days. If we cannot help, you can complain to your local data protection authority.
Security
We encrypt data in transit and at rest, limit access to people who need it, and test our defences every year. The trust page describes our practices. No system is perfectly secure, and if a breach affects your data we will tell you without undue delay.
Children
Our website and product are for businesses. They are not directed at anyone under 16, and we do not knowingly collect their data.
Changes
If we change this policy in a way that matters, we will update the date at the top and tell newsletter subscribers and customers by e-mail at least 30 days before the change applies.