Privacy policy

Which personal data we process, why, for how long and who else receives it, in plain words. If anything is unclear, write to us.

Last updated November 6, 2026.

Who is responsible

The company named below is responsible for the personal data described here. For any data-protection matter, write to the contact email.

Company
Amnalith LLC

When you run an audit

You give us your client’s domain, the list of addresses, the published text and, if you wish, the vendor’s name, how many outlets you were promised and where that is written. We use them only to run the check you ask for and to show you the result. We publish neither your client, nor your vendor, nor your list. The result lives at a link that is hard to guess: anyone who has the link can see it, so share it only with people you choose.

To limit abuse of the free service we keep a scrambled (hashed) form of your IP address and of the audited domain, only to count how many audits arrive within a short window. We do not keep your IP address for this purpose in clear.

When you buy the branded report

You pay by card on the payment provider’s secure page, which asks for your business details (name, billing address, tax ID) and email; we never see your card number. We keep the payment confirmation and the invoice, the brand details you enter for the report, and the evidence that you confirmed you buy for your business: the sentence you accepted, the language, the date, your IP address and your browser. We email you a receipt with the link to your report.

When you order a package or sign in

When you order a press release package, we keep your email address, your company’s name and website, the texts you send (the headline, your release or your answers, and any changes you ask for), the draft we write, each step of the order with its date, the version of the terms you accepted, the evidence that you buy for your business, and the payment references from our payment provider, Stripe. We never see or keep your card number. We use them to deliver your order, to show it in your account, and to account for the sale. We send your release, with your company’s name and link, to a newswire, which publishes it on news sites. Once published, it is public and each site controls its copy.

On Premium we draft your release with help from an AI writing tool, which receives your answers for that purpose.

Why we may use it: to carry out your order, to keep the records the law requires, and to keep the service safe.

Your account is your email address. When you ask to sign in, we email you a link that works once, for 20 minutes; we keep only a fingerprint (hash) of it. Signing in sets one cookie, which keeps you signed in for 30 days or until you sign out. It is strictly necessary for the account to work and is used for nothing else, so it needs no consent. To stop abuse, we count sign-in requests per email address and per connection for a short time.

An order that is not paid is canceled after 30 days and deleted after 90. An account with no orders, no plan and no workspace left is deleted after 90 days. Invoices and payment records are kept as long as tax law requires. The texts of a paid order are kept for two years after the order ends, then deleted; the results of our checks keep only the few short phrases we used to recognize your release on news sites. Sign-in links work for 20 minutes; a sign-in lasts 30 days.

Our payment, email and hosting providers process data in the countries where they run their services. Where the law requires safeguards for a transfer to another country, we rely on the ones it provides, such as standard contractual clauses. Stripe handles card payments as an independent controller; our email provider sends messages on our behalf.

When you use the API or the console

If you open an API account, we keep: your account (email address, organization, country and, if you give one, a tax number) and the business-use confirmation with the version, date and language of its wording and the IP address and browser used to confirm it; your keys (a scrambled copy, the first characters so you can tell keys apart, and the dates they were made and last used); your top-ups and what each call cost, with the payment references from Stripe; a log of each call (time, key, route, the identifier of what you asked about, result code and how long it took), which never holds the body of a request, its headers, the address you asked about, your key or your IP address; the page addresses, texts and CSV files you send and the results; and your webhook settings (the address you give and a secret that signs our messages) with a record of each message we sent and whether it arrived. We use them to run your account and your checks, to bill correctly, to show you proof reports and to find and stop abuse. Why we may use it: to carry out the contract, to keep the records the law requires, and to keep the service safe and know who we sold to.

How long we keep it, for the API and the console: the call log, 90 days; the IP address stored with a business-use confirmation, 30 days, after which it is removed; webhook messages and delivery records, 30 days; results and re-check history of a live check, 12 months after it finished; the text you sent for a check, 30 days after it finished; proof reports you made, 24 months; everything made in test mode, 30 days; ended scheduled checks, 90 days after they end, and the text of an ended scheduled check, 30 days after it ends; revoked keys, 24 months; an account that never paid or published, together with its details, 12 months after its last activity. After 24 months a proof report’s share link stops working and its PDF is deleted; its results then follow the 12-month rule. Invoices, top-ups, credit statements and the business-use confirmations of an account that paid are kept as long as tax law requires. If publishing through the API opens, a release and our notes on it are kept as for package orders.

The addresses and texts you send may identify your own clients. We use them only to run your checks. We never show them to anyone else, and nothing from your checks goes into a list shared across customers or into a public list.

Who receives it: Stripe (payments; it also acts for itself), our hosting provider, the provider that delivers our emails, our accountant, and public authorities when a law obliges us. Results and webhook messages go to the address you set; if that is in another country, that is a transfer you ask for. If publishing through the API opens, your release, with your company’s name and link, goes to a newswire, which publishes it on news sites. Once published, it is public and each site controls its copy. Monthly proof emails are sent through our email provider on behalf of the agency.

When you use a workspace with other people

A workspace can have several people, each with a role: owner, admin, member, billing or read-only. For each person we keep their email address, name, role, when they joined and last signed in, their sessions and devices, and the actions they take in the workspace. We use them to run the sign-in, keep the service safe, show who did what, and account for the sale. Why we may use it: to run and secure the service for the organization the person works for, and to keep the accounting records the law requires.

We decide why and how sign-in and security details are used. The organization that owns the workspace decides what it does with its people’s roles, with who can see what, and with its clients’ details, and we act on its instructions for those. Each role sees only what it needs about colleagues. A member sees colleagues’ names and roles. Owners and admins also see email addresses, when someone last signed in, and the record of actions. Nobody sees another person’s devices or IP addresses.

When someone is invited, we send them one email at the request of the person who invited them, telling them who invited them, why, and how we use their details. We send no automatic reminders; the person who invited them can send the same email once more. If they do not accept within 7 days the invitation and the address are deleted 30 days later. If they choose “this is not for me”, we keep a scrambled copy of the address for 12 months to refuse repeat invitations. Before accepting, a person sees that every action they take in the workspace is recorded with their name.

When a person is removed or asks us to delete their details

Their access ends at once. What they made stays with the workspace. In the workspace’s record of actions their name is replaced by “Former member” and the link between that label and the person is deleted. If they belong to no other workspace we delete their sign-in details after 90 days, or at once if they ask. A record of a money action keeps only an internal number, for as long as tax law requires.

Who at PressProve can see your data

The people who run the service, and outside providers who help them, can see customer data only as far as their work needs. They are bound by confidentiality, they sign in with two-step sign-in, we mask personal details until they have a reason to see them, and we record each time they look at a customer’s data. They do not sign in as you.

When an agency sends monthly proof emails to its clients

An agency can have us send a monthly proof email to contacts at its clients. The agency chooses the people and is responsible for their details. We send the emails for the agency and on its instructions. We keep the recipient’s name and email address and a record of each send (delivered, bounced, complained) for as long as the agency keeps the project, then for 30 days after it ends, and bounce and complaint records for 90 days. Before the first monthly email we send each person one email asking them to confirm, and we send nothing more until they do. We do not track opens or clicks.

If you received one of these emails: it was sent in the name of the agency named in it, because it works with you or your employer and asked us to send you its report. The agency is responsible for your details; write to it first. The unsubscribe link in each email stops them at once. We keep your address in scrambled form on a list of people who asked to stop, for 5 years after the last send, so that we do not send to you again by mistake. You can also write to us at the contact address.

When a report has a record code

Each live proof report gets a record code. Anyone who has the code can open the verify page and see the date the record was issued, the name the buyer gave for the report, the buyer’s client website, the number of pages and results, the dates of the checks and a fingerprint. It shows no page addresses, outlets, email addresses or link to the report. We do not check the name. We keep a record for as long as the report it belongs to. If the buyer closes their account, or the person named asks us, we remove the name and keep the rest; the page then says “Name removed at the holder’s request”. If the buyer asks, we withdraw the record and the page says “It was withdrawn by its holder”. Write to the contact address to ask us to remove a name. Why we may use it: to carry out the contract, and to let people confirm that a report is genuine.

When you use a free tool

The free tools visit the one public page you enter, as any visitor would, and obey its robots.txt file. We keep the result for one hour so you can read it, then delete it; there is no share link. We keep nothing else about the page or the address you typed. To limit abuse we keep scrambled counts for 48 hours: one for your connection, one for the website you entered and one for all visitors. The hosting provider’s technical logs record your IP address for security, but not the address you typed. The tools set no cookie and ask for no email address. Why we may use it: to run a free service without abuse.

When you have a monthly plan

For a monthly plan we keep the plan, its dates, the amount of each charge, the invoice and the payment references from Stripe, and the dates and results of payment attempts. If a payment fails we email the owner and the billing contact about it; those emails contain no advertising. We use these details to give you the plan and to account for the sale. Why we may use it: to carry out the contract, and to keep the accounting and tax records the law requires. Stripe also keeps its own records as an independent controller.

Downloading your data and closing your account

You can download your data, and each person can download their own, from the account page at any time, in files a computer can read. The workspace owner can close the workspace. Access stops at once; you have 7 days to change your mind; within 30 days of the request we delete your data from our live systems, and copies in backups are overwritten within 35 days after that. If we ever need to start from a backup, we first delete again what had already been deleted.

What we keep after you close: invoices, payment and credit records, and the record of money actions, for six years, locked, used for nothing else, because tax and commercial law require it; the confirmation that you buy for your business and the terms you accepted, for up to five years from your last purchase, to answer any claim; the text of a release that went out, its approval and our checks, until two years after the order ended; and the scrambled list of people who asked not to be emailed. Then we delete them.

When we check an outlet’s page

Our checker, an automated program called PressProveBot, downloads the public page as any visitor would see it. It may contain personal data that is already public, such as a byline, people quoted, or who publishes the outlet as stated in its legal notice. For package orders and the free check on our site, we keep an excerpt of the page text (up to 12,000 characters) so the comparison can be repeated. For checks run through the API or the console, we keep no page text, only the result and a short piece of the page around the paid label or your link. We do not look those people up, build no profiles and do not publish their names.

For checks you run through the API or the console, we do not keep the page or an excerpt of it. We keep the result, the phrases of your text we used to find it, a short piece of the page around a paid label or your link, and the link attributes. We obey each site’s robots.txt file and stop visiting a site that asks us to. Website owners can read how to reach us and how to block us at /bot.

When you visit the website

We count visits on our own server only. For each page view we record the page, the source tag in the address if there is one (src or utm_source), the website the visitor came from (the site’s name only, not the full address), and whether the visit is on a phone or a computer. We also count the steps of an order: the order form opened, checkout started, paid, refunded, and a free check started. For this count we set no cookie, store nothing on your device, keep no IP address (not even in scrambled form) and use no identifier that follows you from one site to another. The source tag reaches your order through the page address only. We keep the individual rows for 90 days and the daily totals for 25 months. We use no advertising or third-party analytics cookies. The site sets one cookie of its own, and only when you sign in to your account (see below). If you switch between the light and dark look, your browser keeps that choice on your device; it is never sent to us. The hosting provider records the IP address and the requested page in its technical logs, for security and abuse detection.

Cookies and storage on your device

We use no advertising and no analytics cookies, so there is no cookie banner. When you sign in to your account, one cookie (__Host-pp_customer) keeps you signed in for up to 30 days; the account cannot work without it. If you switch between the light and dark look, your browser keeps that choice on your device (vdr-theme), and on the developer docs it keeps the code language you picked (pp-docs-lang); neither is ever sent to us. A language cookie (lang) is set only if you choose a language; the site is in English only, so it is normally not set. If we ever add a tag that sets advertising or analytics cookies, we will ask you first and update this page. We do not track you across other websites, so your browser’s Do Not Track setting changes nothing here.

When you write to us

When you use the contact form, we keep your name, your email address, the topic you chose and your message, to answer you and to follow up on what you asked. We do not use them for marketing. To stop the form being flooded, a salted hash of your connection’s address is kept for a short window. If email notifications are switched on, the provider that delivers our emails carries a copy of your message to us. We delete the message automatically twelve months after it arrives, or earlier if you ask. If you delete your account, we delete your messages 30 days after we have dealt with them.

When you use the Ask us assistant

Your question and our answer are sent to our AI provider, Anthropic, to write the answer. We keep them for 30 days, then delete them. Please do not type personal or confidential information. Answers come from an AI program and can be wrong; the terms and the refund page decide. We keep no IP address and no identifier with the chat, the assistant sets no cookie and stores nothing on your device, and the conversation is gone from your screen when you leave or reload the page. To stop the assistant being flooded, a salted hash of your connection’s address is kept for a short window.

Emails

We email you about what you asked for, such as the receipt for your purchase. We send no commercial emails to anyone who has not asked for them. We also send messages about your account, such as a failed payment, an invitation you were sent, or a sign-in link. They contain no advertising.

Who else receives your data

We never sell your data or pass it on for anyone’s own purposes. It is received, only as far as necessary, by the payment provider (payments), the hosting provider (the site and its database), the provider that delivers our emails, the AI provider that answers the Ask us assistant (only what you type there), our accountant, and public authorities when a law obliges us. We send your release, with your company’s name and link, to a newswire, which publishes it on news sites. Once published, it is public and each site controls its copy. Where a provider processes data in another country, we rely on the transfer safeguards the law provides. People who help us run the service can see customer data only as far as their work needs; see “Who at PressProve can see your data”.

How long we keep it

Invoices and accounting records for as long as the law requires. An audit’s text, list and evidence only as long as needed to show you the result and answer your questions; you can ask us to delete them at any time. The hashed IP address is kept only to count requests over a short window. The periods for plans, teams, monthly emails, records and closing an account are in the sections above.

Your rights

You can ask for access to your data, to correct it, to erase it, to object to its processing, to restrict it and to receive it in a portable format, and you can withdraw a consent at any time. Write to the contact email saying which right you are exercising; if we cannot identify you with reasonable certainty we will ask for something that proves it. We reply within 30 days. Some data we cannot delete even if you ask: invoices, payment and credit records and the record of money actions while a law obliges us to keep them. We keep them locked and use them for nothing else. If you are not satisfied with our reply, you can complain to your local data protection authority. You can download your data and delete your account yourself from your account page; each person can do this for their own details.

Children, automated decisions and changes

The service is addressed to businesses and professionals. It is not directed to children under 13, and we do not knowingly collect their data; if you believe a child has sent us data, write to us and we delete it. An audit’s results are produced by a program, but they concern pages and placements, not people, and have no legal effect on you. We publish any change to this policy on this page.

Who is behind this site is in the legal notice.