Legal
Privacy Policy
What personal data NamiDB collects about account holders and visitors, why, for how long, who receives it and how to exercise your rights.
- Last updated
- Version
- 2026-11-02
- Questions
- info@namidb.com
Contents
01Who we are and what this policy covers
NamiDB, Inc. (“NamiDB”, “we”, “us”) is a Delaware C Corporation that operates NamiDB Cloud, a managed graph database service, from Quito, Ecuador. This Privacy Policy explains how we handle personal data about the people who visit app.namidb.com, create an account, belong to an organization, are invited to one, or contact us.
For that data, NamiDB is the controller (under the EU and UK GDPR and the Swiss FADP), a “business” (under the California Consumer Privacy Act as amended by the CPRA) and the responsable del tratamiento (under Ecuador’s Ley Orgánica de Protección de Datos Personales, “LOPDP”).
The marketing website at namidb.com may publish its own notice for anything it collects that is not described here.
02Personal data we collect
You give it to us
- Account details: your name, email address and password. We store the password only as a salted hash (bcrypt) in our own authentication service; at sign-up we check it against known breached passwords using a k-anonymity range query to Have I Been Pwned, which sends only the first five characters of the password’s SHA-1 hash, never the password.
- Sign-in with GitHub or Google, if you choose it: the provider sends us your email address, name, profile picture URL and a provider user ID. Your profile picture is loaded from the provider when the console shows it.
- Organizations and members: organization names and slugs, your role (owner, admin or member), and the email addresses of people you invite.
- Billing details: the billing contact’s name, email, address and tax ID, and your payment method. You enter payment details directly on pages hosted by Stripe; we receive only a reference, the card brand, last four digits and expiry, never the full card number or security code.
- Correspondence: what you write to us at info@namidb.com or through the console, and our replies.
- Support requests: when you open or answer a support request (in the console, through the management API or by replying to one of its emails): its subject, category, severity, the database it is about, your messages and ours, and the files you attach (screenshots, logs, query plans and the like, up to 3 per message). Every member of the organization can read its requests. An attachment holds whatever you put in it, which can include extracts of your data, so attach only what we need to help. Requests and their attachments are stored with your account records in the account database we operate ourselves, not with a helpdesk vendor; like the rest of that database, they are included in its encrypted backups (see “How long we keep it”). The emails about them are delivered by our email provider.
- Consent records: which version of the Terms of Service and this Privacy Policy you accepted, when, from which IP address and browser user agent.
- Enterprise inquiries, if you send one through the contact-sales form (with or without an account): your name, work email, company, role, company size, what you are interested in and your message.
- Policy-update subscriptions, if you sign up on the Subprocessors page to hear about changes to our subprocessors and policies (no account needed): your email address and when you confirmed it.
Collected as you use the Service
- Authentication and security records: sign-in events, session records (IP address, user agent, times), verification and recovery codes (single-use, valid 15 minutes, stored hashed), failed attempt counters used for rate limiting, and the cookies described in the Cookie Policy.
- API key metadata: each key’s name, prefix, role, scope, expiry, creator and when it was last used. The secret part of a key is never stored, only a keyed hash.
- Usage Data: per organization and database, hourly counts of read and write requests, errors, bytes transferred, latency and stored bytes. It describes how much the Service is used, not what is in your data.
- Audit log: actions taken in an organization (for example creating a database, revoking a key, changing the plan) with the member who took them and when.
- Service logs: the Service logs requests (time, path, status, request ID and, for console traffic, client IP address and user agent) and errors; one-time tokens are redacted from logged URLs. Logs never contain passwords, API keys, cookies or request bodies.
We do not use analytics, advertising or tracking cookies, pixels or SDKs, we do not buy personal data, and we do not collect special categories of personal data about you.
03How we use it and our legal bases
Under the GDPR, the UK GDPR and the LOPDP (Art. 7) we must have a legal basis for each use. This is what we do and why:
| Purpose | Data | Legal basis |
|---|---|---|
| Create and run your account and organizations; sign you in; provide the console, the data plane and support | Account details, organizations and members, API key metadata, authentication records, correspondence, support requests and their attachments | Performance of our contract with you (GDPR Art. 6(1)(b); LOPDP Art. 7(5)) |
| Meter usage, enforce plan limits and the spend cap, bill and collect fees, keep accounting and tax records | Usage Data, billing details, invoices | Contract; legal obligation for tax and accounting records (Art. 6(1)(c)) |
| Send transactional email: verification and sign-in codes, password recovery, invitations, receipts, usage and limit warnings, security and service notices, changes to our terms | Name, email address, account and organization state | Contract; legitimate interests in keeping you informed about your service (Art. 6(1)(f)) |
| Send product-update emails about NamiDB Cloud to organization owners and admins, until they turn them off | Name, email address, role | Legitimate interests in telling customers about the service they use (Art. 6(1)(f)); you can object at any time |
| Answer Enterprise inquiries and prepare agreements | What you send through the contact-sales form, our correspondence | Steps at your request before entering into a contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) |
| Notify subscribers of subprocessor and policy changes | Email address, confirmation record | Consent, given by confirming the subscription (Art. 6(1)(a)); you can withdraw it with the link in every message |
| Protect the Service: prevent fraud, abuse, spam sign-ups and attacks; rate limiting; investigate incidents; enforce the Terms and the Acceptable Use Policy | Authentication and security records, service logs, IP addresses, Usage Data | Legitimate interests in securing the Service and our customers (Art. 6(1)(f)) |
| Operate, troubleshoot and improve the Service, using aggregated Usage Data and error reports | Usage Data, service logs, error reports | Legitimate interests in a reliable product (Art. 6(1)(f)) |
| Comply with sanctions and export laws: refuse sign-ups, sign-ins and purchases from countries under comprehensive U.S. sanctions, and purchases with a billing address in those countries or in sanctioned regions (a person reviews some regions); screen billing names against the U.S. Treasury’s sanctions list | IP address (its country only, looked up in a database we keep ourselves, so it is not sent to anyone), billing name and address | Legal obligation (Art. 6(1)(c)); legitimate interests in complying with the sanctions laws that bind us (Art. 6(1)(f)) |
| Record your acceptance of the Terms and this policy | Consent records | Legal obligation and legitimate interests in proving the agreement |
| Comply with law, respond to lawful requests, establish or defend legal claims | Any of the above, as needed | Legal obligation; legitimate interests (Art. 6(1)(c), (f)) |
Where we rely on legitimate interests we have weighed them against your rights; you can object (see “Your rights”). We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you. Automated safeguards such as rate limits, the spend cap and abuse filters block requests, never accounts, without human review. The exception is what sanctions law requires: sign-ups, sign-ins and purchases from comprehensively sanctioned countries (as the IP address’s country shows), and purchases with a billing address in such a country or in the Crimea region, are refused automatically. A billing address in another sanctioned region, and a possible match against a sanctions list, are only flagged for a person to review.
Country lookups use IP Geolocation by DB-IP, licensed under CC BY 4.0.
Organization owners and admins receive occasional product-update emails about NamiDB Cloud. They are on by default and can be turned off at any time in your account’s email settings or with the unsubscribe link in each of them. We send no other promotional email, and if we ever offer a newsletter it will be opt-in. Service emails are part of the Service and cannot be switched off while you have an account.
05International transfers
NamiDB is a U.S. company operated from Ecuador, and our service providers are mainly in the United States. Your account data is therefore processed in the United States, in Ecuador and wherever our service providers process it. Customer Content is stored in the storage location assigned to each organization when it is created.
When we transfer personal data out of the EEA, the United Kingdom or Switzerland, we rely on:
- the European Commission’s Standard Contractual Clauses (Decision (EU) 2021/914), with the UK International Data Transfer Addendum and the Swiss adaptations, between NamiDB and its providers, and the EU–U.S. Data Privacy Framework (and its UK and Swiss extensions) for providers certified under it;
- for data we receive as a processor, the Standard Contractual Clauses incorporated in our Data Processing Addendum.
Transfers out of Ecuador rely on the adequate safeguards of LOPDP Article 57: binding contractual commitments that guarantee a standard of protection equal to or higher than Ecuadorian law, with effective remedies for you. You can ask us for a copy of the relevant safeguards at info@namidb.com.
06How long we keep it
| Data | Kept for |
|---|---|
| Account details, organizations and memberships | While your account exists; deleted when you close it (organizations after their recovery period) |
| Organizations you delete | Purged, with their stored data, databases and backups, after a 30-day recovery period |
| Customer Content when a paid subscription ends | Kept: the organization moves to the Free plan, and databases beyond its limits become read-only until you upgrade or delete some |
| Customer Content when we end the Terms (other than your own deletion) | 30 days to export, then deleted from live systems within 30 further days |
| Service logs and metrics | 30 days |
| Security logs (access, sign-in and request logs, which contain IP addresses) | 90 days, for security and abuse investigations |
| Sanctions screening results and their review | While the organization exists, then for as long as sanctions record-keeping rules require |
| Encrypted control-plane backups (which contain account data) | 30 days, rolling |
| Verification and recovery codes | 15 minutes, single use |
| Rate-limiting counters | The length of their window (at most 1 hour), then dropped |
| Usage Data | While the organization exists, as the billing history shown in the console |
| The audit log (actions, the account or key that took them, IP address and user agent) | 365 days from each event, including after its organization is deleted (kept apart, for security and abuse investigations). Deleting your account removes your email address, IP address and user agent from it |
| Invoices and billing records | 7 years, for tax and accounting law |
| Consent records | While your account exists and for the limitation period for claims afterwards |
| Correspondence | 3 years after the conversation ends, unless needed longer for a claim |
| Support requests, their messages and attachments | 3 years after the last message of a request that is no longer open, then deleted automatically; earlier when their organization is deleted (at the end of its recovery period) |
| Enterprise inquiries | 24 months after the last update unless they lead to an agreement, then as part of that customer’s records |
| Policy-update subscriptions | Until you unsubscribe; a sign-up never confirmed is deleted after 14 days |
After deletion, data may survive in encrypted backups until they roll off. We keep information longer only when the law requires it or to establish, exercise or defend legal claims, and then only for that purpose.
07How we protect it
We protect personal data with technical and organisational measures appropriate to the risk: encryption in transit on every public connection, encrypted off-site backups, hashed passwords and API keys, row-level access control in our database, least-privilege access for our staff with two-factor authentication, and continuous monitoring. The Security page describes them in detail. No system is perfectly secure; if a breach affects your personal data, we will notify you and the competent authorities as the law requires.
08Your rights
Depending on where you live, you have some or all of these rights over your personal data. We extend the core rights (access, correction, deletion, portability) to every user, wherever they live.
European Economic Area, United Kingdom and Switzerland
Access; rectification; erasure; restriction of processing; data portability; objection to processing based on legitimate interests; withdrawal of consent at any time where we rely on it; and the right to lodge a complaint with your local supervisory authority (in the UK the Information Commissioner’s Office, in Switzerland the Federal Data Protection and Information Commissioner).
California and other U.S. states
The right to know the categories and specific pieces of personal data we collect, the sources, purposes and the recipients; to delete; to correct; to opt out of the sale or sharing of personal data (we do neither); to limit the use of sensitive personal information (we use your account credentials only to sign you in, a permitted purpose); and not to be discriminated against for exercising these rights. You may use an authorized agent, who must show your signed permission. In the past 12 months we collected the categories described in “Personal data we collect”: identifiers, customer records, commercial information (plans and invoices), internet or network activity (logs, usage), professional information (your organization) and account login credentials, from you, your devices and your organization’s members, for the purposes above, and disclosed them only to the recipients above.
Ecuador
Under the LOPDP you have the rights to information, access, rectification and updating, deletion, objection, portability, suspension of processing and not to be subject to decisions based solely on automated assessments (Arts. 12–20). We answer within the 15-day term the law sets. If you are not satisfied, you can complain to the Superintendencia de Protección de Datos Personales.
How to exercise them
Many of these you can exercise yourself: update your name in the console, export Customer Content through the API, delete organizations and your account. For anything else, email info@namidb.com from the address on your account. We may ask for information to verify your identity, and we answer within one month (GDPR), 45 days (CCPA) or 15 days (LOPDP), extendable where the law allows, free of charge unless a request is manifestly unfounded or excessive.
09Children
The Service is for developers and businesses and requires users to be at least 18. It is not directed to children, and we do not knowingly collect personal data from anyone under 16 (or under 13 in the United States, under COPPA). If you believe a child has given us personal data, email info@namidb.com and we will delete it.
10Do Not Track and Global Privacy Control
We do not track you across websites and do not sell or share personal data, so there is nothing for a Do Not Track or Global Privacy Control signal to switch off. We treat a Global Privacy Control signal as a valid opt-out request where the law requires it.
11Changes to this policy
We will update this policy when our practices change. The version date at the top shows when it last changed. For material changes we will email account holders and show a notice in the console at least 30 days before they take effect, and where the law requires your consent we will ask for it.
12Contact
Questions, requests and complaints about privacy: info@namidb.com. By post: NamiDB, Inc., Diego de Almagro, Quito 170102, Ecuador. Phone: +593 99 298 9693.
We aim to resolve every concern directly; you can always also contact your data protection authority.