Legal
Privacy
RetainerProof is operated by:
DIGITAL AYNS LLC
1603 Capitol Ave Suite 413G-1351
Cheyenne, Wyoming 82001
USA
Contact:
This page describes the data the product actually stores and the companies that process it. It is not a copy-paste policy from another product.
What we store
When you create an account we store your email address and a hash of your password. We also store the brand settings you type in (studio name, contact email, optional phone, website, logo URL, and accent color), the sites you add (name and the public URL), check results, uptime samples, screenshots of those public pages, and the work-log notes you write. If you create an API key, we store its name and a SHA-256 hash of the key. The full key is shown once and is not stored. If you add client digest recipients, we store those email addresses and whether each one unsubscribed. If someone subscribes on a public status page, we store that email address, a confirmation, and an unsubscribe. If you connect your own Resend API key, we store it encrypted and keep only the last four characters visible. The full key is not shown again.
That account and check data lives in a SQLite database on our own server. Screenshot files live on that same server, next to the database. We do not use a separate hosted database.
Payments go through Stripe. We store Stripe’s customer id and subscription id. We do not store your card number.
The public website check at /tools/website-check does not require an account. We do not store the URL you submit or the snapshot we show you. The mobile PageSpeed request sends that URL to Google for the score, and we do not keep it after the page is shown. We store only a count of how many checks ran and how many we refused. The connection address is used to limit how often one connection can run the check. That limit lives in memory on the server. It is not written to the database.
If you sign up for the monthly agency tip, we store your email address, the page you signed up on, the time you signed up, and whether you confirmed the address. We send one confirmation email through Resend from . We do not send the tip until you click that link. Every message includes an unsubscribe link. Email if you want that address deleted.
Processors
- Hetzner (EU hosting). The app and the SQLite database run on a server we rent from Hetzner in the European Union. On request we can also host outside the EU.
- Stripe (payments). Stripe charges the monthly subscription. Stripe receives the email used at checkout and the payment details you enter on Stripe’s page.
- Resend (transactional and alert email). Red-site alerts, the test alert, client digest summaries, status-page confirmation, status incident mail, and the monthly agency tip confirmation are sent through Resend. The tip confirmation is sent from . Resend receives the recipient address and the message. Freelancer alerts use our Resend account. Client digest and status mail use our account unless you save your own Resend key in Brand settings, in which case those messages go through your Resend account and your verified From domain. If that key fails, we do not send those messages from our domain.
- Google PageSpeed Insights API. When a performance check runs, we send Google the public URL you asked us to measure. Google returns scores for that URL. We do not send your password.
- Umami (cookieless analytics, self-hosted). On the public marketing pages — the home page, the website check, the guide pages, the API docs, the updates page, this privacy page, the terms page, and the signup and login pages — we may load Umami from our own servers. A one-time checkout page may load it too, only long enough to record that checkout started, finished, or was canceled. The logged-in app loads it on a single response when an account event happens for the first time: signup, the first site added, or the first digest. Umami is cookieless. It does not do cross-site tracking. It keeps aggregated page and event counts. A custom event may include a plan name (starter, studio, or agency) when we already know it, or a website-check status of ok, issues, blocked, or error. It does not include your email address, account id, or the URL you checked, and it does not store IP addresses. The script is not loaded on client digest URLs or public status pages, and it is not loaded on the rest of the logged-in app.
We do not sell personal data. We do not use advertising networks. We do not use Google Analytics. Cookieless Umami is the only analytics, and there is no cookie banner because no analytics cookie is set.
Cookies
We set a session cookie named cp_session and its signature cookie cp_session.sig, so you stay logged in. Both are HTTP-only. Umami does not set a cookie. We set no analytics or advertising cookies.
Public pages you turn on
The secret digest URL shows a monitoring report for a site you added. If you publish a status page, that page shows current uptime for that site. It does not include your work log, alert email, or the secret digest URL. The status page can collect an email address for down and recovery notices. That address is not used until the person confirms it.
Asking about your data
The app has no self-serve button to delete an account. Email and we will tell you what we hold for that address.