Privacy Notice

Effective: 2026-04-11 · Last updated: 2026-04-11

This Privacy Notice explains what walkindb collects when you use the hosted API at https://api.walkindb.com, why we collect it, how long we keep it, and your rights under the General Data Protection Regulation (GDPR).

The walkindb hosted Service is operated from Portugal by walkindb (the “Operator”, “we”, “us”), with infrastructure located in France (see §1.1 and §5 below). For the purposes of GDPR, the Operator is the data controller for personal data processed in connection with the Service.

Summary in plain language

If that’s all you need, you can stop reading. The rest of this document is the legally rigorous version.

1. Data we process

1.1 Access logs (the only personal data we process for the API)

Every request to https://api.walkindb.com results in one structured log entry containing:

FieldExampleWhy we collect it
timestamp2026-04-11T14:32:11ZOperations, debugging, and correlating with abuse reports.
source_ip198.51.100.42Rate limiting in real time, and abuse / subpoena response after the fact.
instance_id018f2b...a3Linking a complaint about a specific instance to the IPs that touched it.
http_methodPOSTOperational metrics.
http_status200Operational metrics and rate-of-error tracking.
sql_byte_length42Operational metrics; helps us understand load. The SQL text itself is not logged.
user_agentcurl/8.5.0Operational metrics; helps us understand who is using the Service.

What we explicitly do not log:

1.2 Walk-in instance contents

When you submit a query, the Service may create a SQLite database file under our control. The contents of that file are determined entirely by your queries. They are not read, indexed, mined, scanned, or analyzed by us. They exist on disk only for the lifetime of the instance (target: 10 minutes), after which the file is deleted.

We do not maintain backups of walk-in instance contents. We do not snapshot them. They are not replicated to any third party.

1.3 Email correspondence

If you contact us at [email protected], [email protected], [email protected], or [email protected], we will retain the contents of your message for as long as necessary to handle your request and to maintain a record of the matter. Email is processed by our email provider (currently a free or low-cost forwarding service; the specific subprocessor may change and will be listed in this notice when relevant).

1.4 Landing page (walkindb.com)

The landing page at walkindb.com is hosted on Cloudflare Pages. It currently uses no analytics, no cookies, and no third-party trackers. If we add a privacy-respecting analytics tool in the future, we will update this notice and disclose the tool here.

2. Legal basis for processing (GDPR Article 6)

We process the access-log data described in §1.1 on the following legal bases:

3. Retention

DataRetention
Access logs (§1.1)7 days from the timestamp of the request, after which entries are deleted by an automated job. Entries subject to a litigation hold or law-enforcement preservation request are retained until the hold is lifted.
Walk-in instance contents (§1.2)Approximately 10 minutes from instance creation (the TTL); deleted by the Service automatically.
Email correspondence (§1.3)As long as necessary to handle the matter and to maintain an institutional record, typically up to 2 years for abuse and security correspondence.

4. Sharing and disclosure

We share the personal data described in this notice only in the following circumstances:

We do not sell personal data, do not share personal data with advertisers or data brokers, and do not use personal data for training machine-learning models.

5. International transfers

Our primary infrastructure is in France (European Union). Cloudflare’s DNS service is provided from the United States and other jurisdictions; Cloudflare is certified under the EU-US Data Privacy Framework, and our use of Cloudflare is limited to DNS-only resolution (no proxying of API traffic), which keeps the personal data we send them to a minimum.

6. Your rights under GDPR

If you are in the European Economic Area, you have the following rights with respect to your personal data:

To exercise any of these rights, contact [email protected]. Be aware that, because we collect the minimum necessary data and retain it for only 7 days, our ability to identify “your” data is limited to the IP address you provide in your request and to log entries that are still within the retention window at the time we receive your request. For requests about data older than 7 days, we will most likely no longer hold the data at all.

We will respond to verifiable requests within 30 days of receipt, in line with GDPR Article 12(3).

7. Children

The Service is not directed at children under the age of 16. We do not knowingly collect personal data from children under 16. If you believe a child has used the Service in a way that involves personal data being collected, please contact [email protected] and we will delete the relevant log entries.

8. Security

We protect the access logs described above with industry-standard measures: minimum-privilege OS user, no public network exposure for the log store, log rotation and automatic deletion, and security hardening of the host (firewall, automatic security updates, no password authentication for SSH). We will publish the bullet-point version of our hosting controls in SECURITY.md in the open-source repository.

No security model is absolute. The single most effective protection for your data is to not store anything sensitive in walkindb in the first place. This is why the AUP forbids storing personal data about identifiable third parties in walk-in instances.

9. Changes

We may update this notice. Material changes will be reflected in the “Last updated” date at the top and announced in the walkindb changelog. We will not retroactively expand retention or share previously collected data in ways inconsistent with the notice that was in effect when the data was collected.

10. Contact

We do not yet have a designated Data Protection Officer (DPO); the Service does not currently meet any of the conditions in GDPR Article 37(1) that would require one.