YOUR INFORMATION
LAST UPDATED OCTOBER 10, 2026
Privacy Policy
Account information
We process your email address, display name, age or date of birth, profile photo, optional phone number, account settings, and account status. A confirmed email, display name, and age 16 or older are required for onboarding.
Identity verification
Identity verification is required before creating or joining a Check. Stripe Identity asks you for a government-issued ID and a matching live selfie. Stripe processes those materials and returns a verification status and verified date of birth to WEOAUS. Government documents, the selfie collected by Stripe, and your full date of birth are not displayed to other members. A separate current in-app Check photo may be shared with the other Check participant. When you choose a new profile photo, WEOAUS compares it with the selfie Stripe checked during identity verification, using AWS Rekognition CompareFaces. The comparison is probabilistic and is not a guarantee of identity. If it passes, the chosen photo is saved as your profile photo. Existing legacy profile photos are not automatically rematched. WEOAUS does not save a copy of the Stripe selfie or a reusable face template in AWS. A temporary Stripe selfie file reference is retained for up to 48 hours to support the comparison, then expires or is deleted.
Private Checks and conversations
We process Check roles, one-time codes and expiry status, agreement versions and acceptances, ticket and deal details, private Check photos, messages, receipt and trade confirmations, and completion records. Both participants accept the same agreement, and a change requires renewed acceptance. A completed Check records what participants stated and confirmed. It does not independently verify payment, ticket authenticity, possession, transferability, behavior, or venue entry.
Ticket proof and supporting evidence
On compatible iPhone builds, a Check may request a prepared screenshot, screen recording, or both as ticket proof. This flow attempts local barcode and QR masking, removes image metadata and recording audio and metadata, and checks recorded device capture time and large video timeline gaps. Only the prepared copy is uploaded after you review it. Supporting evidence is separate from ticket proof. Supporting evidence currently accepts image uploads only in three categories: Ticket context, Payment receipt, and Transfer confirmation. New supporting images go through local barcode and QR masking and a required visual review before upload. They do not receive the ticket-proof capture-time or video timeline analysis. Supporting images uploaded before this protection was added were not retroactively redacted. These controls provide limited technical signals. They are not authenticity detection, cryptographic provenance, proof of ownership, or a guarantee that a recording is continuous or every barcode or QR code is detected. Inspect every prepared item and hide barcodes, QR codes, passwords, payment numbers, and identity details before sharing.
Connected accounts
Connecting an account is optional. Discord and Facebook use their authorization flows. Reddit control uses a private one-time challenge and does not require your password or inbox access. A username selected for a deal may be shown to the two participants with its actual confirmed or unconfirmed status. Your full connected-account list remains visible only to you.
Notifications, diagnostics, and safety
We process device push tokens and notification message previews through Expo so we can deliver alerts. We also process diagnostic, performance, error, security, and access logs needed to operate and protect the service. Safety reports may include the reported Check, messages, evidence, and account information needed for review. The public website and its hosting provider may process ordinary visit and technical analytics, such as requested pages, device or browser information, referral information, and error data. The private Check invitation page applies stricter privacy controls, including a no-referrer policy and controls that prevent third-party analytics scripts from running on that page. Hosting access records may still exist.
Reporting suspected fraud and authority requests
You can report suspected ticket fraud in the app. A report preserves relevant Check details, messages, evidence, and account identifiers for authorized staff review. A report is not proof of wrongdoing and is not automatically sent to police. You may contact your local authorities and provide the WEOAUS report reference. WEOAUS reviews official authority requests, verifies the requester and legal basis, limits disclosures to what is required or permitted by applicable law, and keeps an internal record of the request and decision. WEOAUS does not promise to contact police in every country. WEOAUS never shows or gives one participant another person's government ID, Stripe identity documents, or full date of birth.
Who can access information
Check records, conversations, and selected evidence are available under participant access rules. Authorized safety personnel may access reported records for review. We use ordinary access controls and private storage, but no online service can promise absolute security. Screen recording and mirroring protections also have limits and cannot prevent another camera from capturing a screen. Public website invitation previews use only the limited fields approved for that preview. They do not expose private messages, evidence, account identifiers, exact locations, identity documents, or barcodes.
Service providers
- Supabase: authentication, database, and private storage
- Stripe Identity: government ID and live-selfie verification, and the selfie used for profile photo comparison
- AWS Rekognition: comparing a newly chosen profile photo with the selfie Stripe checked. AWS processes the images to perform the comparison. WEOAUS has opted out of AWS using this content to improve its services.
- Expo: push notification delivery and message previews
- Apple: app distribution and device services
- Email providers: service and support email delivery
These providers process information as needed to provide their services and under their own terms and privacy policies.
Location and earlier data
Core ticket Checks do not need precise location, and WEOAUS is not currently positioned as a location-based social product. If location information from an earlier product version remains associated with your account, the access and deletion rights below still apply.
Retention, deletion, and your choices
You can manage notification permissions on your device, decide whether to connect outside accounts, and choose what evidence to share. To request account deletion, use WEOAUS Settings. If you cannot access the app, email support@weoaus.ca from the address on your account.
A deletion request immediately deactivates your account and signs you out. Unclaimed codes stop working. Active Checks close and become read-only. Account deletion is completed after the longest applicable shared-Check retention period. A connected Check, its agreement versions, conversation, receipts, and private evidence are preserved for at least 30 days after the deletion request or Check closure, whichever is later, so the other participant does not lose the shared record. Reported Check records are kept while a report is open or under review, then for 30 days after resolution or dismissal. A documented legal hold can extend retention until the hold is released, followed by the 30-day period. The longest applicable period applies. Scheduled cleanup removes the Check record and private evidence after that period. Providers may retain their own data under their terms and legal obligations, including Stripe Identity materials. WEOAUS account deletion does not instantly erase data held by Stripe or other providers.
Changes and questions
We may update this policy as the service changes. The updated date above identifies the current version. Questions and privacy requests can be sent to support@weoaus.ca.