Privacy Policy
Who this policy is for
This policy applies to visitors using the public ThreeNearMe website and to people who contact ThreeNearMe by email or through an available online Contact or enquiry pathway.
Information we collect
The information depends on how you use the site.
Contact & enquiry information
When you contact ThreeNearMe, the information collected depends on the enquiry type and the details you choose to provide. It may include:
- name and email address
- subject and message
- the relevant ThreeNearMe page
- correction information
- supporting context or source URL
- business or organisation name
- organisation website
- business information updates
- commercial-interest information
The online Contact form does not accept attachments.
Site & technical information
ThreeNearMe does not currently use behavioural advertising trackers, remarketing pixels, public account cookies, or browser account features on the public site.
Like most websites, technical providers may process request information such as IP address, browser details, requested URL, timestamps, security events, and response status so the site can be delivered, protected, monitored, and diagnosed.
How we use information
Information is used for clear operational and editorial purposes.
Review enquiries
Read, triage, administer and respond to messages sent through available Contact or enquiry pathways.
Maintain published information
Assess factual corrections, business information updates and supporting context so published information can be reviewed when needed.
Consider commercial enquiries
Review advertising and Spotlight enquiries while keeping commercial discussions separate from editorial recommendations.
Protect the service from abuse
Limit spam, duplicate automated submissions, misuse and security issues affecting the public site or Contact pathways.
Enquiries & review
Providing information can inform review. It does not control the editorial outcome.
Sending an enquiry does not automatically change published content, create a business claim, guarantee consideration or publication, or affect Top Three inclusion, order, scoring, or selection. Editorial recommendations remain independent.
Commercial enquiries are handled separately from editorial decisions, and payment cannot buy Top Three inclusion or position. For more detail, read the Editorial Policy and Advertising & Spotlights.
If an online enquiry is accepted, public responses include only a correspondence reference such as TNM-.... There is no public tracking or status portal.
Service providers
Providers support hosting, security, storage, email and monitoring.
ThreeNearMe uses service providers to host, secure, monitor, store and deliver the public website and Contact workflows. Providers may change over time, but ThreeNearMe aims to keep provider access limited to the purpose of the service they provide.
When the online enquiry form is available and an enquiry is accepted, Supabase/PostgreSQL is the authoritative private storage for the enquiry record.
Cloudflare
Website delivery, security, and bot or abuse protection for the online enquiry form through Turnstile when that form is used.
Supabase/PostgreSQL
Authoritative private storage for accepted online enquiry records and related retention state.
Resend
Operational email delivery for internal notifications and simple receipt-only sender acknowledgements where configured.
Better Stack
Operational monitoring for uptime and backup heartbeat checks.
Authorised ThreeNearMe administrators and editors review enquiries through private administrative systems. Email pathways and notification workflows may also create operational copies in ThreeNearMe mailboxes or provider systems.
Resend is used as the email-delivery provider for internal operational notifications and, where configured, simple sender acknowledgements after an online enquiry is accepted. A sender acknowledgement is a transactional receipt with the correspondence reference. It is not approval, marketing consent, a promise of response time, or a decision about a correction, business update, advertisement, or recommendation.
Security & abuse prevention
Contact pathways use security checks without turning enquiry records into raw-IP logs.
ThreeNearMe uses technical controls to protect Contact pathways from spam, repeated automated submissions, and misuse. Cloudflare may process technical request information for website delivery and security. When the online enquiry form is used, Cloudflare Turnstile helps distinguish legitimate visitors from automated abuse. See Cloudflare's Turnstile Privacy Addendum for Turnstile-specific privacy information.
Network and request information may be processed transiently for security, bot detection, rate limiting, and troubleshooting. Raw IP addresses are not persisted with normal enquiry records by default.
ThreeNearMe may derive a privacy-conscious security identifier from network or request information to help limit abuse and repeated automated submissions; this identifier is generally kept for about 30 days unless a security, abuse, legal, dispute, editorial-accountability, operational, or retention-hold reason justifies keeping it longer.
Retention
Retention should be understandable.
Retention depends on the enquiry type, whether the enquiry has been closed, and whether there is a hold or downstream editorial-accountability reason to keep a record. These are the current target periods for Contact enquiries:
Ordinary enquiries
Generally up to about 24 months.
Applies to general, business information, advertising and other enquiries unless a reason supports a shorter or longer period.
Correction submitter identity
Structured name and email fields are generally anonymised after about 24 months.
This applies where no retention hold or other exception applies.
Correction editorial provenance
Correction records may be retained for up to about 5 years.
This supports editorial accountability before final deletion, unless a reason to retain longer applies.
Anti-abuse identifiers
Generally around 30 days.
Privacy-conscious derived identifiers may be retained longer for security, abuse, legal, dispute, operational or retention-hold reasons.
Operational email copies
Generally no longer than about 24 months by default.
Mailbox and provider copies are handled separately from the database retention lifecycle and remain subject to operational and legal requirements.
Operational logs
Shortest practical infrastructure and security retention.
Logs should minimise personal data.
ThreeNearMe may keep information longer where needed for legal, security, dispute, abuse-prevention, editorial-accountability, operational, or retention-hold reasons. Deletion or anonymisation may also be delayed where a record is linked to a correction outcome, an active review, an unresolved issue, or another accountable editorial decision.
Correction anonymisation does not guarantee that personal information typed into free-text messages, correction details, supporting context, or source descriptions will be removed automatically. If enquiry information is independently incorporated into an editorial issue, research project, source assessment, correction record, or published update, that downstream editorial record may remain after the original enquiry is anonymised or removed.
The database retention lifecycle does not automatically delete external mailbox or provider copies created by email pathways or notification workflows.
Privacy requests
Questions about privacy?
Email privacy@threenearme.com for privacy questions or requests. Privacy and legal enquiries remain on the dedicated privacy pathway rather than a default Contact-form type.
ThreeNearMe links to third-party business websites and other public sources. Those external sites have their own privacy practices. For factual updates, see Corrections. For general enquiries, use Contact.