Privacy Policy (Privacyverklaring) | Aquifer and Pump

This page is a general privacy policy template for Aquifer and Pump. It is written to be clear and practical, but it is not legal advice, and it does not create a lawyer-client relationship.

Privacy law differs by country, state and province. Before you rely on this text, have it reviewed against the laws that apply to you, such as state privacy laws in the US, PIPEDA and provincial laws in Canada, or the GDPR if you have visitors in the EU or EEA.

Nothing here is a promise about how third parties handle data. Where this policy mentions your own service providers, replace the placeholders with the actual names and details before publishing.

Aquifer and Pump exists to give well owners straight answers, not to collect data. This policy explains, in plain terms, what information this site may gather when you visit, why it is gathered, how long it may be kept, and what rights you have over it.

You can reach us about anything on this page at [email protected].

Which data we may collect

Most of what this site does is show you articles, and that works without you handing over anything. Reading a guide about a pressure switch or a bacteria test does not require an account.

Depending on how the site is set up, a few categories of data can still be collected. Contact data: if you email us or use a contact form, we receive your name, email address and whatever you write. Technical data: servers and analytics tools typically log your IP address, browser type, device, pages visited and approximate location derived from the IP address. Cookie data: small files stored in your browser, covered in the cookies section below. Newsletter data: if a signup form is offered, your email address and your consent to receive messages.

We do not ask for, and do not want, sensitive information about your health. If your water test came back positive for bacteria or nitrate, talk to your local health department or a licensed lab, not to a website contact form.

Good privacy practice starts with collecting less. Keep only what you actually use, and know why you use it. The sections below describe purposes, legal bases and retention in general terms, because the honest answer is that the specifics depend on the tools and providers you actually run.

Purposes: why the data is used

Data collected through this site is used for a small set of purposes. To answer you: if you write to us, we use your contact details to reply. To keep the site running: server logs help with security, debugging and blocking abuse. To understand what readers need: aggregated analytics show which guides are read, so gaps in the content can be fixed. To send a newsletter: only if you signed up, and only until you unsubscribe.

We do not sell your personal data, and this template does not contemplate selling or sharing it for cross-context behavioral advertising. If your actual setup differs, say so plainly here and check which state laws that triggers, for example in California, Virginia, Colorado or Connecticut.

For visitors in the EU and EEA, the GDPR requires a stated legal basis for each purpose. In general terms: replying to your message rests on legitimate interest or steps toward a contract; analytics and non-essential cookies rest on your consent, collected through a cookie banner; keeping the site secure rests on legitimate interest; a newsletter rests on your consent, which you can withdraw at any time.

For US visitors, most state privacy laws do not require a legal basis in the GDPR sense, but they do require transparency about what is collected and why, and they give you rights described below. For Canadian visitors, PIPEDA and provincial laws are built around meaningful consent.

Adjust this section to match your real data flows. The legal basis has to reflect what you actually do, not what sounds tidy.

How long data is kept depends on what it is and why it was collected. This template deliberately does not state fixed periods, because inventing a number you do not actually follow is worse than stating the principle and filling in the real figure once you know it.

Retention period

The working principle is simple: keep personal data no longer than needed for the purpose it was collected for. Emails are kept as long as needed to handle your question and any follow-up. Server logs are kept for a limited period set by your hosting provider. Analytics data is kept for the retention period configured in your analytics tool. Newsletter addresses are kept until you unsubscribe, then removed or suppressed.

Before publishing, replace these general statements with the actual retention periods of your hosting, analytics and email providers. If you cannot find them, that is a sign to ask the provider, not to guess.

Your rights over your data

Depending on where you live, you have some or all of the following rights. Access: you can ask what personal data is held about you. Correction: you can ask to fix data that is wrong. Deletion: you can ask for your data to be erased, subject to legal retention duties. Objection and restriction: you can object to certain processing or ask for it to be limited. Portability: in the EU and EEA you can ask for a copy in a usable format. Opt out: in covered US states you can opt out of the sale or sharing of personal data and of targeted advertising; this template states that no sale takes place. Withdrawal of consent: where processing rests on consent, you can withdraw it at any time, for example by unsubscribing.

To use any of these rights, email [email protected]. State clearly what you are asking for. We may need to verify that the request really comes from you before acting on it.

If you are in the EU or EEA, you also have the right to complain to your national data protection authority. In Canada, you can contact the Office of the Privacy Commissioner. In the US, some states let you appeal a denied request or complain to the state attorney general.

Cookies are the part of privacy that readers actually notice, mostly because of the banner. This section explains what they are and which categories this site may use, in the same plain terms as the rest of the policy.

Cookies and similar technologies

A cookie is a small text file a website stores in your browser. Some are strictly necessary, for example to remember your privacy choices or keep the site secure, and those can be set without consent in most jurisdictions. Others are optional.

This site may use analytics cookies to understand which guides are read and how visitors move through the pages, and functional cookies to remember preferences. If advertising or embedded third-party content is ever added, those parties may set their own cookies, and this section must be updated before that happens.

For visitors in the EU and EEA, non-essential cookies are only placed after you consent through the cookie banner, and you can change or withdraw that choice at any time through the same banner. You can also delete or block cookies in your browser settings, though some parts of the site may then work less smoothly.

Questions and contact

If anything on this page is unclear, or you want to exercise a right described above, email [email protected]. We will answer as quickly as we reasonably can, and within any deadline the applicable law sets.

This policy may be updated when the site or the law changes. The current version is always the one published on this page, with the date of the last revision shown at the top once you finalize the template.

The next step is yours: before publishing, walk through your actual setup, name your real providers, fill in real retention periods, and have the result checked against the laws that apply to your visitors.