Legal
Privacy
These documents are templates under review. They are not legal advice. Provider details follow once the company is registered.
We keep personal data to a minimum.
Website and tool pages
We do not set cookies on ambolt.dev and we do not use third-party analytics or third-party scripts. We keep a simple request log without IP addresses or user-agent strings: the page or tool, the referring site, the country, and whether the request looks automated. It tells us which pages and tools are used. Cloudflare, our network provider, processes connection data (such as the IP address) to deliver and protect the service. If we ever suggest another language or currency, we use the country Cloudflare reports for the request; it is not stored.
Free online link check
When you check a page, we fetch that page and the links on it, and stream the results back to you. The one-check-a-day limit uses your IP address, held in memory for that day only and not stored. The request log records that a check ran, without the address you entered.
Ambolt Link Checker plugin
The WordPress plugin stores its results in your own database and contacts only the links it checks. It sends nothing to Ambolt unless you connect it to an account (see the next section). Reports you download are yours.
Ambolt Link Checker cloud app (applies when the web app opens)
This section describes the cloud app at app.ambolt.dev/lc. It applies from the day the web app opens to the public; until then none of it is in use. For customers who need one, the data processing agreement sets out the processor terms for the page data below.
What we store, why, and on what legal basis
| Data | Purpose | Legal basis (GDPR Art. 6) |
|---|---|---|
| Account e-mail address, display name, country, sign-in records, session records | Run your account, sign you in, send alerts and reports | Contract (1)(b) |
| Sites you add: address, host, how you proved ownership, scan frequency, alert settings | Check the sites you chose, on the schedule you chose | Contract (1)(b) |
| Scan results: the link addresses found on your pages (mail, phone and script links are not stored), the page each was found on, the anchor text (shortened), the status, the HTTP code and when it was last checked. We never store page bodies. | Show you which links are broken and where to fix them | Contract (1)(b) |
| Plugin reports: plugin and WordPress version, counts and the top broken links, sent by a connected plugin | Show the plugin's result in your account | Contract (1)(b) |
| API keys: a one-way hash, a short prefix and last four characters, scopes, site binding and dates. The key itself is shown once and never stored. | Let a connected plugin or script use your account | Contract (1)(b) |
| Alert log: which alert e-mail went to which address and when | Avoid repeating alerts, show you what was sent | Legitimate interests (1)(f) |
| Security and audit log: events with a hashed e-mail address, country and browser family | Detect misuse and keep the service secure | Legitimate interests (1)(f) |
| Billing records from the merchant of record: provider ids, plan, amount, currency, status, dates. Card details are handled by the merchant of record and never reach us. | Run subscriptions, keep accounts of our sales | Contract (1)(b); legal obligation (1)(c) for bookkeeping |
| Abuse reports from site owners: host, reporter e-mail, message | Honour requests to stop checking a site | Legitimate interests (1)(f) |
| Anonymous free check: a one-way hash of your IP address salted per day, the checked host and a counter. The address itself is not stored. | Enforce one free check a day and a daily cap per target host | Legitimate interests (1)(f) |
Link addresses and anchor text on a customer's pages can contain personal data about third parties (a name in an address, for example). We process them for the customer, as set out in the data processing agreement, and only to report link status. Our checker also sends one request to each link target; the owner of that site sees our address and our user agent, AmboltLinkChecker/1.0. How it behaves, and how a site owner can ask us to stop, is explained on the site owners page.
Retention
- Scan results: deleted 30 days after the link was last checked (a link that is still checked stays current).
- Removed sites and everything under them: 30 days after removal.
- Plugin reports: 30 days.
- Anonymous check counters: 2 days. Spent or expired connect codes: removed within a day. Revoked or expired API keys: removed after 90 days.
- Alert log: 90 days. Raw payloads of billing events: emptied after 90 days.
- Abuse reports: the reporter's e-mail address and message are removed 90 days after the report is handled; the record of the host stays for a year.
- Billing records (provider ids and amounts, no card data): kept for as long as bookkeeping law requires, and detached from your account when you delete it.
Export and erasure. In your account you can download everything we hold about it as a JSON file (Export my data), and delete the account. Deleting stops all checks and revokes your API keys at once. For 7 days you can undo it by signing in again; after that the account, your sites, results, keys and sign-in are erased for good. We cannot delete an account while a paid subscription is active; cancel it first (see the refund and cancellation policy). Bookkeeping records are the one thing we are required to keep.
Developer endpoints and MCP
We process the request you send and the public wallet address that pays, which is visible on the blockchain anyway. We keep request counts and payment records for accounting and to detect abuse. The free call on tool pages is limited per IP address per day; the address is held in memory for that purpose and not stored.
Accounts (app.ambolt.dev)
If you create an account we store your e-mail address, a salted Argon2id hash of your password (never the password), your sign-in methods (for Google sign-in only Google's account identifier; we keep no Google access tokens), session records, and a security log of sign-ins with a hashed e-mail, country and browser family. We use cookies there only to keep you signed in. Customer settings and usage counters for a tool are stored only when you use that tool.
Support
If you write to hello@ambolt.dev (or to support@ or security@ once those addresses are live) we keep the message and our reply to answer you and to keep a record. Replies are written under the product name.
CRA File tools and waitlist
The free tools under /cra run in your browser: what you type or the SBOM file you open is not uploaded. The only exception is the button that checks components against the public OSV database, which sends package names and versions to api.osv.dev when you press it. We count how often each tool is used, without any identifier. If you join the waitlist we store your e-mail address, the product and the date, only to tell you when the product launches. You can remove your address yourself on the CRA File page. We delete the list after the launch message or after 12 months, whichever comes first.
Telegram bot
The bot @ambolt_power_bot stores your Telegram chat id, the alerts, watched addresses, tender searches and watched pages you set, to send them to you. Send /stop to remove your alerts. Payments in Stars are handled by Telegram.
Apify Actors
Runs and inputs are processed on the Apify platform under Apify's terms and privacy policy.
Processors
| Processor | What for | Where |
|---|---|---|
| DigitalOcean | Hosting of the website, API and the Link Checker cloud app | Frankfurt, Germany (EU) |
| Cloudflare | Network, DNS, tunnel and e-mail routing | Global network |
| A merchant of record | Card payments, sales tax and VAT, receipts, refunds for the cloud plans | To be named here when billing opens |
| Resend | Alert, report and sign-in e-mail from the web app | EU region; to be named as live when the web app sends mail |
| Sign-in, if you choose it | Global | |
| Telegram | Bot messages and Stars | Global |
| Apify | Actors | Under Apify's terms |
We tell you about a new processor on this page and in the changelog before it is used for personal data.
Retention (everything else)
Account data is kept while the account exists and deleted on request; security logs for 12 months; support tickets for 24 months; the request log for 90 days. The retention periods for the Link Checker cloud app are listed in its section above.
Your rights
You can ask what we hold about you, ask us to correct or delete it, ask for a copy, object to processing based on legitimate interests and complain to your data protection authority (in Denmark, Datatilsynet). Cloud app account holders can export and delete their data themselves. Otherwise write to hello@ambolt.dev; we answer within 30 days. Because we hold little, most requests are answered by deleting an account or a Telegram chat id.
Provider
Provider details follow once the company is registered. Contact: hello@ambolt.dev.