On this page
CoconutDB ("the Platform") is a collaborative backend platform developed and operated by CoconutDB. It allows teams to design and manage data tables, control access permissions, track data changes, automate workflows, and expose REST APIs — all through a unified interface.
This Privacy Policy applies to all users of the CoconutDB platform, including Global Administrators, Workspace Admins, Editors, and Viewers. By accessing or using the Platform, you agree to the collection and use of information described in this policy.
This policy covers only data processed within the CoconutDB platform itself. Data stored in tables, documents, and workspaces that you create belongs to your organisation. CoconutDB acts as a data processor for that content, not a data controller.
CoconutDB collects data in three broad categories: account data you provide directly, operational data generated as you use the platform, and technical data collected automatically.
Account & identity data
- Profile information: full name, display name, email address, mobile number, date of birth, gender, and profile image URL.
- Authentication data: hashed password, TOTP 2FA secrets, session tokens, and JWT authentication records.
- Location & contact: street address, city, postal code, state/region, and country — provided optionally in your profile.
- Workspace membership: the workspace(s) you belong to, your assigned role, and the date you joined.
Operational & platform data
- Records you create, edit, or delete in data tables, including all field values and version history snapshots.
- Files and documents you upload to the Document Vault or attach to table records via File Picker columns.
- Automation workflow definitions, JavaScript code blocks, and trigger configurations you author.
- Webhook endpoint configurations, email dispatcher SMTP credentials, and developer API key metadata.
- Row-Level Security (RLS) policy expressions applied to your workspace tables.
Technical & audit data
- IP address, browser type, and device information collected at login and during active sessions.
- Full API call logs: timestamp, HTTP method, endpoint path, originating user, and response status code.
- Rate-limit events when a user account is blocked for exceeding 30 API calls within a 30-second window.
- Record version history: field changes, old value, new value, timestamp, and responsible user.
We process your data only to operate, secure, and improve the CoconutDB platform. We do not sell, rent, or trade personal data to third parties for advertising or commercial profiling purposes.
| Purpose | Data used | Basis |
|---|---|---|
| Authentication & access control | Email, hashed password, 2FA secret, session token | Contract performance |
| Delivering platform features | Table records, vault documents, workflow scripts, webhooks | Contract performance |
| Workspace audit trail | Version history, activity logs, API call logs | Legitimate interest |
| Rate limit protection | API call frequency, IP address | Legitimate interest |
| Transactional email delivery | SMTP credentials, recipient address | Contract performance |
| Platform security & fraud prevention | IP address, login attempts, blocked account records | Legitimate interest |
| Profile personalisation | Display name, profile image, contact details | Consent |
All CoconutDB data — including table records, vault files, and user credentials — is stored in a PostgreSQL database. Workspace data is physically isolated per workspace (tenant), meaning records from one workspace are never accessible to another.
Technical safeguards
- Passwords are stored as cryptographic hashes and are never transmitted in plaintext.
- All API calls require a valid Bearer token (JWT) that expires after a fixed period.
- Developer API keys are shown only once and are never stored in recoverable plaintext.
- Document Vault files are stored as encrypted binary objects inside PostgreSQL.
- TOTP two-factor authentication is available and recommended for administrator accounts.
- Domain whitelisting enables workspace admins to restrict API access to authorized origins.
Organisational safeguards
- Access to production systems is restricted to authorised CoconutDB personnel.
- Role-based access control limits what any user can read or modify within a workspace.
- Row-Level Security (RLS) policies can restrict data access at the individual record level.
- The Global Admin default password must be changed immediately after first login.
- Failure to change defaults or enable 2FA exposes platform-wide administration to unauthorised access.
CoconutDB enforces a layered access model. Each layer determines what a user can see and do within a workspace.
| Role | Scope | Personal data accessible |
|---|---|---|
| Viewer | Read-only access to table records and vault documents within a workspace. | Own profile, workspace member list (names and roles only) |
| Editor | Create, update, soft-delete, and restore records; upload vault documents. | Same as Viewer, plus authorship metadata on created records |
| Admin | Full workspace control: schema, members, deletes, API keys, webhooks, automation, and RLS. | All workspace member profiles, full activity logs, API key names |
| Global Admin | Platform-wide user management across all workspaces. | All registered user profiles, workspace memberships, and activity history |
Only the Global Admin can block or permanently delete user accounts platform-wide. Workspace Admins can manage roles inside their own workspace only.
CoconutDB issues two types of credentials for API access. Both carry significant security implications and are governed by this policy.
JWT session tokens
Issued automatically at login. Tokens are time-limited and expire after a set period. They are scoped to the authenticated user’s role and workspace membership.
Developer API keys
Long-lived static keys generated by Workspace Admins for server-to-server integrations, scheduled jobs, and automation scripts. These keys carry Admin-level privileges and do not expire unless explicitly revoked.
- API keys are displayed only once at generation.
- CoconutDB does not retain a recoverable copy.
- You are responsible for secure storage using environment variables or a secrets manager.
- Never commit keys to source code. Compromised keys must be revoked immediately.
CoconutDB maintains a real-time activity log for every workspace. This log records API calls, user actions, and system events to support security monitoring and audit requirements.
- Timestamp, HTTP method, endpoint path, and response status for every API call.
- The authenticated user responsible for each action.
- Rate limit breach events and the account that triggered the block.
- Record creation, update, and deletion events in per-row version history.
- Document Vault uploads and deletions.
- Workspace member additions and role changes.
Workspace activity logs are accessible to Workspace Admins and the Global Admin. Viewers and Editors cannot access workspace logs. Individuals may see the version history of records they are permitted to read.
To protect platform stability, CoconutDB automatically blocks any user account that makes 30 or more API calls within a 30-second window. Blocks expire after 5 minutes. Persistent violations may be escalated to the Global Admin.
CoconutDB supports integrations with external systems through webhooks, the Email Dispatcher, and Automation Workflows. When you configure these features, data may be transmitted to third-party systems you control.
Webhooks
When a webhook is triggered, CoconutDB sends a JSON payload containing event details and relevant record data to the external URL you configure. You are responsible for the privacy and security practices of the receiving system.
Email Dispatcher (SMTP)
The Email Dispatcher stores the SMTP credentials you provide. These credentials are used solely to send emails on your behalf. CoconutDB does not use your SMTP credentials for any other purpose and does not read the content of emails sent through the Dispatcher.
Automation Workflows
Workflows execute custom JavaScript that you author. This code runs server-side within the CoconutDB environment and may make outbound HTTP calls to external APIs. You are responsible for ensuring any external services handle data appropriately.
CoconutDB is not responsible for the data handling practices of external systems that receive data via webhooks, Email Dispatcher, or Automation Workflows.
Data is retained for as long as your account or workspace is active, plus a defined period after termination to allow dispute resolution, legal obligations, and data recovery requests.
| Data type | Retention period | Deletion method |
|---|---|---|
| Active table records | Until soft-deleted by authorised user | Moved to Recycle Bin; hard-deleted by Admin |
| Soft-deleted records | Until purged by Workspace Admin | Permanently removed on Purge action |
| Version history | Retained for the lifetime of the record | Removed when the parent record is hard-deleted |
| Vault documents | Until deleted by Workspace Admin | Permanently removed on delete |
| Activity & API logs | 90 days rolling window | Automatic expiry |
| User accounts | Until deleted by Global Admin | Platform-level deletion |
| Developer API keys | Until revoked by Workspace Admin | Manual revocation; key becomes invalid immediately |
Depending on your jurisdiction, you may have rights over the personal data CoconutDB holds about you. CoconutDB respects these rights and will respond to valid requests within applicable legal timeframes.
- Right to access: request a copy of the personal data we hold about you.
- Right to rectification: correct inaccurate or incomplete personal data via My Profile.
- Right to erasure: request deletion of your personal data, subject to legal constraints.
- Right to portability: receive your personal data in a structured, machine-readable format.
- Right to object: object to processing based on legitimate interest, including activity logging.
- Right to restriction: request that processing of your data is limited in specific circumstances.
To exercise any of these rights, contact us at the address in Section 13. We will verify your identity before processing any request. Requests will be fulfilled within 30 days.
CoconutDB is a professional backend platform intended for use by organisations and adult individuals in a business context. The platform is not directed at, and we do not knowingly collect personal data from, anyone under the age of 18.
If you believe a person under 18 has registered an account or provided personal data through the platform, please contact us immediately using the details in Section 13 so we can remove the data and close the account.
CoconutDB may update this Privacy Policy from time to time to reflect changes to the platform’s features, applicable law, or our data practices. When we make material changes, we will:
- Update the "Last updated" date at the top of this page.
- Where feasible, notify active workspace administrators via in-platform notification or email at least 14 days before changes take effect.
- For significant changes affecting how we use your personal data, seek fresh consent where required by applicable law.
Continued use of the CoconutDB platform after the effective date of an updated policy constitutes your acceptance of the changes.
If you have questions about this Privacy Policy, wish to exercise your data rights, or need to report a privacy concern, please reach out through the following channels.
General privacy enquiries
privacy@coconutdb.comPlatform administrator
admin@coconutdb.comCompany
CoconutDB
Response time
We aim to respond to all privacy requests within 5 business days.
For security vulnerabilities or suspected data breaches, please email us with the subject line [SECURITY]. We treat such reports as high priority.
This document constitutes the complete Privacy Policy for the CoconutDB platform. It supersedes any previous versions.