Plan together.
Stay in control.

Your FairYes data

The current FairYes beta requires a connection to load and save trips. This rebuilt version does not offer offline trip downloads or a 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. Signing out 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.

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.

The current rebuilt beta 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: imsoflat12@gmail.com. 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.