Who operates Pint Path and how to contact us
Pint Path is a registered business name operated by Isaac William De Worsop, an Australian individual/sole trader, ABN 80 319 578 329.
Address for service of documents and principal place of business: WOTSO, Level 3, 11–19 Bank Place, Melbourne VIC 3000, Australia.
Privacy and general enquiries: admin@pintpath.au
Send privacy complaints in writing with enough detail for us to investigate. We aim to acknowledge requests within two business days and provide a substantive response within 30 calendar days, or explain why more time is reasonably required. If you are not satisfied after allowing a reasonable response period, you may contact the Office of the Australian Information Commissioner.
Plain-English beta summary
Public users can browse approved venue and beer-price information. Consumer happy-hour discovery and contribution controls are hidden for the current launch scope, while assigned venue-manager and admin tools may still maintain that data for a later approved scope. 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, user or public account ID, account status, subscription/access tier, purchase and billing-status history, 18+ self-confirmation status, contribution points, fraud strikes, upload counts, review outcomes, customer-support/feedback messages, saved venues/beers/areas, and preferences you choose to save. Stripe processes full payment-card details; Pint Path receives billing identifiers and status rather than full card numbers.
When an enabled contribution or assigned venue-management tool accepts data, we may 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, tap-list photo, or other user content. The current public contributor flow does not offer happy-hour submission. Raw evidence is not public map data.
The website and iOS app may process a persistent app-install identifier, device/platform details, app version, product interactions, search and filter history, diagnostic or security events, notification state, IP-derived request metadata, and coarse or precise location only for the location features you choose. These fields support sessions, abuse prevention, troubleshooting, privacy-safe analytics, and the features described below.
Service providers and integrations
Pint Path uses Railway for application hosting, Supabase for authentication and selected database/storage services, Google for configured web sign-in plus maps and venue lookup, Apple for iOS app/platform services, Stripe for payments and billing management, OpenAI for controlled menu-evidence extraction, Resend for account-deletion completion notices and optional transactional venue-report email, 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.
The selected primary and independent-backup Supabase projects were verified in Australia on 28 July 2026. Pint Path has not yet completed an evidence-backed country inventory for the active Railway region or every provider's support, security, and resilience processing. Public launch is blocked until those actual locations are recorded, any likely overseas recipient countries are published here, and the required Australian privacy safeguards are approved. Pint Path will not guess provider countries.
Search, analytics, and venue reports
We collect product analytics such as searches, filters, map marker clicks, venue views, price-detail views, beer-list views, area context, radius selections, and interaction timestamps. Historical records, or events collected only if a later approved scope enables the feature, may include happy-hour interest. These events help us improve coverage and generate privacy-thresholded 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.
Alcohol-linked Pint Points, Free Pint Rewards, Pub Golf, and the associated drink log are paused for the public launch. The drink log will not be enabled unless Pint Path first resolves whether its records are health information under Victorian law, obtains any required consent, and publishes the applicable collection, access, correction, security, retention, deletion, and overseas-disclosure controls.
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.
Email and direct marketing choices
Essential account, security, privacy-request, billing, trial, and service messages are sent when needed to provide or protect the service. Promotional or research email requires a separate, specific choice unless another lawful basis clearly applies. Pint Path records the consent wording, source, time, and version where consent is used.
Commercial email identifies Pint Path and includes working sender/contact details and an easy unsubscribe method. Unsubscribe requests do not require login, remain functional for at least 30 days after the message, and are actioned within five working days. Unsubscribing from marketing does not stop essential service messages.
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 currently see approved public venue and beer-price data; approved happy-hour data would be public only if consumer discovery is deliberately enabled under a later approved scope.
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.
Current automated limits are: authentication sessions are deleted 30 days after expiry or revocation; globally revoked provider-session records are retained for 90 days; raw Stripe webhook payloads and security request fingerprints are redacted after 30 days; Stripe event and security-audit envelopes are retained for up to 400 days; reviewed exact upload location is purged 30 days after review; source evidence normally expires after 90 days and has a 180-day hard cap; pending ingestion image bytes expire after 90 days with a 180-day hard cap; and migration quarantine payloads and migration backups expire after 30 days. Off-site backup retention is configurable from 7 to 30 days.
The final schedule for account profiles, approved public submissions, support cases, consent records, billing records, analytics, moderation records, deletion evidence, and legally required financial records is not yet approved. Public launch is blocked until each category has an owner-approved purpose, period, deletion action, backup treatment, and legal basis, and this policy is updated to match.
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 schedule account deletion. 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.
A deletion request has a clearly displayed seven-day cancellation window. After that date, the current reviewed workflow revokes Pint Path sessions and discount passes, deletes a configured Stripe customer and Supabase identity, removes private source evidence, raw submissions and item text, contribution-ledger rows, and public prices derived from those submissions, records an independent deletion tombstone, and deletes or anonymises the remaining account-linked records covered by the published retention policy. Failed provider steps remain saved for retry. Records that must lawfully be retained are access-restricted and must be deleted or anonymised when that reason expires.
Pint Path aims to complete verified deletion requests within 30 calendar days. An authorised operator executes the irreversible provider and anonymisation steps after the cancellation window. When deletion commits, a transactional completion notice is queued automatically. Its destination address is held separately using authenticated encryption and removed on verified delivery, an audited terminal resolution, or no later than 30 days after deletion completion. If deletion has not completed, the held encrypted destination is removed after at most 60 days. Backup and migration copies exclude and securely compact away this separate recipient secret before retention or upload. Only non-identifying delivery and audit metadata is retained afterward.
The current iOS release does not include native Apple or other social sign-in, and production must keep Apple OAuth disabled. If Apple sign-in is enabled later, Pint Path must implement and verify Apple authorization-token revocation before that release.
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.