Privacy Statement
Effective October 14, 2026
This statement covers the PostgresBackup Windows app and the website at postgresbackup.com. “We” and “us” means Frank Buchner, the independent developer who builds and sells PostgresBackup. Questions or requests go to [email protected].
1. The PostgresBackup app
Your data stays on your computer. The app connects only to the PostgreSQL servers you add, and it writes backups only to the folders you choose. We never receive your database contents, your backups, or anything about them.
Your server logins stay local. Server connection details, including passwords, are saved in the app's settings folder (C:\ProgramData\PostgresBackup). Only your Windows account, Administrators and the PostgresBackup background service can read that folder. The folder also holds the app's activity logs and your license status. Uninstalling the app and deleting the folder removes all of it.
No usage tracking. The app doesn't record or report what you do in it: no analytics of your servers, jobs or backups, no crash reporting and no advertising code. It doesn't need an account.
Install ID. On first run, the app creates a random install ID. It's generated from nothing about you or your computer, and it's stored in the app's settings folder. It lets us tell installs apart without knowing whose they are.
Update checks. About once a day while it's running, the app asks postgresbackup.com for the latest version and release notes. The request carries the app's version number and the install ID, and nothing else: no license code, settings or data about your databases. If you choose to install an update, the installer download carries the same two details. You can switch automatic checks off in the app's update window; the app then contacts us only when you check or activate yourself.
License activation. When you activate a license, the app sends the license code, its version and the install ID to postgresbackup.com to confirm the code is genuine.
Microsoft .NET runtime. PostgresBackup runs on Microsoft's .NET Desktop Runtime. If it isn't installed, Setup downloads it directly from Microsoft (builds.dotnet.microsoft.com) and installs it. That request goes to Microsoft, not to us, and carries nothing about you, your install or your databases. Microsoft's own privacy statement covers it.
What we record. We record these update checks, update downloads and activations (successful or not, with the code that was entered) in SiloCDP, on an anonymous profile for your install that holds the install ID and the app version. Each one also records the app's user agent (which shows your operating system) and your approximate location — country, region, city and postal code, worked out by our hosting provider from your IP address. We use this to count how many installs run each version and how many are activated, and to spot activation problems. The profile isn't linked to your name or email address, and we don't use it for advertising.
These are the only requests the app makes to us. As with any web request, our hosting provider can see your IP address while it handles them (see section 4). We pass the IP address on to SiloCDP with each of these records, which uses it only to look up the network it belongs to (so that traffic from data centers and bots can be told apart from real installs) and doesn't store it. The same applies to the purchase question described in section 3.
2. Visiting postgresbackup.com
On your first visit, a cookie banner asks what you're happy with. Until you choose, and if you choose Reject all, none of the tracking below runs. We also treat the Global Privacy Control signal from your browser as a refusal. You can change your mind at any time with , which is also linked in the footer of every page.
Consent record (always on)
Your choice is saved in a cookie named silo_consent for up to 365 days, so the banner doesn't appear on every page. A record of the choice (which categories you allowed, when, and the version of this policy) goes to SiloCDP, our consent provider, as proof of consent. The banner is provided by SiloCDP and loads from its servers.
Analytics (only if you allow “Analytics”)
We use SiloCDP to count visits and understand which pages are useful. It stores a random visitor ID and a session ID in your browser's local storage (keys starting with silocdp_). For each page view it records the page address and title, the site that referred you, any campaign tags in the link (utm_*), your browser's user agent and device type, and how long you stayed on the page. It also keeps a visitor profile with basic device details: browser and operating system, screen size, language, time zone, the page you arrived on and the referring site. When you download the installer, we record it as a view of the installer's address. We don't use this to identify you, and we don't use it for advertising.
We also use Google Analytics 4 for the same purpose. It sets cookies named _ga and _ga_* and records similar information: pages viewed, the referring site, your browser and device type, and your approximate location (derived from your IP address; Google Analytics 4 doesn't store full IP addresses). Google processes this data under its privacy policy.
Browser notifications (only if you allow Analytics and then opt in)
If you allow analytics, the site may offer to send you notifications about new releases. Nothing is sent unless you also accept your browser's own permission prompt. If you do, your browser creates a push-subscription address, and SiloCDP adds it to your visitor profile so it can deliver the notifications. A small script at /nw-sw.js (a “service worker”) runs in your browser to display them. To stop notifications, turn them off for postgresbackup.com in your browser's site settings.
Marketing
This site doesn't run advertising or marketing tags. The banner lists a Marketing category because SiloCDP offers it, but nothing on this site uses it today. If that changes, we'll update this statement and ask again.
| Stored item | Set by | Purpose | Kept for |
|---|---|---|---|
silo_consent (cookie) | SiloCDP | Remembers your cookie choice | Up to 365 days |
silocdp_* (local storage) | SiloCDP | Visitor, session and profile IDs (analytics consent only) | Until you clear site data |
_ga, _ga_* (cookies) | Google Analytics | Counting visits (analytics consent only) | Up to 2 years |
The site's fonts and images are served from our own domain. The only other services your browser contacts are SiloCDP (the cookie banner on every visit, plus analytics if you allow it), Google (if you allow analytics) and Stripe when you choose to buy.
3. Buying a license
Purchases are processed by Stripe on Stripe's secure checkout page. Stripe collects your payment details, email address and billing information to take the payment and prevent fraud. We never see or store your full card number. Stripe handles this data under its privacy policy.
From Stripe we receive a record of the purchase: your email address, the amount and the payment status. We use it to show you your license code, to help you recover a lost code, and to handle refunds and support requests. Each purchase (email address, license code, amount) is also recorded in our server logs and, as a customer profile identified by your email address, in SiloCDP, so we can count sales and match a purchase to its activation. If you allowed analytics on this site, the random visitor ID from your browser goes along with the purchase, so your earlier visits appear on that profile. Buying doesn't add you to a mailing list.
After checkout we ask, optionally, where you heard about PostgresBackup. If you answer, the answer (and any detail you type) is added to the same customer profile in SiloCDP, so we can tell which channels bring customers.
Release update emails (only if you sign up)
You can ask for an email when a new version comes out, on this site or from the app's Updates window (which opens a page here). The sign-up form is provided by SiloCDP: it stores your email address, your consent (with the wording you agreed to, the time and the page) and where you signed up. You first get an email asking you to confirm, and nothing more is sent until you do. Every email has an unsubscribe link that works with one click. We use the address only for these updates and never share or sell it.
4. Hosting and server logs
postgresbackup.com is hosted on Amazon Web Services (AWS). Like almost every web host, AWS records basic technical details about each request (IP address, browser user agent, the page requested and the time) to keep the service running and secure. These logs are kept for a limited time and aren't used to track you.
5. Emailing us
If you write to [email protected], we'll have your email address and whatever you choose to send. We use it only to reply and help you, and we keep the conversation only as long as it's useful for support.
6. Who we share data with
We share information only with the service providers named above, so they can do their jobs: SiloCDP (consent, website analytics, notifications, release update emails, and the install and purchase records described above), Stripe (payments), AWS (hosting) and Google (analytics). We also share it when the law requires us to.
- We never sell, rent or trade your personal information.
- We never access, upload or read your databases or backups.
- We never share data for advertising or cross-site tracking.
7. Your choices and rights
- Change or withdraw consent at any time with . Withdrawing stops tracking from then on.
- Clear what's stored in your browser by deleting this site's cookies and site data in your browser settings.
- Access, correct or delete your data. Depending on where you live (for example under the GDPR in the EU and UK, or the CCPA in California), you can ask for a copy of the personal data we hold about you, ask us to correct or delete it, or object to how we use it. Email [email protected] and we'll respond within 30 days. Records we must keep for tax or accounting, such as purchase records, are kept for as long as the law requires.
- You can also complain to your local data-protection authority.
8. Children
PostgresBackup is a tool for database administrators and developers. It isn't aimed at children, and we don't knowingly collect data from anyone under 16.
9. Changes to this statement
If we change how we handle data, we'll update this page and its effective date. If a change needs your consent, the cookie banner will ask you again.