SocialPageFinder

Privacy Policy

Effective: 18 September 2026 · Version: 2026-09-18

1. Who we are and how to contact us

SocialPageFinder is a directory service operated under the business name FarmGateRun, based in Queensland, Australia.

Legal operator: Shane Thomas, trading as FarmGateRun.

For privacy questions, access or correction requests, account deletion or complaints, email admin@socialpagefinder.com with the subject “Privacy”.

2. Information we collect

What we collect depends on how you use the service:

Browsing and security: IP address, request and browser information, session identifiers, security checks and operational logs. Hosting providers may keep their own access and security logs.
Creating and maintaining an account: Email address, display name, a password hash, account status, language and time-zone preferences, verification records, and records of accepted policy versions. Registration asks you to confirm that you are at least 16; it does not currently request your date of birth or an identity document.
Account security: Verification and reset-token records; where two-factor authentication is used, an encrypted authenticator secret and hashed recovery codes.
Submitting or managing a listing: Page or business name, descriptions, social links, website address, category, country/region/city, language, uploaded images and descriptions, and contribution or management history.
Claiming a listing: The page concerned, the verification method, a domain email address where used, private written evidence of management rights, and the review outcome.
Other account activity: Saved favourites, reports, corrections, appeals, privacy requests and support correspondence.
Permitted imports: Listing information supplied by an authorised source, source contact and permission records, original and corrected import rows, duplicate-review outcomes and provenance records.

We do not ask you to provide government identity documents, social-platform passwords, or payment-card details through the current directory. Do not include sensitive or unnecessary personal information in descriptions, reports or evidence. If we receive such information, we will review whether it is needed and can lawfully be kept.

3. Where information comes from

We collect information directly from you through forms, account activity, uploads and correspondence, and automatically when your browser uses the service.

We may also receive information about a listed person, creator or business from another user recommending a public page, or from an authorised import source. A listing can therefore exist even if its subject has never opened an account with us. The current application does not automatically scrape external social pages.

If a listing identifies you and you want to understand its source, correct it or request removal, contact us or use its report link. We will review the request and provide information we can appropriately disclose without exposing another person's private information or protected evidence.

4. Why we use information

We use relevant information to operate accounts and the directory; review and publish contributions; verify claims; resolve duplicates and disputes; handle reports and requests; send account and service emails; prevent abuse; protect security; troubleshoot failures; and understand use of the directory.

We may also use or retain relevant information to meet legal obligations or establish, exercise or defend a legal claim, where permitted by law.

You can browse public listings without registering and can normally use a display name rather than publishing your legal name. Account features require a working email address. Declining necessary information can prevent us from creating an account, reviewing a claim or completing a request. We ask for only the verification reasonably needed for the task.

5. What becomes public

Approved listing content, including descriptions, location fields, images and external links, can be viewed by anyone and indexed by search engines. Consider that before contributing information. Others may retain copies outside our control even after we remove a listing.

Your login email, password hash, private claim evidence, saved favourites and private reports are not intended to appear on public listing pages. If you put private details in public-content fields yourself, they may be published; do not do so.

Listing managers may receive summary activity counts for their listings. These reports do not provide a named list of individual visitors. Authorised staff can access records needed to operate, secure and moderate the service.

6. Cookies, analytics and Turnstile

Listing link counter (added 19 September 2026): We keep a separate count of visitors who follow each listing's external links. Signed-in accounts count once per listing; anonymous visitors count once per browser session using a random identifier in the existing session. This counter stores a listing identifier and a visitor key, with an account reference when signed in. It does not store click timestamps, IP addresses or user-agent details, and does not use Google Analytics or a new persistent cookie. These records are retained to prevent repeat counting while the listing is retained, subject to account deletion and privacy requests. Any public total will not identify individual visitors.

We use an essential session cookie to maintain login and support form security. Blocking it may prevent account features from working.

The application records limited first-party events such as searches, listing views and outbound clicks. Its analytics records contain event categories, timestamps, listing identifiers, selected filters or result counts, and deduplication values derived from an IP address using a key that changes daily. Raw search text, email addresses and raw IP addresses are not stored in that analytics event table. Separate infrastructure logs may contain IP addresses and request details. Hashing reduces exposure; we do not describe all such records as anonymous.

Advertising features and social embeds are disabled in the current application configuration.

Where enabled, we also use Google Analytics 4 after you accept optional analytics. It helps us understand visits to eligible public pages using cookies, browser/device information and page-view data. Account, administration and search-result pages are excluded from this integration, as are signed-in visitors. We supply public page URLs without query strings and limit the referrer supplied to its origin. We do not intentionally send form contents, account identifiers or private tokens. Google still receives technical information from your browser, including your IP address, when its tag runs.

You can reject analytics without losing access to the directory, or change your choice through Analytics preferences. Before acceptance, our integration does not load the Google tag or send it analytics requests. We save your choice in local browser storage for up to 180 days. The integration sets analytics cookies to expire after 60 days without renewal on each visit; deleting them or clearing browser storage can reset your preferences. Withdrawing consent stops subsequent collection by our integration and attempts to remove its accessible analytics cookies; it does not itself delete data already held by Google. See Google's Privacy Policy.

Google retains analytics information according to the settings of our Analytics property and its applicable policies. Cookie expiry and withdrawal of consent do not determine how long previously collected information remains in Analytics reports. Contact us if you need information about analytics data already collected.

We use Cloudflare Turnstile to help distinguish legitimate activity from automated abuse. Your browser connects to Cloudflare, which processes technical signals including IP and browser/device information for security purposes. Cloudflare explains its handling in its Turnstile Privacy Addendum. Turnstile is a separate service even where the website's DNS remains with Hostinger.

External websites and social platforms apply their own policies when you follow their links.

7. Providers and other disclosures

We use Hostinger for website hosting and the configured email service, Cloudflare for Turnstile, and Google for optional consent-based analytics. These services process the data needed for their functions, such as hosted account records, email recipient details and message contents, browser security signals, or public-page visit information.

We may disclose relevant information to technical contractors acting for us, professional advisers, and authorities where required or authorised by law. In handling a dispute, we may share the substance of the issue with the affected contributor or page manager while limiting unnecessary disclosure of the reporter's identity and private evidence. We cannot promise absolute confidentiality where disclosure is legally required.

We do not sell private account details or private claim evidence. Publishing approved directory information is different from making private records available for sale. We do not currently send promotional mailing campaigns. Any future marketing programme will be separately explained and provide the choices required by law.

8. Overseas processing

Our providers may process information outside Australia. The exact hosting, email, support and security processing locations depend on our provider arrangements; public listings can also be accessed worldwide.

Overseas handling may include the United States and countries in the European Economic Area through our global providers. The locations used for a particular record depend on the service and provider arrangements; we do not promise that information stays in Australia. Further information is available in the privacy policies of Hostinger, Cloudflare and Google. Contact us for information about the arrangements relevant to your request.

We will consider applicable privacy requirements when arranging overseas handling and use appropriate contractual and operational safeguards. This policy does not ask you to waive protections simply by continuing to use the service.

9. Security and retention

The application uses password hashing, access controls and encrypted storage for selected sensitive records such as private claim evidence and queued email contents. These measures do not mean every record or backup is encrypted, or that any internet service can guarantee security. We will assess suspected incidents and provide notifications where required by applicable law.

We keep information for the purposes described here and review whether it remains needed. Account deletion and removal of personal information require a review of active listings, ownership, reports and any justified retention obligations. A deletion request is not immediate erasure of all copies.

Retention depends on the type of record and why it is still needed:

Account and listing records are kept while needed to provide and manage the service, then reviewed when an account closes, a listing is removed or a privacy request is received.
Claim evidence and verification records are kept while needed to assess management rights, handle a review or resolve a dispute. Removing an evidence file does not necessarily remove separate claim metadata.
Temporary tokens, unfinished submissions, detailed analytics and original import files are subject to maintenance and retention review. Deleting an import file does not itself delete copied database rows, corrections or source-permission records.
Support correspondence, reports, moderation history, audit records and source-permission evidence may be retained for as long as reasonably needed to resolve the matter, protect security, explain a decision or meet a legal obligation.
Provider logs, mailbox copies, analytics reports and backups have separate retention arrangements. Backup copies may remain until the relevant backup cycle expires and are not intended for continued routine use after an approved deletion.

We consider whether the purpose is still active, the sensitivity of the information, applicable legal requirements and any outstanding dispute when reviewing retention. Where information is no longer needed and retention is not required, we take reasonable steps to delete or de-identify it. Contact us for information about a particular record or deletion request; we will explain any justified retention and applicable limitations.

10. Access, correction and deletion

You can update supported profile fields and use the account export feature for the records it includes. That export is not necessarily a complete response to a legal access request. Contact us for additional access, corrections, or information that concerns you in a listing contributed by someone else.

We may ask for reasonable identity or authority verification before disclosing or changing private records. Please do not send identity documents unless a suitable verification method has first been agreed. We will explain any refusal or limitation and available complaint options where required by law.

You may request account deletion through account settings or email. We will explain what we can delete, anonymise or remove from public view, and what must be retained and why. Deleting an account does not itself resolve a separate listing's status. Mandatory rights under applicable law continue to apply.

11. Young people

Accounts are for people aged 16 and over. The current registration process uses an age declaration, not independent identity or age verification. If you believe an account belongs to someone under 16, contact us so we can investigate and take appropriate action, including reviewing the account and its personal information.

Do not submit identifying or sensitive information about a child merely because it appears on another website. A listed external platform may impose different access or age requirements.

12. Privacy complaints and changes

Email admin@socialpagefinder.com with details of your concern and your preferred outcome. We aim to respond within 30 days. If we need more time, we will explain why and provide an update.

If unresolved, you may contact the Office of the Australian Information Commissioner where the complaint falls within its jurisdiction, or another relevant regulator. The OAIC explains its privacy complaint process. Nothing in this policy limits privacy rights or remedies available to you under applicable law.

We will publish an effective date with updates to this policy and provide appropriate notice of material changes. If a new use requires consent or another legal basis, we will address that before starting the use. Publishing a policy update does not itself supply consent.

Private enquiries — notice added 20 September 2026

Customers may choose to share their name, email and request privately with a verified page owner. See how enquiries use your information for sharing, outcome counts, withdrawal and retention details.