Reading about erectile dysfunction is a private act, and a site on this subject that treated visitor data casually would deserve none of the trust it asks for. This page describes what Erection records, why, who else sees it, and what you can do about it.
Questions go to [email protected], answered by a person and not a form.
Who runs the site
The site operates at springlynnemotorcycles.co.nz and is published by an independent editorial project, which acts as data controller for everything described below. General correspondence belongs at the addresses on the contact page; data requests belong at the privacy address above.
Readers sit mostly in the United States, so the California Consumer Privacy Act as amended by the CPRA applies to Californian visitors. Readers in the European Economic Area are covered by Regulation (EU) 2016/679, readers in the United Kingdom by the UK GDPR and the Data Protection Act 2018, and the New Zealand Privacy Act 2020 applies through the domain registration. Where the regimes differ, we apply whichever gives the reader more control.
What gets collected
What you send us
An email to us contains whatever you put in it: your address, any name you sign with, and the message. Nothing is enriched from other sources. The site has no contact form, no newsletter, no accounts and no comments, so those collection points do not exist.
We never ask for and never want payment details, identity documents, age-verification records or anything about your medical history. A message describing symptoms is answered with a suggestion to see a clinician and then deleted; we are not equipped to hold health information and have no wish to be.
What the server records
Serving a page produces technical data that lands in server logs and aggregate analytics:
- IP address
- Needed to route the response back to you, used to derive an approximate country for traffic reporting, and used to filter scraping and denial-of-service traffic. Analytics receives it truncated.
- Browser and version
- Used to confirm the layout renders on the browsers readers actually use, and to identify self-declaring bots.
- Operating system and device class
- Used to decide how much layout work goes into mobile against desktop, since the split shifts over time.
- Pages viewed and time on each
- Used to find explanations readers abandon halfway, which is the signal that a passage needs rewriting.
- Referrer
- Used to tell whether a visit arrived from a search engine, a forum link or a direct entry, and to spot sites republishing the text without attribution.
- Language and screen size
- Used for layout testing and to confirm the English-language scope matches the audience.
Cookies
The site sets one first-party cookie recording your consent choice so the banner does not reappear, and the content delivery network sets short-lived technical cookies for bot filtering and rate limiting. Analytics cookies load only after you accept them, and the identifiers involved expire after two years and twenty-four hours.
No advertising or marketing cookies exist here, because the site runs no advertising and no commercial links at all, a position documented on our disclosure page. Refusing analytics changes nothing you can see: every page stays fully readable, and the only loss falls on our side of the exchange.
Why any of it is processed
- Delivering the pages
- Serving HTML, stylesheet and images to your device at a reasonable speed through a content delivery network.
- Editorial improvement
- Aggregate reading patterns show which explanations fail, and that is how sections get rewritten.
- Traffic statistics
- Visit counts, sources and device breakdowns, read at the level of countries and page groups and never at the level of one visitor.
- Security
- Blocking automated abuse and keeping enough log history to investigate an incident afterwards.
- Correspondence
- Answering your email, and retaining what the law requires for as long as it requires.
Legal bases under GDPR Article 6
Consent under Article 6(1)(a) covers every cookie that is not strictly necessary, meaning analytics alone. You give it through the banner and can withdraw it at any time by clearing site data, with no effect on the lawfulness of processing that already happened.
Legitimate interests under Article 6(1)(f) cover security logging and aggregate measurement. Our interest is keeping the site online and knowing which material to improve; there is no profiling and no decision that affects you, and that is what makes the balance come out in favour of processing. Article 6(1)(b) applies narrowly to handling a message you chose to send, and Article 6(1)(c) where retention is compelled by law.
Who else sees it
We do not sell personal data, do not share it with advertising networks, and have no commercial partners to share it with. Three categories of processor are involved: an analytics provider receiving truncated IP address, page views, session length, device class and country; a content delivery network processing IP address, request headers and timestamps as it filters traffic; and hosting and mail providers storing server logs and any message you send.
Those providers are United States companies, so data reaching them leaves the EEA and the United Kingdom. Transfers rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework where the recipient is certified, and on Standard Contractual Clauses under Commission Implementing Decision (EU) 2021/914 otherwise. Copies of the safeguards in force are available on request.
No page behaves differently from any other in this respect. Reading morning erection, how long should an erection last, vacuum erection device, public erection or female erection generates the same minimal server record, and nothing in that list is tagged, segmented, or used to build an interest profile about you.
How long anything is kept
- Email correspondence
- Twelve months after the last message in the thread, then deleted. Threads establishing a published correction are kept longer as part of the editorial record described in our editorial policy.
- Server access logs
- Ninety days: long enough to investigate an intrusion, short enough not to become an archive.
- Analytics data
- Aggregate reports for fourteen months. The identifying cookies expire after two years and twenty-four hours.
- Records kept for legal reasons
- Up to six years where tax or limitation periods require it, then deleted or irreversibly anonymised.
Your rights
Article 15 gives you a copy of the personal data we hold about you, and we have thirty days to provide it. Article 16 covers correction of inaccurate data and Article 17 erasure where no lawful ground for keeping it survives. Article 18 freezes processing while a dispute over accuracy is resolved, and Article 20 lets you take what you gave us in a machine-readable file, which for this site means an export of your correspondence.
Article 21 covers objection to anything done on the basis of legitimate interests, and consent can be withdrawn without explanation. Californian readers may request disclosure of the categories collected, request deletion and correct inaccuracies; we neither sell nor share personal information as the CPRA defines those terms, so no opt-out link is required.
Write to [email protected] to use any of these. We acknowledge within seventy-two hours and complete within thirty days. Unsatisfied EEA readers may complain to their national supervisory authority, UK readers to the Information Commissioner's Office, and readers dealing with the New Zealand side to the Office of the Privacy Commissioner.
Security
Connections run over TLS, so an intermediary on a public network cannot see which pages you opened. The site is static HTML with no database and no user accounts, which removes the two components behind most breaches of small publishing sites.
Administrative access is protected by two-factor authentication and limited to the people who need it. Software is patched on the provider's schedule and backups are encrypted at rest. No system is immune, and saying so plainly beats promising otherwise.
Adults only
The site is written for readers aged eighteen and over and is unsuitable for minors. We do not knowingly collect data from anyone under eighteen and have no mechanism that would invite it. Anything reaching us from a minor is deleted without a copy being kept, and a parent who believes their child has written to us should contact the privacy address for confirmation.
Changes
This policy changes when the site changes, and a new analytics tool or hosting arrangement requires an update here before it goes live. The revision date at the top reflects the current version, and a change broadening what we collect triggers a fresh consent request instead of relying on an old banner.
Who is behind the project is described on the about page, and anything unclear above is worth an email through the contact page.