Detailed notices for current features

Detailed service documents · English

The current release includes Evently Social accounts and centralized Firebase processing for authentication, private and public profiles, username lookup, friendships, blocking, shared occasions, posts, post images, delivery state, and in-app notifications. Existing local and iCloud Evently functions remain separate.

Authentication, profile management, friendships, post delivery, and account-related synchronization are processed to provide the Social service requested by the user and to take steps related to the user agreement.

Date of birth is processed privately to enforce the Evently Social minimum age of 16. The full date and birth year are not shown in public profiles or username search. Birthday sharing is a separate feature and remains off until the user enables it.

Security, abuse prevention, App Check, blocking, moderation preparation, and service-integrity processing may be based on the operator’s legitimate interests and applicable legal obligations. Optional marketing consent is not enabled automatically.

Google LLC provides Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, App Check, Installations, and Core. Google may process account identifiers, email, profile and user content, technical identifiers, security signals, IP address, device and request metadata as required to operate these services.

Apple provides iOS, iCloud, App Attest, DeviceCheck, App Groups, widgets, Apple Watch, photo selection, and notification infrastructure. Local Evently and iCloud data are not automatically migrated into Social except for the account owner’s explicitly reviewed profile values.

Firebase and Apple affiliates may process data outside the EEA. Transfers may rely on an applicable adequacy decision, standard contractual clauses, or another lawful safeguard.

Active Social account data is retained while the account is used. A deleted post disappears immediately from normal user surfaces, while restricted deletion, security, and backup records may remain temporarily where needed for integrity, dispute handling, legal obligations, or backup rotation.

Account and content deletion requests can be made through the in-app account controls where available or at hello@tripelfy.com. A final production retention and backup deletion schedule must remain consistent with the deployed backend.

The app keeps account-scoped local cache copies of authorized social responses, messages, profiles, posts and images to reduce repeated data transfer. Copies can survive app restarts, use iOS file protection, and are excluded from Evently iCloud backups, widgets and Watch data. The cache is limited to 256 MB with a 12 MB response limit; older copies are evicted when the storage limit is reached. Saved data remains readable offline for the same signed-in account; startup and reconnection refresh previously loaded pages in the background. Signing out, changing accounts or acceptance of account deletion clears this cache. A saved copy does not grant continuing access: the server validates updates and permissions, and changes and deletions take effect at the next successful synchronization. This adds no tracking or marketing collection.

A place voluntarily selected for a regular post is stored in Firebase with its name and map coordinates and is visible to the post's selected audience. Apple Maps processes the entered place search query. This feature does not automatically read device location or photo GPS metadata. The place can be removed before publishing; published place data follows the post's visibility, account deletion and content deletion rules.

Users may request access, correction, export, restriction, objection, and deletion where applicable. Identity verification may be required to protect the account and other users.

Firebase Authentication stores the account email, verification state, password-derived authentication data, account UID, and authentication metadata. Password reset and email verification are handled by Firebase Authentication; the app does not store readable passwords.

Cloud Firestore stores public profiles, protected private account records, normalized username reservations, friendships, blocks, shared occasions, canonical posts, recipient deliveries, read state, and service metadata. Full date of birth and email are protected private account data.

Cloud Storage stores Social profile images and optional post images. Images are resized and compressed before upload. Access is restricted by authentication, ownership, post participation, Security Rules, and App Check as applicable.

Supplement dated 11 October 2026. Tripelfy social and account-based services must not be used by anyone under 16. Users aged 16–17 are minors; where applicable law requires a legal representative's involvement for a booking or another contract, this must be arranged before entering into that contract. The minimum age is not blanket consent to personal data processing. Access to the privacy notice, acceptance of service terms and optional analytics consent are separate matters. Firebase accounts, social content and chat, business bookings, and local/iCloud records involve distinct processing. The service processes chat messages and attachments on servers; we do not promise end-to-end encryption. Business bookings and related messages are also disclosed to the selected provider, whose privacy notice and booking terms must also be reviewed. Social account deletion does not replace the separate handling of business records or local/iCloud data. If in-app deletion is blocked, access, correction, erasure or restriction may still be requested at hello@tripelfy.com; records requiring retention under applicable law must be assessed individually. We normally respond to data subject requests within one month and communicate any justified GDPR extension within that period.

With your permission, Google Firebase Analytics summarizes the screens and features you use and the time you spend with the app in the foreground.

Measurement may also process an app-instance identifier, device and app information, and approximate location derived from your IP address.

We do not send Analytics your name, email, account ID, messages, calendar content or booking details. We do not collect advertising identifiers.

Consent is optional and applies to this app installation. All app features remain available if you decline.

Turn it off anytime in Settings. This stops measurement and resets the local analytics identifier; it does not delete data already sent.

Evently Shop account saves contain up to 200 product identifiers, a list revision and an update time in the account's private Firebase data. Up to 20 named gift lists and 300 list entries can also be stored, with personal notes of up to 280 characters and an already-purchased flag. Lists can be edited or deleted; deleting a list does not remove the saved products. The app and website use the same list; merchant and Shop-admin accounts have no access. Previous device saves are copied only after an explicit confirmation of the destination account; the local copy remains. Saves do not copy people, contacts or events. Account deletion erases the cloud list with the account's private records; local saves are managed separately. Prices and stock may change; purchases and orders take place at the selected partner store.

Firebase stores created social groups, memberships, text/photo group posts and ownership-transfer state; public event details and attendance responses. Saved items and collections belong to the saving account. Explicitly selected photo stories, their audience, likes, comments and story-view receipts are social data. Only the story author can request its viewer list. Group/event invitations, join requests and explicitly selected event cover images are also stored. Stories become inaccessible after 24 hours; scheduled cleanup removes expired story files. Marketplace is discontinued; account erasure still removes legacy data. New video uploads and video calls are unavailable; erasure handling for legacy video data remains. Reports enter a pending safety review queue; submitting a report does not automatically remove content. Memories use the account’s own earlier posts. Notification read state and conversation archiving are account data. Personal calendar search runs on the device and does not send personal occasions to social search.

The community service stores personal message text, sender/recipient identifiers, explicitly selected attachments and read state. Group chat stores members' text messages, sender, timestamp and per-account read position. Group chat and media require current membership, active accounts and block checks; the group owner has moderation rights. Ownership transfer grants management rights to the new owner while preserving group privacy settings. Following is separate from friendship: follower/followed account identifiers, relationship time and aggregate counts are stored. Only an account owner can request their own follower/following lists; aggregate counts belong to the available profile feature. Following supports already-public social posts and grants no private or friend-only content access. Blocking removes both follow directions between the accounts; unblocking does not automatically restore them.

When you submit a ticket through an available support feature, Firebase stores its subject, category, entered text, account identifier, timestamps, case status and related messages. The case content is accessible to its account owner and separately verified authorized operators; it is not public social content. Authorized operators may inspect reported content text and explicitly opened photos or videos for review. Content-report review records the decision, time and operator identifier. A removal decision hides the content immediately; a repeatable server task permanently deletes its media files and retries failures. Submitting a report does not automatically remove content or promise an automatic response or a fixed response time. These features become available with the app and its corresponding backend release; local development does not establish production availability.

Community account deletion from the profile requires fresh password authentication and final confirmation. An accepted request hides the profile and closes the community account. The server starts permanent erasure after at least 70 minutes to allow previously issued upload credentials to expire, and retries failures. It removes owned community content, media, legacy listing data, saved items and contributions. Groups still owned by the account at deletion are erased with members' content stored in those groups. Previously transferred groups remain; the deleting account's posts, media, comments, chat messages and read states are removed from them. Incoming/outgoing follow edges and owned support tickets are also erased. The deleting account's messages and operator identifiers are removed from other users' retained support tickets; the decision and timestamp may remain without the deleted operator identifier. Community conversations disappear for both participants. Active business responsibilities and future bookings must be resolved first; separate booking and business records follow a separate retention process. Community account deletion does not erase personal local or iCloud Evently data.

Opening social search processes the search term on the server. Search terms and account-bound pagination state are usable for at most one hour, then removed by scheduled cleanup. Saved items, likes, comments and story-view state are stored for app functionality, separately from the optional usage analytics described in its own notice, without advertising tracking for these features.

Thoughts, city, work, education, relationship, family, language, interests, places, links and contact details voluntarily entered and saved in the profile thought bubble or About are stored in Firebase under the private account's separate profile details. Each detail is visible only to its owner by default; the owner can explicitly choose friends or Evently users as its audience. Phone and contact email have individually chosen audiences and do not change the sign-in email. A thought stays until changed or removed; it is not automatically shared as a post. Highlighted details follow the same audience checks. Every read rechecks account status, current friendship and blocks on the server. No details are automatically imported from local contacts or screenshots of other services. Individual values can be removed in the editor and are also erased with the Firebase account.

Messages store server timestamps for sending, delivery and reading, plus an edit revision. Delivery and reading require the other participant's acknowledgement. Withdrawing your message revokes its text and attachment, leaving a deletion marker; repeatable background work permanently removes its attachment. Archived posts are accessible only to their author. Trashed posts can be restored for 30 days; after expiry a scheduled server task removes content, attachments, reactions and comments. Group owners can appoint or revoke administrators; the server authorizes every membership and moderation operation. Account deletion also removes message-attachment cleanup and ownership records. These additions require deployment of the corresponding server version.

The app feed reads followed businesses' public posts from their original business records. Account-bound paging state is usable for one hour and later removed by scheduled cleanup. Booking submission and status changes create in-app notifications for the customer and business, storing booking/business identifiers, service label, status, revision, actor and timestamp. Read state is stored separately per account. This does not itself deliver phone push notifications. Evently's calendar displays the shared booking record and does not automatically copy it to Apple Calendar. Explicitly attached business chat images are available to the customer and authorized active provider. Community account erasure also removes the account's own notifications, read markers and paging state; business booking and provider notification records follow separate retention procedures. An authorized provider may add a private CRM guest to a group class: customer and session identifiers, seats, frozen booking terms, answers, note and audit timestamps are stored in the protected business records. This shares capacity with online bookings; matching email addresses do not themselves link a CRM guest to an app account.

Photo albums store their name, owner account identifier, audience, ordered references to already-shared own photo posts, revision and timestamps in Firebase. Adding a photo does not upload it again or expand its original post access. Deleting an album preserves the original posts and photos; account deletion also removes owned albums. Server-only account-linked pagination records can be used for one hour and are removed by scheduled cleanup. Local Evently/iCloud photos and contacts are not automatically added to albums.

Custom audience lists store their name, selected Evently friends' account identifiers, revision and modification time under the private Firebase account. Only the owner may manage them. Applying a list and sending a post recheck active accounts, friendship and blocks. Later list edits do not change earlier posts' recipients. List deletion removes names and member identifiers; a revision marker remains until account deletion to prevent stale saves. Account deletion removes owned lists and the erased identifier from other users' lists. Local address books are not imported.

People displays accepted Evently friends subject to current profile permissions. Shared profile details of other users are revalidated online before display and are hidden offline. Your own phonebook data remains available. A phonebook entry may be manually linked to a friend: only identifiers are stored locally on that device, scoped to the account; phonebook data is not uploaded. Online status has separate consent, off by default, requiring both friends' consent. Private session signals expire within 45 seconds. Optional Social calendar preferences are stored in the private Firebase account. Only friends' currently shared occasions appear; they are not copied to the local or iCloud calendar. Separately enabled reminders are scheduled on the device for the next 24 hours using generic notifications without names. Withdrawn sharing is removed when the app refreshes; offline removal may be delayed until that refresh. Social reminders are removed at sign-out. Account erasure removes calendar preferences and presence signals.

The app keeps account-scoped local cache copies of authorized social responses, messages, profiles, posts and images to reduce repeated data transfer. Copies can survive app restarts, use iOS file protection, and are excluded from Evently iCloud backups, widgets and Watch data. The cache is limited to 256 MB with a 12 MB response limit; older copies are evicted when the storage limit is reached. Saved data remains readable offline for the same signed-in account; startup and reconnection refresh previously loaded pages in the background. Signing out, changing accounts or acceptance of account deletion clears this cache. A saved copy does not grant continuing access: the server validates updates and permissions, and changes and deletions take effect at the next successful synchronization. This adds no tracking or marketing collection.

A place voluntarily selected for a regular post is stored in Firebase with its name and map coordinates and is visible to the post's selected audience. Apple Maps processes the entered place search query. This feature does not automatically read device location or photo GPS metadata. The place can be removed before publishing; published place data follows the post's visibility, account deletion and content deletion rules.

Evently Social is available only to users who have reached the age of 16. Users must provide accurate registration information, keep account access secure, and may not impersonate another person.

Users retain ownership of their posts and images and grant the operator only the limited rights needed to store, process, secure, and deliver that content to the recipients selected by the user.

Illegal, deceptive, threatening, harassing, privacy-invasive, infringing, malicious, or abusive content and attempts to bypass blocks, access controls, age checks, or security rules are prohibited.

Users can remove friends, block users, delete their own posts from active surfaces, and request account deletion. The operator may restrict or suspend accounts and preserve necessary evidence when required for security, moderation, legal claims, or legal compliance.

Supplement dated 11 October 2026. Tripelfy social and account-based services must not be used by anyone under 16. Users aged 16–17 are minors; where applicable law requires a legal representative's involvement for a booking or another contract, this must be arranged before entering into that contract. The minimum age is not blanket consent to personal data processing. Access to the privacy notice, acceptance of service terms and optional analytics consent are separate matters. Firebase accounts, social content and chat, business bookings, and local/iCloud records involve distinct processing. The service processes chat messages and attachments on servers; we do not promise end-to-end encryption. Business bookings and related messages are also disclosed to the selected provider, whose privacy notice and booking terms must also be reviewed. Social account deletion does not replace the separate handling of business records or local/iCloud data. If in-app deletion is blocked, access, correction, erasure or restriction may still be requested at hello@tripelfy.com; records requiring retention under applicable law must be assessed individually. We normally respond to data subject requests within one month and communicate any justified GDPR extension within that period.

The app keeps account-scoped local cache copies of authorized social responses, messages, profiles, posts and images to reduce repeated data transfer. Copies can survive app restarts, use iOS file protection, and are excluded from Evently iCloud backups, widgets and Watch data. The cache is limited to 256 MB with a 12 MB response limit; older copies are evicted when the storage limit is reached. Saved data remains readable offline for the same signed-in account; startup and reconnection refresh previously loaded pages in the background. Signing out, changing accounts or acceptance of account deletion clears this cache. A saved copy does not grant continuing access: the server validates updates and permissions, and changes and deletions take effect at the next successful synchronization. This adds no tracking or marketing collection.

A place voluntarily selected for a regular post is stored in Firebase with its name and map coordinates and is visible to the post's selected audience. Apple Maps processes the entered place search query. This feature does not automatically read device location or photo GPS metadata. The place can be removed before publishing; published place data follows the post's visibility, account deletion and content deletion rules.

Analytics · English

With your permission, Google Firebase Analytics summarizes the screens and features you use and the time you spend with the app in the foreground.

Measurement may also process an app-instance identifier, device and app information, and approximate location derived from your IP address.

We do not send Analytics your name, email, account ID, messages, calendar content or booking details. We do not collect advertising identifiers.

Consent is optional and applies to this app installation. All app features remain available if you decline.

Turn it off anytime in Settings. This stops measurement and resets the local analytics identifier; it does not delete data already sent.

Country, holiday and name-day data updates

At launch, when returning to the foreground and periodically during active use, Evently checks the operator's published shared country, holiday and name-day database over HTTPS. Every device receives the same public reference package.

The request sends no contacts, personal events, profile, selected countries, sign-in token or cookies. Google Firebase/Cloud Functions may process and log technical network information, such as IP address and request time, to serve and protect the service.

If a download fails or is invalid, the last verified local package remains in use, or the bundled database if no downloaded package exists. Updates do not change personal events, contacts or the storage of personal iCloud data.

Recovering an unfinished booking

During a new individual or group booking, the app keeps the account, business, service and booking identifiers the revision before a reschedule and save time on this device. This record contains no password, sign-in token, note or questionnaire answer. When the same account returns to the same service, the app checks the current server state. The record is removed after successful confirmation or release of the hold; after seven days it cannot be used and is removed on the next read. It is excluded from Evently's own backup, iCloud sync, widget and watch data. Operating-system settings govern device backups.