Privacy Policy
Last updated: May 2026.
This Privacy Policy explains how we—the operators of “Biker Friendly”—collect, use, disclose, retain and safeguard personal information when you use our mobile Application and the online Services that power accounts, publisher listings, uploads, feedback, ingestion, maps, moderation and reliability work.
“Operators”, “we” and “us” mean the operating team referenced in our Terms of Use.
Apple processes its own categories of information through iOS, the App Store, entitlement checks, crash diagnostics, MapKit-related features and purchases Apple intermediates. Read Apple’s privacy materials together with this Policy.
If anything in this Policy conflicts with mandatory privacy law where you reside, that law wins to the fullest extent.
Who and what this covers
This Policy covers personal information we process to deliver what our Terms describe. It reaches authentication records, publisher and listing fields, moderated content queues, voluntarily submitted feedback, diagnostics you attach when you send feedback (which can include navigation breadcrumbs, mirrored console logs and coarse device identifiers), ingestion outputs publishers trigger, transactional email routed through hosted infrastructure we configure, coarse coordinates tied to listings, and ordinary server logs subprocessors emit.
Independent websites, social platforms or ticket merchants publish their own policies for anything you browse outside our App.
Categories of personal information
Depending on features you enable, typical categories include:
• Identification and credentials: pseudonymous identifiers, email-like addresses mandated by authentication partners we configure and session artefacts needed to operate sign-in securely.
• Publishers’ content: descriptive text, photos, addresses, subdivisions or regions, ticketing links, scraped previews, summaries or metadata you upload.
• Support artefacts: typed feedback plus optional diagnostics files we assemble only when you include them explicitly.
• Location context: coarse coordinates inferred from submissions or geocoder results tied to publisher forms or approximate map viewpoints—there is no always-on fleet-tracking service operated from our backends.
• Technical metadata: timestamps, abbreviated IP-derived security signals or request fingerprints generated by reputable cloud subprocessors for uptime, auditing and misuse detection.
How we use information
We use personal information only for compatible purposes: • providing and defending publisher accounts, • publishing, ranking or moderating submitted listings, • troubleshooting stability, diagnosing abuse patterns and safeguarding infrastructure, • operating feedback, ingestion and email routing you voluntarily trigger, • communicating about misconduct, outages or lawful requests impacting you, • satisfying taxation, accounting or regulatory retention obligations when required.
We refrain from repurposing identifiable listing data for unrelated behavioural advertising profiles.
Recipients, subprocessors and transfers
We disclose information only to teammates, professional advisers covered by confidentiality or technical subprocessors that host object storage, relational databases, realtime channels, transactional email, ingestion jobs and redundancy backups—for example deployments built on Supabase-related infrastructure in regions we select. Contracts impose confidentiality compatible with industry standards.
Processing may transit or reside outside your province, including in the United States or the European Economic Area, because cloud vendors operate globally. We do not sell contact lists purely for unrelated third-party promotional consideration; statistical insights stay aggregated wherever feasible.
Where regulators publish cross-border expectations, we follow reasonable guidance aligned with lawful transfers.
Maps, coordinates and device signals
Listings rely on coarse coordinates publishers supply or approximate geocoder results produced when addresses are keyed in. Map-related telemetry that Apple gathers follows Apple disclosures and is outside our dashboards for continuous surveillance.
Treat publisher-supplied coordinates as approximate unless you independently verify onsite.
On-device diagnostics and Clear logs
Ephemeral navigation breadcrumbs and mirrored console output may reside offline inside your device caches for troubleshooting parity with common tooling. Unless you voluntarily attach bundles inside Send feedback, the contents stay on-device while routine server logs reflect connection metadata.
Clear logs removes locally stored diagnostics buffers—it does not, by itself, delete historical publisher records synced to hosted Services.
Retention
We keep information only while purposes above remain valid unless law demands longer—for example moderated evidence, invoices or mandated security artefacts. Removing in-app listings or deleting the Application queues eventual erasure asynchronously; residual encrypted backups expire according to rolling schedules typical for reputable clouds.
Use Send feedback with specifics if you seek accelerated timelines wherever realistically possible.
Security
Safeguards include TLS transport encryption, partitioned access scopes, hashing where prudent, alerting through infrastructure vendors when bursts look abusive, and disciplined change procedures. Absolute security remains impossible.
Should we discover an incident that materially jeopardises people, we will seek to mitigate it and disclose outcomes as statutes require.
Choices and privacy requests
Depending on PIPEDA, Quebec Law 25 or comparable statutes, you may pursue access, correction, deletion or portability remedies we may honour through prudent procedures—update publisher listings directly, uninstall the Application, or outline requests using Send feedback with identifiers needed for responsible verification.
You may decline optional diagnostics attachments absent regulator or judicial orders narrowing that choice.
Children
The Services follow Apple minimum-age guidance—generally four or older unless supplemental parental regimes apply locally. Promptly alert us through Send feedback if we appear to retain a child’s personal information improperly so legitimate deletion paths can activate.
Updates and contact
This Policy may change; the Last updated label tracks revisions. Continued interaction after materially broader collection commonly signals acceptance unless statutes require additional steps.
Privacy questions arrive through Send feedback in Settings or via https://www.bikerfriendly.app.