Privacy Policy

Clear rules for Pint Path data.

Pint Path collects only the information needed to run a Melbourne beer price, happy-hour, contribution, and venue-insight platform safely.

Last updated: 12 July 2026. Privacy, access, correction, export, and deletion requests can be sent through the tracked Contact us form or Account support controls.

Plain-English beta summary

Public users can browse approved venue, beer-price, and happy-hour information. Accounts are used for submissions, saved preferences, contributor points, venue manager access, billing flows, support, and privacy requests. Venue managers see assigned venue tools and aggregate insights only; private user evidence and individual click paths are not sold or shown to bars.

What we collect

We may collect account details such as email address, display name, sign-in provider, account status, subscription/access tier, 18+ self-confirmation status, contribution points, fraud strikes, upload counts, review outcomes, support/feedback messages, saved venues/beers/areas, and preferences you choose to save.

When you submit data, we collect the venue, beer, serving size, price, happy-hour details, automatic submission timestamps, mission context where relevant, upload-location proof where you choose it, and private source evidence when you upload a menu, receipt, or tap-list photo. Raw evidence is not public map data.

Service providers and integrations

Pint Path uses Railway for application hosting, Supabase for authentication and selected database/storage services, Google Maps/Places for maps and venue lookup, Stripe for payments and billing management, and private server or Supabase storage for source evidence. Security and abuse-prevention providers may process limited request metadata needed to protect the service. Source-evidence retention is controlled by the service retention policy and private signed access.

Search, analytics, and venue reports

We collect product analytics such as searches, filters, map marker clicks, venue views, price-detail views, happy-hour interest, beer-list views, area context, radius selections, and interaction timestamps. These events help us improve coverage and generate paid venue insights.

Venue reports are aggregate-only. We do not sell or expose individual user names, emails, exact user locations, private click paths, raw source evidence, or individual account data to venues. Small data buckets are suppressed so venue reports do not expose tiny or identifying groups.

Location

Location is used only when you choose a location feature, such as "Use my location", near-me sorting, or upload-location proof. If you allow location on the map, we may remember that on-device preference so the map can ask your browser for one-time location again on future visits. You can turn it off from the location button. Nearby browsing uses approximate browser location for distances and map relevance. Analytics may store coarse context such as area, distance bucket, or selected radius, but not continuous movement trails.

If you submit venue data, we may save a private, one-time upload-location proof so reviewers can decide whether contribution points should be awarded. This is used to reduce fake submissions from home and is not shown publicly or sold to venues.

Age and rewards

Pint Path is intended for adults aged 18+ in Victoria. We may store an 18+ confirmation status and, in future, a third-party age-verification provider reference. We do not store raw ID documents, licence numbers, passport numbers, Medicare numbers, or ID images.

Leaderboards and venue discounts

If leaderboards are enabled, they may show a public Pint Path account ID, optional display name, rank, approved submission count, and contribution points. Leaderboards do not show your email address or private upload evidence.

If you choose to show a rotating discount code or QR code at a venue, we may record that explicit redemption, including the public account ID, venue, item or special, quantity, estimated savings, and timestamp. We do not use discount passes for passive location tracking or hidden drink tracking.

How we use information

We use information to operate accounts, authenticate users, prevent abuse, review submissions, publish verified public price data, calculate contribution points, provide paid access, support users, improve map coverage, prepare privacy-safe venue reports, and protect the integrity of the platform.

Who can access information

You can access your own account and submission information. Admins/reviewers can access private submission evidence where needed to verify data and investigate abuse. Assigned venue managers can see only their own venue tools and aggregate insights that meet privacy thresholds. Public users see only approved public venue, beer-price, and happy-hour data.

Security and retention

We use authentication, server-side authorization, private storage for evidence, rate limits, audit logging, and review workflows to protect the service. No online service is perfectly secure, so users should not upload sensitive ID documents or unnecessary personal information. We keep data while needed for the service, auditability, abuse prevention, legal obligations, and product analytics, then delete or aggregate where practical.

Your choices

You can browse public map data without an account. Uploading, verification, saved items, and contributor features require an account. Signed-in users can manage optional analytics and venue-report inclusion from the account page. You can request correction, deletion, export, or account support through Contact us. Some records may need to be retained for fraud prevention, payment records, moderation, audit logs, or legal reasons.

Account deletion and export

Signed-in users can open Account, choose Support, download a quick JSON export, or request deletion review. The self-service export includes account-linked submission location fields so you can see the exact location data Pint Path holds about your uploads. It does not include raw passwords, raw tokens, private evidence files, or raw photo bytes. Deletion requests create a tracked admin review so ownership, billing, moderation, security, fraud-prevention, and legal retention requirements can be checked before account data is removed or anonymised where practical.

If you cannot sign in, use Contact us and choose "Account deletion request" or "Privacy request". Include the account email and enough detail to verify ownership. Do not send passwords, payment card numbers, private keys, ID documents, or unnecessary personal documents.