Owner/legal review draft

Privacy Policy

Last updated: May 7, 2026

PostLane is built for community, plans, and everyday discovery. We use information to run accounts, profiles, posts, circles, chats, plans, events, safety tools, support, and account deletion. This page is written for public readiness and should be reviewed before final launch.

Account and profile data

We may process account details, authentication information, profile fields, profile photos or media you choose to add, visibility settings, verification status, and support information needed to keep your account working.

Friend graph and community data

PostLane may process friend connections, friend requests, blocks, circles, circle membership, invitations, invite links, posts, media, comments, plans, events, RSVPs, attendee context, and related moderation status.

Chats and coordination

We use chat and conversation information to deliver messages, coordinate plans, support event chat and circle event chat, and operate safety tools. If a chat feature is end-to-end encrypted or otherwise privacy-bounded, PostLane should not weaken that boundary; reports should include user-selected evidence when review is needed.

Split-cost tracker data

PostLane may support manual split-cost tracking for plans. In PAY.0 this is non-payment tracking only: users can record manual paid or unpaid status, but PostLane does not move money or hold balances.

Safety reports and moderation data

Reports, block signals, moderation notes, event safety details, and support messages may be used to review abuse, enforce the Community Guidelines, protect people, prevent fraud, and respond to urgent safety concerns. Community report submissions may include contact email, reporter username or profile link, reported username(s) or profile link(s), category, description, account, content, event, or chat references, timestamps, and optional follow-up preference. This information may be used for safety review, moderation, abuse prevention, support, legal compliance, and recordkeeping.

Device, diagnostics, and support data

We may use device, app, diagnostics, reliability, and support data to maintain account access, troubleshoot bugs, improve reliability, prevent abuse, and respond to help requests.

Future payment references

Future real-world event payments, deposits, tickets, refunds, disputes, or organizer payouts are not live unless separately approved and launched. If future payment tools are enabled, PostLane should store only the references and status needed for reconciliation, receipts, refunds, fraud prevention, tax, legal, and support obligations.

Stripe and secret handling

Future Stripe customer or payment references should be treated as planned-only until approved. Raw payment details and Stripe secret keys must not be placed in iOS, public website code, public Vercel environment variables, client logs, telemetry events, or public source control. Payment provider secrets should stay in backend or Edge Function secret storage if a future payment phase is approved.

Access controls

User-facing data should be protected with least-privilege access controls, including Supabase Row Level Security or equivalent backend access rules where applicable. Service or secret keys should remain backend-only and should not be exposed to browsers or app clients.

How we use information

We use information to provide PostLane, maintain account access, route chats and circles, support posts, plans and events, operate reporting and blocking tools, prevent abuse, troubleshoot reliability, support account deletion, and respond to support requests.

Data deletion and retention

You can request account deletion through the app when available or through the public Delete Account page. Some information may be retained where needed for safety, fraud prevention, security, legal obligations, tax, future payment records, dispute handling, or support records.

Contact

For privacy or account questions, contact support@getpostlane.com. For privacy or data concerns involving community behavior, you may also submit a community report.