Privacy
What DeployPost does with information
DeployPost is run by RTG Product Labs. The free website check needs no sign-up, account, email or payment. DeployPost Watch, the daily check, needs an account: what Watch keeps is further down.
When you check a site
The address you enter is sent to our server. The server then requests that public page and a few related public files: its robots.txt, sitemap and share image, the page’s logo (only when the result offers to make a share image or site icon, so it can be drawn with), the page’s http:// version, the same address with or without “www.”, a made-up address on the same site (to see how missing pages answer), up to 8 links from the page, and up to 10 other pages of the site from those links or its sitemap (to read their titles, descriptions and search settings). These requests identify themselves as DeployPostCheck. We only read; nothing on the site is changed. More about the checker.
The server also looks up the domain’s public email records (the same records any mail server reads before accepting a message): who handles its email (or, when none is listed, the server address mail would go to instead), its SPF and DMARC records, one standard signing record for Google or Microsoft email, and three optional settings (MTA-STS, TLS reporting and a BIMI logo). If the domain publishes MTA-STS or a BIMI logo, the server also reads that public policy file or logo file. No email is sent to or from the domain.
If the page shows an email address on its own domain, the check only uses it to tell you whether mail sent to that address has somewhere to go. The address is not shown in the result, stored or used to contact anyone.
The result is kept in the server’s memory for about 10 minutes, so that checking the same address again doesn’t send the site more requests. Then it is deleted. “Check again” skips that saved copy. The result is not written to disk or a database, and it is not used for anything else.
Page speed
When page-speed checks are available, our server asks Google PageSpeed Insights to time the page you checked. We send Google only the page’s address; Google’s servers then load the page on a simulated phone and send back the timings, along with how fast the page has been for real Chrome users when Google has enough of them. Nothing about you is sent. Google handles that request under its own privacy policy. The timings are kept in our server’s memory for about an hour, so that looking again doesn’t ask Google again, and then deleted. The “See Google’s full report” link opens Google’s own site.
Links to a result
After a check, the address you checked is added to this page’s link (for example /?url=yoursite.com) so you can copy it, email it or come back to it. If you pick a different builder under “Show steps for”, the link carries that choice too (for example &for=wix). Anyone who opens that link runs a new check of the same public site. The link stays in your browser history like any other page you visit. “Save as PDF” uses your browser’s own print dialog, so the copy is made on your device and not sent to us.
The share image, site icon and business details makers
If you make a share image or a site icon, it is drawn in your browser from what is already shown in your results, the logo found on the page, and the letters, colour or logo file you choose. A logo file you choose is read by your browser only and is not uploaded to us. What you make is saved straight to your device and is not uploaded to us either. The business details you type into the business details maker, and the kind of business you pick, stay in your browser too: we turn them into a block for you to copy, and they are not sent to us.
Pictures in our emails
When DeployPost emails a business about its website, the email can show a picture of a fix drawn from that site’s own public page: its name, title, description and colour. The picture comes from this server. Legacy links name the website and carry those words. Newer links may also include the random message handle described under Measurement; neither contains a recipient address. Our logs record only that a picture was requested, not which site it was for. Showing it sets no cookie.
Limits that keep the check fair
To stop the check being overused, the server counts how many checks come from each connection address (your IP address, or for IPv6 the network part of it) and how often each site is checked, separately for checks and page speed. These counts are kept in memory for about an hour and then deleted.
Logs
When our server keeps a log, it records only the time, which page or check was requested, the answer code and how long it took. It never includes the address you checked, your IP address or your browser details. Cloudflare hosts this service: it handles the connection to deliver the page and may keep its own standard request logs, which can include the full link you opened.
DeployPost Watch
If you sign up for DeployPost Watch, it runs the website check described above on each page you add, once a day, and tells you when something changes. To do that it keeps:
- Your email address, and when you confirmed it.
- The addresses you watch, and a summary of each one’s last check: which checks passed or need attention, when its security certificate runs out, who handles its email, and where the address leads. Not the page’s text.
- A list of the changes we told you about, for 90 days.
- The alert channels you add (Slack, Discord, Microsoft Teams or your own webhook). Their addresses, which work like passwords, are stored encrypted.
- If you subscribe: the customer and subscription numbers Stripe gives us, and whether your subscription is active. Stripe handles the payment on its own pages; we never see your card.
- If you send your domain’s DMARC reports to Watch: what those reports say, which is the addresses (IP) of the servers that sent email as your domain, how many messages each sent, whether they passed, the domain each was signed or sent for, which mail provider reported them, and the DMARC policy your domain publishes. Reports don’t contain the messages or their subjects. We don’t keep the report emails themselves, or the recipient domains some reports list. We keep what they say for 45 days. Anyone can send to a report address, so we count a report only when its signature shows a mail provider sent it. For any other report we keep only the address it came from, the signing domain, the provider and report number it claims, its date and how many messages it claims to cover, also for 45 days, so we can show you how many were set aside.
Naming the servers that send as you. To show a sending server as, say, “Google” rather than a number, we look up its public DNS name through Cloudflare’s public DNS service and keep that name for 45 days.
Email. We send sign-in links, the alerts you asked for, a reminder before a free trial ends, and notices about your account, through Resend. Every alert email has a one-click link to turn alert emails off. Sign-in links work once: the first one lasts 24 hours, later ones 30 minutes. If an address bounces for good or reports our email as spam, we keep a scrambled form of it (a hash, not the address itself) that a new sign-up can be matched against, so we don’t email it again, even after the account is deleted.
Signing in. Signing in sets one cookie, dpw_session, which keeps you signed in on that browser for 30 days. It is used for nothing else, and signing out removes it.
Limits. To stop sign-ups being misused, we count requests from each connection address, and emails to each address. The counts are kept under a code made from the address with our own secret key, so they can’t be traced back to it, and are deleted within a day.
How long we keep it. For as long as you use Watch. When a free trial or subscription ends, checks stop, and we delete the account and everything above 30 days later unless you start again. An account whose email was never confirmed is deleted after 7 days. You can delete your account at any time on your settings page, which removes everything straight away. Stripe keeps its own payment records, as the law requires.
Who else is involved. Cloudflare runs Watch and stores its data. Resend delivers its email. Stripe handles payments. Mail providers such as Gmail and Outlook send the DMARC reports you ask for. Alerts you send to Slack, Discord, Microsoft Teams or your own webhook are handled by those services. Watch’s checks come from the same checker as the free check and identify themselves the same way. See the Watch terms.
Launch Readiness Pass workspace
We store your confirmed business profile, selected site, public-check evidence, included quote scope, generated files and recheck records to deliver your launch package. Stripe processes payment; we store one-time order, payment and refund identifiers and status, never card details. Browser-rendered downloads are stored when you request that action.
Refunds stop new paid work but retain delivered files. Watch trial expiry does not delete an account with a Launch Pass order. Explicit account deletion removes private workspace facts, observations and files. Payment/refund identifiers and frozen purchase scope remain for reconciliation and refund recovery; contact us with access or deletion questions. Download your files before deleting your account.
Measurement
Your analytics setting shows here once the page has loaded.
To learn whether the check is useful, we measure how it is used with PostHog, an analytics service in the United States. Outside the EU, EEA, UK and Switzerland this is on by default, and you can turn it off above. In those places, and when we can’t tell where you are, nothing is sent to PostHog unless you choose Allow on the small card that appears. If your browser sends Global Privacy Control or Do Not Track, it stays off and we don’t ask.
When it is on, PostHog receives: which of our pages opened (never the rest of its link), when a check starts and whether it is the example or your own site, how it was started, whether a result appeared, and the kind of error when a check fails. With these go a random ID made in your browser and one for the visit, your country as Cloudflare sees it, your browser, system and device type (such as Safari, iOS, phone), the name of the website that sent you here when your browser shares it, and our own campaign labels when the link carried them. We never send the address you check, anything read from that site, its result, what you type, email addresses or DNS records. We tell PostHog not to keep your IP address or place you by it. PostHog does not record sessions or track clicks. We do not use fingerprinting or advertising.
Where we ask first, until you allow analytics (or if you say no), we only add one to anonymous daily totals when a page opens, when you start a check of your own site and when its result appears. The totals hold no ID, address or detail about you or the site. Cloudflare stores them in the EU, and they are deleted after 90 days.
Your choice, the random ID and the first campaign label are kept in this browser’s storage. A separate cookie holds only “on” or “off” for email request measurement; it contains no ID and expires after one day. “Turn off analytics” stops PostHog, anonymous totals and email request measurement in this browser, in every open tab of this site, and removes the ID and labels. Anything already recorded is not deleted automatically; email us to ask.
Email image and link requests
Some emails use a random, message-specific handle in the functional image and preview link. When measurement is allowed, we record an image request, a preview-link request, or a browser-confirmed landing separately. These are request signals, not proof that a person opened or clicked an email: mail proxies, security scanners and other automated systems can make requests.
Individual request signals are recorded only outside the EU, EEA, UK and Switzerland when the request includes the “on” choice cookie and no Global Privacy Control or Do Not Track signal. First-click landings can be recorded after the browser checks its existing privacy choice. In consent regions, when location or choice is unknown, or after refusal, the image and link still work but no individual signal is recorded. Mail proxies usually provide no browser choice, so their coverage is unavailable. Older messages have no recorded request history; missing signals do not mean a message was ignored.
The private message record keeps the event kind, its time and a random request ID to prevent duplicate processing. We do not store IP addresses, user agents or raw request links in that record, and do not send message handles or recipient details to PostHog. The message handle can record signals for 30 days; the functional image and preview link continue working afterward.
DeployPost Watch uses a sign-in cookie and measures account and billing actions under the same regional analytics choices. See Watch privacy for its full data handling and analytics details.
Other services your browser contacts
- The page’s fonts come from Google Fonts, so your browser connects to Google to load them.
- When analytics are on, your browser sends the events described under Measurement straight to PostHog.
- If the site you check has a working share image, your browser loads it straight from that site to show it to you, without telling it which page you came from. For the Oak & Stone example, the share image comes from this site.
- “Email it” opens your own email app with a link to the result. Nothing is sent unless you send it.
Questions
Email hello@rtgproductlabs.com.