FairYesFAIRYES · ACCOUNT & PRIVACY
Your privacy
Your trips work in your browser
Open FairYes to plan trips, invite friends, manage your password, and contact support. No download is required.
This separate account service remains available for account deletion and support.
Privacy and data information
Your FairYes data
FairYes requires a connection to load and save shared trips. You can explicitly export a private itinerary guide for offline reading or a calendar file for your calendar app. These exported copies do not update automatically and are not removed when you sign out or delete your account; delete them from your device and any destination you shared them with. FairYes has no passport vault. Saved changes awaiting confirmation and pending invitations may be retained privately on your device so you can safely retry or continue after sign-in. Unconfirmed trip-photo uploads are encrypted on this device and can be recovered for seven days; they are sent only when you retry. Signing out removes the saved photo upload and clears the current account’s private interface.
Your Activity inbox stores friend and shared-trip updates for 30 days. Phone alerts are optional, use Expo and Apple notification services, and show generic text without names, destinations, messages or costs. We store your most recently registered device token and notification choices; changing accounts on that phone detaches the previous account. You can turn alerts off, choose categories and mute individual trips. Delivery is not guaranteed and these are not emergency alerts. Included destination photographs work offline and show source and license credits. Online suggestions and photos use Google Maps as described below. Photo availability varies by location.
FairYes stores your account link, shared trip details, invitations, and planning responses. Your organizer sees your chosen display name while confirming your request to join. Your profile email stays private. This version does not collect, hold, send, or refund money.
Friend requests share your chosen display name and need both people to accept. Friends can see only plans they both already have permission to access. Other trips stay private. Private drafts are visible only to their creator. Reusing a plan copies its title, destination, and cost labels, with fresh dates, prices, invitations, and responses. Deleting an account removes its friend profile, connections, private friend invitations, and drafts. Private friend links expire after seven days and can be revoked. Only a token hash is stored on the server. New friend links connect both accounts when the recipient signs in and accepts. Older links require the sender to confirm a request. Friendship does not grant access to a trip. Social trip cards are made on your device and contain only the previewed details you choose. Traveler names, costs, cost-note addresses, and invitation codes are excluded. Optional notes and destination names may contain private text, so review the card before sharing. Countdown images are static snapshots that reveal roughly when travel begins. Sharing uses the app you choose; saving asks only to add the chosen card to Photos and does not read your library. Recipients can keep a copy. No social account connection or automatic posting is required. Removing or privacy-redacting a source plan clears unpublished copies. Published new plans are separate records under their own access rules. Request-recovery references help prevent duplicate saves and are removed with the account. References older than 90 days are pruned when you next save. When Google search is available, typing destination searches sends the search words to Google through FairYes. Results and categories help you explore the area. Selecting a destination saves its name to the trip. The destination search notice below explains what is shared. If you choose an itinerary map button, FairYes opens Google Maps with that stop’s meeting place and the trip destination. It does not include traveler names, notes, costs or invitation links. Google receives that search and your network information under its own policies. Check the map result before traveling.
Trip tools let organizers appoint managers and offer ownership to another joined traveler, who must accept. Recorded expenses store who reports paying, selected travelers, their shares, approval status and dates. Pending submissions do not affect balances. These are records, not verified payments. Confirmed members can read trip chat, expense records and attachments, including people admitted later. Emergency contacts are shared with a trip only after you confirm permission. Embassy details entered by travelers are not verified by FairYes. Do not upload passports, payment-card details or private identity documents to chat or trip files.
FairYes has no private passport profile. If you used that feature in an older app version, those local records are separate from the current FairYes service. Do not put identity documents in shared trip files.
Optional push and SMS alerts require separate consent and service activation. Trip alerts default off and can be muted by trip. Enabled alerts store your device push token or your provider-verified phone number privately. Generic activity notices are sent to Expo/Apple/Google for push or the activated text provider; chat content, destination and passport details are excluded. Legacy trip-alert delivery attempts and provider references are retained up to seven days. Activity-inbox delivery references remain with the update for up to 30 days; temporary device-token snapshots for pending delivery receipts are removed within one day. Delivery can fail or be delayed and is not an emergency service. Message and data rates may apply. Reply STOP to stop texts; a suppression record of the number is retained to honor that request even after account deletion, until a verified START request. START does not automatically re-enable alerts in the app.
Deleting your account deletes the plans you own for everybody. In other groups you joined, your access and personal decision records are removed; original historical names and written details are removed. Other travelers keep their own decision dates and numeric receipts, clearly marked as redacted. Current plans belonging to other organizers remain and need a new review. Copies already exported by other people are outside FairYes.
A restricted sign-in safety record is kept for 24 hours and then removed by scheduled cleanup. A separate restricted deletion record stores account identifiers and request/completion dates so deletion can be reapplied before a restored database reopens. During this private pilot, completed recovery records are retained for 8 days; their database backup history can retain earlier copies for another 7 days. Incomplete deletion requests remain until resolved. Trip database recovery history lasts 7 days. Restoration must remain offline until deletion records have been reapplied and checked. Deletion completion describes active application records and the sign-in account.
A content report lets our support operator review the reported plan’s title, destination, dates, traveler names, costs, copied terms, chat messages, and attached receipts or PDFs. Ordinary help reports do not include those details. Moderation notices remain for 30 days. Deleting your account also removes your reports and replies, including unresolved reports.
Operated by Curtis Parker. Contact: curtis@fairyes.app. Trip database recovery history: 7 days. Restoring a backup must preserve account deletion requests.
There are no ads, card collection, or marketing messages in this planning build. Sign-in codes are sent only when requested. Standard message rates may apply.
Destination search and photos
FairYes sends destination search text, selected place identifiers, and temporary search session identifiers to Google Maps to show suggestions and photos. Photo display also connects your device to Google. We do not send trip titles, traveler lists, costs, or FairYes sign-in tokens to Google. Destination names you choose are saved with your trip; Google photo details are held only temporarily for display.
Sign in with Apple
On supported iPhones, you can choose to sign in with Apple. Apple shares an account identifier and an email address, which may be a private relay address. FairYes does not receive your Apple password. We store an encrypted Apple authorization token on our server so we can revoke the connection when you delete your account. Use your original sign-in method to access existing trips; a different Apple or relay identity may create a separate account.
App reliability
FairYes uses Expo to collect technical diagnostics such as app version, device and operating-system information, startup timings, error reports and crash reports. These help us find and fix problems. FairYes does not intentionally attach your email, trip contents or messages to these reports. Crash diagnostics may be delivered after the app reopens.
Language and accessibility choices
FairYes remembers your chosen interface language on your device. It does not send private messages or trip contents to a translation service. The initial interface languages are English, Spanish, French and Portuguese; external services and some messages may use another language.
Optional accessibility requirements are shared with all current and future joined members of a trip. Use practical requirements only, with the traveler’s permission; do not add diagnoses or identify a person’s disability. Only the organizer can update these choices. They stay with an archived trip and are deleted when the trip is deleted. Venue access information comes from Google when available. Missing information means unknown and must be confirmed directly with the venue.
Shared trip photo albums
Trip albums are separate from the friends feed. Any joined member can contribute photos, captions and image descriptions. All current and future joined members can view the album. Photos are stored privately with Cloudflare; embedded location metadata is removed. Each read checks current trip access. A contributor or organizer can remove a photo. Leaving or being removed from a trip ends access and removes that person’s contributions. Closing a trip keeps the album available in History. Deleting the trip or the organizer’s account deletes the album for everyone. Deletions queue stored photo files for cleanup; limited database recovery copies follow the retention period above.
Trip photos are visible to the group after upload and can be reported to FairYes support. Reports hide the photo from the reporter and let authorized support staff inspect and remove the reported content. Copies other members already saved cannot be recalled. Keep originals separately; the album stores smaller sharing copies, with limits of 200 photos per trip and 50 uploads per person per day. Contact curtis@fairyes.app for access, privacy or content concerns.
Free access and earlier purchases
FairYes is free for now, including the printable trip book and shared packing checklist. No card, trial countdown or automatic subscription is required. Meet travelers remains subject to its availability, age, consent and moderation rules. Travel bookings and venue costs are separate. If pricing changes later, we will show the terms and ask you to choose before starting a paid purchase. Saved trip books contain the shared itinerary and packing list; anyone you give a downloaded copy to can read it, and future changes or deletions cannot recall that copy.
For earlier website purchases, Stripe handles payment details. FairYes sends an opaque order reference and the chosen product to Stripe, not your itinerary, friends, messages or access requirements. Stripe may collect billing information, payment details and device information needed to complete payment, calculate configured taxes and prevent fraud. FairYes stores transaction references and payment, refund or dispute status to associate the upgrade with a trip. FairYes does not receive full payment-card details.
For earlier Apple purchases, Apple handles the payment sheet and RevenueCat verifies transactions using a random purchase-account identifier, product and transaction identifiers, purchase/refund status and necessary technical information. FairYes does not send your email or trip contents to RevenueCat. Sign in with the same FairYes account to recover an upgrade. Test transactions never unlock production purchases. Deleting a trip or account removes its access and does not itself request a refund; contact support first if you need purchase help. Payment providers may retain records under their own policies and legal obligations.
Stripe privacy policy · RevenueCat privacy policy · Purchase support
Optional travel partner links
Some travel links are affiliate links. FairYes may earn a commission on eligible purchases, as disclosed beside the link. Opening a link takes you to the provider, where you choose travel details and review prices, availability and cancellation terms before booking. The provider handles the booking and payment.
Affiliate links contain FairYes’s partner and campaign identifiers so the provider can attribute eligible bookings. FairYes does not add your name, email, trip ID, dates, private itinerary or accessibility requirements to these links. When you visit a provider, it receives ordinary browser and connection information and may use cookies or similar technologies under its own policy. No partner page or tracking script is embedded in FairYes’s travel cards.
Travel memories shared with friends
Posting is optional. We store the place, caption and photo you choose, your profile name, post and review dates, and content reports. FairYes reviewers check memories before approved posts appear to your current accepted friends. New friends can see your earlier approved memories. Reports hide a post from the person who reported it, and reviewers can remove content. Removing or blocking a friend ends their access; it cannot recall copies they already saved. Your private trip plans, costs and itinerary are not copied into a memory. Your saved-memory list is private to your account and contains references, not copies. Saved references are removed when the post is removed, you report it, or friendship access ends. Place searches filter only content you are allowed to see.
Photos use private Cloudflare storage. We remove photo metadata, including embedded GPS coordinates, before storage. We do not use your precise device location for these posts. Deleting a memory makes it inaccessible immediately and queues its photo for removal. Account deletion removes your memories and reports. Limited recovery copies follow the database retention period above. Contact curtis@fairyes.app about content or privacy.
Optional Meet travelers
This adult traveler area is opt-in. We save your traveler name, adult self-attestation, rules acceptance, outing details, join requests, reports and subscription status. Self-attestation is not identity verification. Reviewed outing titles, host names, city, area, activity, time, cost and venue information are visible to eligible signed-in travelers. Exact meeting points are available to accepted members and FairYes reviewers. Joining creates access to a separate shared trip, its chat and album, including content visible to current and future members; your other private trips are not published. Avoid personal addresses and private contact details in listings.
Apple/RevenueCat or Stripe process membership purchases and send status updates using an opaque FairYes account reference. FairYes does not receive full card details. Payment providers retain records under their own policies. Cancel your provider subscription before account deletion. Venue accessibility descriptions are host-provided information, not verified guarantees. Blocking/reporting and management of existing outings remain available without paid access.