MyEvents360

Privacy policy

Last updated: October 14, 2026

This policy describes how MyEvents360 collects, uses and protects its users' personal data, in accordance with the General Data Protection Regulation (GDPR) and the French Data Protection Act (loi Informatique et Libertés).

1. Data controller

Inferevo, a French simplified joint-stock company with a sole shareholder (SAS(U)), share capital €1,000, 173 rue de Courcelles, 75017 Paris, France, RCS Paris 130 803 158, publisher of MyEvents360, represented by its President, Bertrand Boucher.
Contact: contact@myevents360.com

The data controller determines the purposes and means of the processing described below. No data protection officer has been appointed, as this is not mandatory for this service; any question about your data can be sent to the address above.

2. Data we collect

Account and profile

  • Email address (used for authentication and service messages)
  • Password, stored only in hashed form
  • First and last name, profile name (public handle)
  • Profile picture, cover image, bio and links to your social networks (optional)
  • Phone number (optional) — which can be verified with a code sent by SMS; secondary email addresses and phone numbers you add to your account (optional)
  • Language, favorite city and search radius (optional)
  • Notification, privacy and display preferences

Age and protection of minors

  • Date of birth, requested at sign-up (or later for older accounts), and the resulting age group (under 18 or adult). They are not visible to other users.
  • Your device's time zone, sent for every account and used to time the night-time muting of notifications for accounts under 18.
  • Installation identifier: a random identifier specific to the installed app, sent at sign-up. If a sign-up is refused because the age entered is under 15, this identifier is flagged for 24 hours so that a new attempt with another date is refused; the date entered is not kept.
  • Age signal provided by the app store: on iOS 26 and later (with your consent in Apple's prompt) and on Android (Google Play, in countries where the service exists), the app may ask the store for an age range (for example "under 18") and how it was established (self-declared, confirmed, supervised by a parent), at most once a day. We keep only the latest answer, until your account is deleted. If it shows you are under 18 although you declared being an adult, your account switches to the protections for minors, and you can contest this with proof. Legal basis: legal obligation and legitimate interest in protecting minors.
  • Parental supervision (optional): the link between the teen's account and the account of the adult(s) supervising them, its status and dates, requests to relax protections and the answers given (see §9).
  • Age contest: if our team changes your account's age group, the related file (reason, dates, decision) and, if you contest it, the photo of the identity document you send (identity card, passport or residence permit) and its type (see §5 and §9).

Events, groups and participation

  • Title, description, dates, location, category and cover image
  • Members, roles, invitation responses, votes and poll answers
  • Contributions to event modules: lists, "who brings what", carpooling, guestbook, schedule, QR-code check-in (passes and check-ins)
  • Invitations to people who are not registered: they are sent from your device (SMS, WhatsApp or email, with the app of your choice); we neither receive nor keep their contact details
  • Guests without an account: when someone replies to an invitation from an event's public web page without creating an account, we record their first name, last name, email or phone, reply, number of companions (adults and children), optional message and a technical identifier specific to their browser. If the organizer allows it, they can also, without an account, add photos and videos to the gallery (for instance from a QR code) and sign the guestbook, under the name they give; these contributions last as long as the event
  • Event activity log: members' actions (adding a media item, a schedule step, an expense, replies…) are recorded in the event's history; the author is removed from it if their account is deleted
  • Shared expenses: amounts, currencies, participants, split and photos of receipts

Messages and media

  • Messages exchanged in event chats, group chats and direct messages, with their attachments, reactions, pins and read receipts
  • Photos, videos, documents, comments and "Souvenir" montages you share
  • Audio recordings: voice messages and Souvenir montage voice-overs

Online presence

The app records the time of your last activity to show whether you are online and when you were last seen. From Settings › Privacy, you choose who can see this information (everyone, your contacts or nobody); if you hide it, you cannot see other people's either.

Location

  • One-off location: when you choose to use your location (for example to set an event's venue or share a place in a chat).
  • Live location: the event organizer turns this feature on, decides who may share their position (all participants or organizers only) and who sees shared positions: all participants, only your contacts among them (organizers are included only if they are your contacts), or organizers only. You decide whether to share: before you start, the app shows you by name who will see you. You choose the duration (1 h, 4 h or until the event ends) and the accuracy (exact, or approximate: an area of about 150 m), and you can stop at any time. If the organizer later widens the audience, your sharing is paused until you confirm again. Sent: coordinates, accuracy, timestamp and device battery level. If you allow it in your device settings, sharing can continue while the app is in the background. A minor's position is never visible to all participants and is approximate by default. When you reach the event venue, your arrival is recorded and, unless you turn this option off, the people who see your position are notified. Your trail stays visible to the same people after you stop sharing, until it is deleted: you can erase it yourself at any time; otherwise positions and arrivals are deleted automatically no later than 24 hours after the event ends (or after your sharing ends, if later; see §5).
  • Meeting points: members can pin a named place (coordinates and label) on the event map; it stays visible as long as the event exists, without your name if you delete your account.

Address book

If you grant access to your contacts, the email addresses and phone numbers in your address book are sent to our servers to identify which of your contacts already have a MyEvents360 account. These details are used only for this matching at the time of the request and are not stored in our database. You can revoke this permission in your device settings.

Purchases and subscriptions

If you subscribe to a paid plan (Plus, Max or Pro), the purchase is made and paid through Apple's App Store or Google Play. Through RevenueCat, we receive your plan, its dates and its status. We do not receive your payment card details, which remain with Apple or Google.

Feedback and support

When you send feedback ("Bugs and suggestions") or contact support: your message, any screenshots you attach and technical information (app version, platform, operating system, device model, language). The app does not send your feedback to any third party: it is stored on our servers. To handle it, the team uses its internal tools, a development assistant (Claude Code, by Anthropic) and its task tracking tool (Linear); it does not copy your name into them, only the feedback text, its topic, the technical information above, a reference number and links to the screenshots (see §4, block E). Whatever you write in the feedback or show in a screenshot is therefore included as is.

Reports

When you report content or a profile from the app: the item concerned, the reason you choose, your optional comment and the date. If a report related to the protection of minors leads to content being hidden, a copy of that content and of the reports about it is kept as evidence (see §5).

People reporting content without an account

The illegal content report form, which can be used without an account, collects: your name and email address (optional for a report of child sexual abuse), the explanation you provide, the reference and category of the content concerned, your good-faith statement and the language of the form. This data is used to review the notice and to inform you of the decision taken.

Sanctions and legal obligations

When the team sanctions a breach of the terms of use, or enforces a court decision: the formal warning or the time-limited suspension of the account (reason, dates, reference of the decision where applicable). A suspension may come with a block on signing up again: we then keep an encrypted, non-reversible fingerprint of the account's verified email address and phone number, never these identifiers in clear. When the team permanently deletes an account for a serious breach (termination), we likewise keep the fingerprints of its verified email addresses and phone numbers, to refuse a new sign-up, and its profile name, so that no one takes it over: neither is linked to the erased account any more. When the law requires it (serious illegal content, a threat to a person's life or safety), we report the content to the competent authorities with the references of the content and of its author, and we carry out the orders they send us. Finally, each time the team views a private message or a non-public conversation, which is allowed only for a reason that concerns that message, the access is logged (date, reason, message concerned, never its text).

Account security and signed-in devices

For each device signed in to your account, we record: the device type and its operating system, the app or browser used, the date of first sign-in, the last activity, and an approximate location (city and country) derived by Cloudflare from the network address of the last sign-in. The network address itself is not kept with the device. A randomly generated installation identifier, stored as a fingerprint, lets us recognise a device you have already used and alert you by email when you sign in from a new device. You see these devices in Profile › Settings › Identification and security › Security and can sign them out.

If you turn on two-factor authentication (optional), we record the method you chose (code by email or authenticator app) and when you turned it on. The authenticator app key is stored encrypted; backup codes and trusted-device tokens are stored only as fingerprints, never in clear text. Codes sent by email and attempt counters are kept only for a few minutes to an hour. Your two-factor authentication status and your list of devices are included in your data export.

Technical data

  • Device notification token (for push notifications)
  • App version and platform in use
  • Error and crash reports, configured not to send identifying information (IP address, cookies) by default
  • IP address and connection information in technical logs (security)
  • Advertising identifier (IDFA on iOS / Google Advertising ID on Android) — used only when ads are shown and according to your consent (see §4 ter).

We remove from the photos and videos you share the hidden information your device writes into them (GPS location, exact date and time of capture, device model). Depending on the case, this cleaning happens on your phone before upload (photos in chats and private messages, JPEG photos in the gallery) or on our servers right after (gallery, chats, private messages, guestbook videos, profile, cover and group photos, schedule images, expense receipts); in the latter case, the original file may remain accessible to other participants for a few minutes, and for up to four hours if refreshing the content delivery network temporarily fails. Not cleaned: voice messages, documents, screenshots attached to a bug report, a profile, cover or group photo over 8 MB or 20 megapixels, and a gallery photo over 50 megapixels, kept as is.

3. Purposes and legal bases

  • Providing the service (authentication, event management, messaging, media sharing) — legal basis: performance of the contract.
  • Sending push notifications about events — legitimate interest + system-level consent.
  • Content moderation (automatic detection of inappropriate content) — legitimate interest to ensure a safe environment.
  • Sending transactional emails (verification, password reset) — performance of the contract.
  • Measuring and improving use of the service — activity statistics linked to your account (days of use, features used, notifications opened), viewed only by the MyEvents360 team to steer the product, never sold or shared; kept for the life of the account and deleted with it — legitimate interest.
  • Displaying advertising in the mobile app (via Google AdMob) — legal basis: consent for personalized advertising and tracking, legitimate interest for non-personalized advertising (see §4 ter).
  • Sharing your live location and finding your contacts from your address book — legal basis: consent, given by turning the feature on and granting the device permission, which you can withdraw at any time.
  • Managing subscriptions and in-app purchases — performance of the contract.
  • Handling your feedback and support requests — legitimate interest in improving the service and answering you.
  • Handling notices of illegal content submitted without an account through the report form — legal basis: legal obligation (EU Digital Services Act, article 16).
  • Sanctioning breaches and answering the authorities (warnings, suspensions, blocking a new sign-up, reports to the authorities, orders, log of views of private messages) — legal basis: performance of the contract for the sanctions set out in the terms of use; legal obligation for court decisions, reports and orders, and for proving that each view was lawful; legitimate interest in preventing a suspension or a termination from being bypassed for the sign-up block and the frozen profile name.
  • Checking the minimum age and protecting users under 18 (date of birth, age group, default protections, night-time muting, temporary refusal after a refused sign-up, review of age reports and contests) — legal basis: legal obligations to protect minors online and legitimate interest in keeping users safe.
  • Parental supervision, when the teen and the adult turn it on — legal basis: performance of the contract (a feature requested and accepted by both accounts), which either of them can end at any time.
  • Securing your account (two-factor authentication, listing and signing out signed-in devices, alerts when you sign in from a new device, approximate location of sign-ins, limits on attempts) — legal basis: performance of the contract for the two-factor authentication you turn on, legitimate interest in protecting accounts against fraudulent access for the rest.

4. Recipients and sub-processors

Your data is visible to other users according to what you share and the settings of each event or group. It is also entrusted to the providers below. Unless stated otherwise (block D), they are sub-processors: they process it on our behalf, on our instructions and only as needed to run the service. For each one we state its role, the data it receives, where that data is processed and the safeguard covering any transfer outside the European Union. A summary by type of data is available on the "Where your data lives" page.

A. Service hosting: data stored in the European Union

The core of the service (database, servers, files, cache, backups and error reports) is stored in the European Union. Several of these providers are companies established outside the Union, mostly in the United States: even when the data stays stored in Europe, their staff may access it remotely (support, maintenance), which counts as a transfer. This access is covered by the European Commission's standard contractual clauses and, for certified US companies, by the EU–US Data Privacy Framework.

  • Supabase Pte. Ltd. (Singapore) — database: account, profile, events, messages, media references and, more generally, the data described in §2 — stored in the European Union (Frankfurt, Germany); only our servers access it. Safeguard: standard contractual clauses.
  • Railway Corporation (United States) — hosting of the API and background jobs; application logs, which include IP addresses; the service's working memory (Redis), for short-lived data: one-time codes, abuse rate-limiting counters (which include IP addresses), real-time message relay (a message's content passes through while it is being delivered and is not stored there), the background job queue (including the content of notifications and emails waiting to be sent) and caches — servers in the European Union (Amsterdam, Netherlands). Safeguard: standard contractual clauses / Data Privacy Framework.
  • Cloudflare, Inc. (United States) — R2 storage of photos, videos, documents and voice messages and, in a separate private storage area, of the documents sent to contest an age decision — storage placed, since October 8, 2026, in Cloudflare's EU jurisdiction (storage guaranteed in the European Union): Cloudflare commits to storing and processing these files within the European Union. Cloudflare remains a US company: remote access by its staff remains possible and counts as a transfer. Photos, videos and other shared files are delivered through Cloudflare's global network, which may keep temporary cached copies outside the European Union (see block B); age-contest documents are not delivered through that network. Safeguard: standard contractual clauses / Data Privacy Framework.
  • Backblaze, Inc. (United States) — disaster-recovery backup storage, when backups are in service (see §5) — servers in the European Union (Amsterdam). Backups are encrypted before upload: Backblaze cannot read their content. Safeguard: standard contractual clauses.
  • Functional Software, Inc. (Sentry) (United States) — error and crash reports, configured to send neither IP addresses nor account identifiers — data hosted in the European Union (Germany). Safeguard: standard contractual clauses / Data Privacy Framework.

B. Delivery of emails, text messages, notifications and subscriptions

These providers carry what the service sends you, or manage your subscriptions. They are established in the United States and often run global networks: the data concerned may therefore be processed outside the European Union. Safeguard: standard contractual clauses / Data Privacy Framework.

  • Resend — service emails and beta invitations: recipient address, subject and content of the email (including one-time codes and links to download your data) — United States.
  • Twilio Inc. — text messages: your phone number to send a verification code; your number and the message text for inactivity notices — United States and delivery relays worldwide.
  • 650 Industries, Inc. (Expo) — push notification relay: your device's notification token and the content of the notification, which it hands over to Apple or Google (see block D); app updates (IP address, app version, platform); app performance measurements (startup and rendering times) — United States. Expo states that it does not keep notification content after delivery.
  • Cloudflare, Inc. — file delivery network (photos and videos you view may be cached temporarily in the nearest data center, wherever it is), hosting of the web app and website, DNS, routing of emails addressed to MyEvents360, bot protection on the contact and reporting forms, routing of the traffic between the app and our servers (including deriving the approximate city and country of a sign-in from the network address) — global network.
  • RevenueCat, Inc. — subscription and entitlement management: receives only a random internal identifier, never your email or name, and the status of your purchases as reported by Apple or Google — United States.

Content of push notifications. A notification contains the text shown on your screen, for example an event title. For a chat message or a private message, it contains by default the sender's name and the first 100 characters of the message; this text passes through Expo, then Apple or Google. If you turn off "Message previews" (Profile › Settings › Notifications), a message notification no longer contains the sender's name or the content: it only says that a new message has arrived. For 15 to 17-year-olds, "Message previews" is off by default and can only be turned on with the agreement of an adult who supervises the teen (see §9).

C. Artificial intelligence, moderation, maps and images

These providers only receive data when the matching feature is used. AI features ask for your consent before the first submission (see §4 quater). Automated moderation is the exception: it does not depend on your consent and applies to content in spaces where it is enabled, and to identity elements (see §4 bis).

  • OpenAI, L.L.C. — automated moderation (text of the content analyzed and image addresses); cover-image generation (the description you type); audio transcription of voice-overs for Souvenir montage subtitles. No account identifier is sent — United States (see §4 bis and §4 quater). Safeguard: standard contractual clauses / Data Privacy Framework.
  • Anthropic, PBC — AI assistant, AI-assisted event creation, rewriting of cover-image descriptions and text translation via the Claude API, with your consent — United States (see §4 quater). Safeguard: standard contractual clauses / Data Privacy Framework.
  • Mapbox, Inc. — maps, address search and conversion of coordinates into an address. Your device queries it directly: Mapbox receives the text of searched addresses, coordinates to convert where applicable, the map area displayed and, as with any site visited, your device's IP address. Mapbox usage statistics are turned off in the mobile app — United States. Safeguard: standard contractual clauses / Data Privacy Framework.
  • Pexels GmbH (cover-image library) — Germany. To search for an image, our servers send it only the search term. Previews are then loaded directly by your device from Pexels, which therefore receives your IP address and your device's user-agent (a short technical label every phone or browser sends automatically to the sites it visits: type of device, operating system and app used). The chosen image is copied to our servers and then served by us.

D. Independent controllers

The following companies are not our sub-processors: they process the data their service needs for their own purposes, under their own privacy policies.

  • Apple (App Store, APNs notification service) and Google (Google Play, FCM notification service) — distribute the app, sell subscriptions and collect their payment, and deliver push notifications to your device (token and content of the notification).
  • Google Ireland Limited (AdMob) — advertising in the mobile app, when it is shown — see §4 ter.

E. The team's internal tools

These tools are used only to handle the feedback ("Bugs and suggestions") and support requests you send us. The app sends them nothing automatically: the team copies a piece of feedback into them to handle it, without your name (see §2, "Feedback and support").

  • Linear Orbit, Inc. — the team's task tracking tool — United States. Safeguard: standard contractual clauses / Data Privacy Framework.
  • Anthropic, PBC (Claude Code) — a development assistant that helps the team analyze feedback — United States. Safeguard: standard contractual clauses / Data Privacy Framework.

F. Public authorities

When the law requires it or on their order, we send the competent authorities (the Pharos reporting platform, the public prosecutor, administrative or judicial authorities of a European Union member state) what they need: the reference and a copy of the content concerned, and the identifiers of its author. These authorities are not our processors.

Transfer safeguards

Where data is transferred outside the European Union, or can be accessed from a third country by a provider established outside the Union, these transfers are covered by the European Commission's standard contractual clauses and, for certified US providers, by the adequacy decision on the EU–US Data Privacy Framework. You can obtain a copy of these safeguards by writing to us.

Exchange rates used for shared expenses are fetched by our servers directly from the European Central Bank, without sending any personal data.

We do not sell or rent your personal data to third parties.

4 bis. Automated content moderation

To keep our community safe and detect prohibited content (hate, harassment, threats, violence, self-harm, sexual content, child exploitation, illicit activities), we use a local word filter, run on our servers, and the OpenAI Moderation API automated moderation service.

Where it applies: automated moderation is set per space.

  • Events: on by default. The event's creator and administrators can turn it off or choose its level (Strict, Standard or Lenient). It covers the event chat, photos posted in the event, comments and the guestbook.
  • Groups: on by default. The group's administrators can turn it off or choose its level. It covers messages and images in the group chat.
  • Private messages: not moderated by default. Each user can turn on "Moderate my private messages" (Profile › Settings › Privacy) and choose its level. It only takes one of the two participants to have it on for the conversation to be moderated, both ways; the strictest level chosen by the participants who turned it on applies.
  • Identity elements (an event's title, description, cover photo and invitation message; a group's name, description and photo; profile name, profile photo and cover photo): always analysed, at the Standard level. This check cannot be turned off.

When a space has turned moderation off, its content goes through neither the local filter nor OpenAI. Videos, voice messages and documents are not analysed automatically.

Members of an event or group whose chat is moderated are told so by a notice when they open the chat, which shows the level. The space's administrators see hidden messages and images and can restore them if they were hidden by mistake, or delete them, with exceptions (serious content, child protection, requests from an authority).

Data sent to OpenAI (only for content in a space where moderation is on, and for identity elements):

  • The text concerned (message, comment, guestbook entry, identity element), when it is posted or edited.
  • The address (URL) of the images concerned: OpenAI downloads the image from our storage and analyses it visually, when it is sent or shortly after, in the background.

Consequences: a comment, guestbook text or textual identity element that is flagged is refused when sent, and its author is asked to rephrase it. A flagged chat message or image is hidden from other users; a flagged profile, cover or group photo is removed. In these cases, unless a competent authority forbids it, the author is informed through a statement of reasons, which states that an automated tool was used: for an image, by notification and email; for a text, by an in-app notification, with a limited number of emails. They can contest the decision free of charge within 6 months by writing to contact@myevents360.com; the appeal is reviewed by a member of our team, not by an automated system (see the Terms of Service, §5). Automated decisions have no legal effect on the user.

OpenAI API policy: under OpenAI's commercial terms, data sent through its API is not used to train its models. Its moderation service does not keep the analysed content in its abuse-monitoring logs, unless required by law.

Legal basis (GDPR): legitimate interest in protecting users and the community from unlawful content (Article 6.1.f).

Sub-processor: OpenAI, L.L.C., 3180 18th Street, San Francisco CA 94110, USA. Transfers outside the European Union are framed by the EU Commission's Standard Contractual Clauses and the EU-US Data Privacy Framework.

4 ter. Advertising (Google AdMob)

The MyEvents360 mobile app may display ads served by Google AdMob (Google Ireland Limited), as sponsored cards inserted in the Explore feed. Plans that include ad removal show none, and the web version shows none. When ads are shown, the Google Mobile Ads SDK may access your advertising identifier (IDFA on iOS, Google Advertising ID on Android) to display ads and measure their performance.

Consent: where regulations require it (notably in the European Economic Area and the United Kingdom), a consent screen (Google UMP) collects your choice; on iOS, an App Tracking Transparency prompt is also shown. If you decline, the ads displayed are non-personalized and your advertising identifier is not used for cross-app advertising tracking. Accounts under 18, and accounts whose date of birth has not been provided yet, only receive non-personalized ads, whatever that choice.

Data involved: advertising identifier, ad-interaction data, and approximate technical information (device type, language). This data is processed by Google under its own policy — see Google's privacy policy and how Google uses data.

Legal basis (GDPR): consent (Article 6.1.a) for personalized advertising and tracking; legitimate interest (Article 6.1.f) for displaying non-personalized advertising. You can withdraw your consent at any time by resetting the advertising identifier in your device settings, or by declining via the consent screen / iOS tracking prompt.

Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, which processes this data as an independent controller, under its own rules (see §4, block D). Transfers outside the European Union are framed by the EU Commission's Standard Contractual Clauses and the EU-US Data Privacy Framework.

4 quater. Artificial-intelligence features (assistant and generation)

The app offers generative-AI features that you trigger yourself: the conversational AI assistant, AI-assisted event creation (you describe the event and the AI prepares a draft), cover-image generation from a text prompt, and Souvenir Studio subtitles (transcription and translation). These features rely on third-party AI providers and are only active when you use them; each one asks for your explicit, screen-by-screen consent before the first request is sent (see "Legal basis" below).

Data sent:

  • Assistant and event creation — we send Anthropic (Claude API) your messages and the current conversation (up to 20 messages), your language, your device's time zone and time, the event draft being created, and, depending on your question, information you can already see in the app:
    • your events: title, type, dates, place or address, description, number of members, your role and your response, practical information (dress code, parking, access, gifts, what to bring, door code if one is set, notes) and, for organizers, the response counts;
    • event chat messages with their author's first name (recent messages or search excerpts);
    • the member list (first name, role, invitation response) and, if the matching screen shows them, their questionnaire answers;
    • module content: schedule, questionnaire, who brings what, polls, checklist, carpool (route, time, driver's first name), written guestbook entries with their author, attendance and stay periods;
    • an activity summary: unread counts per event and, for your private messages and groups, only the sender's first name, the group name and the number of unread messages — never their content — as well as the titles of unread announcements;
    • your plan, its end date, your limits, storage used and AI credits, and your favorite city if you look for public events near you.
    Never sent: your email, phone number, date of birth and account identifier, the text of your private and group messages, your photos, videos and voice messages, your GPS positions, and no last name. Your first name is not sent to identify you; it only appears where the app already shows it to other members: in the member list of an event you are viewing, or as the author of an event chat message, a guestbook entry or a carpool ride. A name may still appear in text written by a member (message, description, title): it is sent as is.
  • Cover-image generation — the text (prompt) you provide is sent to OpenAI (Images API, gpt-image models) to produce the proposed images; when you ask to improve this description, it is first sent to Anthropic to be rewritten, together with the event’s title, type, city and date.
  • Automatic subtitles for Souvenir montages — the audio recording of your voice-over is sent to OpenAI (Whisper transcription model) to produce the subtitles.
  • Translation of Souvenir montage texts — the texts to translate (subtitles and title cards) are sent to Anthropic (Claude API).

For each use, we keep a technical log (feature, model, amount consumed, cost) without the content sent; it is kept for 13 months at most, and deleted with your account if that happens sooner.

Purpose: to perform the feature you requested (answer a question, draft an event, generate or enhance a cover image, transcribe or translate Studio subtitles).

Model training: under these providers' commercial terms, data sent through their APIs is not used to train their models. Anthropic (assistant) deletes it within 30 days, except content flagged as violating its usage policies, which is kept for up to 2 years. OpenAI does not keep transcribed audio; for image generation, it keeps requests for up to 30 days for abuse monitoring. Longer periods may apply where required by law.

Reliability: AI-generated content may contain errors, inaccuracies or outdated information. It is provided as assistance; it is your responsibility to check and correct it before using or publishing it. You remain responsible for the content you share.

Legal basis (GDPR): your consent (article 6.1.a), collected before the first use of each feature and withdrawable at any time in Profile › Settings › Privacy; withdrawing it does not affect processing already carried out. Security and abuse prevention remain covered by legitimate interest (article 6.1.f).

Sub-processors: Anthropic, PBC, San Francisco, United States — see Anthropic's privacy policy; OpenAI, L.L.C., 3180 18th Street, San Francisco CA 94110, United States. Transfers outside the European Union are covered by the European Commission's Standard Contractual Clauses and the EU-US Data Privacy Framework.

5. Retention period

  • User account: until you delete it, from Settings. Deletion is normally immediate; in case of a technical incident, the account is first deactivated and its deletion is then completed automatically as soon as possible. An account left 2 years without signing in may also be deleted: you are then notified by email 30 days and then 7 days before deletion (by text message, to the account's verified phone number, if the account has no email address), and simply signing in keeps the account. An account with an active paid plan, or that we can reach neither by email nor by text message, is not deleted automatically.
  • Events and content: as long as the event exists, until deleted by the creator or the user concerned, or with the account.
  • Account security: a signed-in device (with its approximate city and country) is removed when you sign it out or after 30 days without activity; a trusted device, at the latest 30 days after a code was last entered; the list of already recognised devices, one year after their last sign-in; the two-factor authentication method, its key and the backup codes, until you turn two-factor authentication off. Everything is deleted with the account.
  • Live location: positions, trails and arrivals deleted automatically no later than 24 hours after the event ends, or after your sharing ends if later; you can erase your trail earlier. Meeting points: as long as the event exists.
  • Address book: not stored (used only for the time of the matching).
  • Invitations sent to registered users: they expire after 30 days by default and are deleted within two weeks of expiring.
  • Replies from guests without an account: as long as the event exists; they are deleted with it, including if the person who invited them has deleted their account in the meantime.
  • Subscriptions: plan, dates and status for the life of the account. Purchases are made and invoiced by the App Store or Google Play, which keep the invoices and accounting records; we do not keep any.
  • AI usage log (without content): 13 months at most; it is deleted with the account if that happens sooner.
  • Feedback and support requests (bugs and suggestions): 12 months after they have been handled, and at most 2 years after they were sent if they are never handled; if the account is deleted, they are no longer linked to your name (screenshots remain filed under a technical identifier).
  • Handled reports: 12 months after the decision. If you delete your account, the reports you filed are kept, detached from your account (they are no longer linked to your identity), for handling reports and appeals. Likewise, a report is kept if the reported content or account is deleted (by its author, by moderation, or together with the event or account it belongs to): only technical references are kept (identifiers of the content, of its author and of its event or group, date of deletion), never the content itself. A report still pending at that point is deleted 12 months after the content was deleted if it has not been handled in the meantime.
  • Notices of illegal content submitted without an account (name, email, explanation, content concerned): 6 months after the decision, and at most 2 years after they were filed if no decision has been taken.
  • Moderation log (moderation decisions and actions): 3 years.
  • Log of automated moderation decisions (reference of the content concerned, category, decision and follow-up): 400 days.
  • In-app notifications: 90 days after creation once read, as soon as they expire where applicable, and at most 1 year if never read.
  • Evidence kept after a report related to the protection of minors (copy of the hidden content and of the reports about it): 1 year from the time the content was hidden, extended if legal proceedings are under way. It is kept even if the content or its author's account is deleted, and deleted if the report turns out to be unfounded.
  • Sanctions and legal obligations, kept even after the account is deleted, to meet our legal obligations and to be able to defend ourselves in court: warnings, 7 years after the warning; suspensions, 5 years after they end; fingerprints used to block a new sign-up, erased at most 5 years after the suspension, even if it is still running (they only block a new sign-up while the suspension lasts); fingerprints and profile name of a terminated account, 2 years after the termination; reports to the authorities, 6 years after they are sent, extended while court proceedings are ongoing; log of views of private messages by the team, 5 years after each view; orders from the authorities and non-disclosure orders, 6 years after they are closed or end, an order being kept for as long as it keeps a piece of content removed.
  • Data export archive: link valid for 72 hours, archive deleted afterwards.
  • Date of birth, age group and time zone: for the life of the account.
  • Sign-up refused for age: only the installation identifier is flagged, for 24 hours; the date entered is not kept.
  • Parental supervision (links and requests to relax protections, including ended ones): until the account of the teen or of the adult concerned is deleted.
  • Age reclassification and contest files: for the life of the account.
  • Photo of an identity document sent to contest an age decision: kept in a private storage area, separate from the service's photo storage and excluded from backups; only a platform administrator can view it, and every view is logged. It is deleted as soon as a decision is made and, in any event, 7 days after it was sent (to within an hour, as the purge runs hourly), including if it could not be reviewed in time.
  • Technical logs and error reports: 90 days at most.
  • Email delivery logs: at the email provider, 12 months at most.
  • Disaster-recovery backups: when disaster-recovery backups are in service, they are encrypted copies of the database and files, kept for 7 days and technically protected against deletion for at most 14 days. Deleted data then leaves the backups no later than 14 days after its deletion. Should the service ever be restored from a backup, accounts deleted in the meantime would be deleted again before the service is brought back online.

6. Your rights

Under the GDPR, you have the following rights over your data:

  • Right of access: obtain a copy of your personal data.
  • Right of rectification: correct inaccurate data — directly from your profile and settings, except your date of birth, which can no longer be changed in the app once declared: to correct it, write to us.
  • Right of erasure: delete your account and data (Profile › Settings › Delete my account) or ask us to do so.
  • Right of portability: download your data in a structured, machine-readable format, from the app: Profile › Settings › Privacy › "Download my personal data". An archive (data in JSON format and the original media you provided, except photos of expense receipts, which appear by their address) is prepared, then a download link valid for 72 hours is sent to you by email. A new request is possible after a waiting period of a few days, shown in the app. This feature requires an email address on your account; otherwise, write to us.
  • Right to restriction of processing, in the cases provided for by the GDPR.
  • Right to object: object to certain legitimate-interest-based processing.
  • Right to withdraw consent: at any time, without affecting the lawfulness of prior processing — for example by stopping location sharing, revoking contacts or location access in your device settings, or changing your advertising choices (see §4 ter).
  • Post-mortem instructions: set instructions on what happens to your data after your death (French Data Protection Act).

To exercise these rights, contact us at contact@myevents360.com. We respond within one month, which may be extended by two months for complex requests; we may ask you to prove your identity if there is reasonable doubt.

You also have the right to lodge a complaint with a supervisory authority, in particular in the Member State where you live (in France, the CNIL).

7. Security

Data is protected by technical and organizational measures: HTTPS for all communications, hashed passwords (bcrypt), short-lived JWT tokens, at-rest encryption of the database (Supabase), of the working memory (Redis, Railway) and of stored files (Cloudflare R2), restricted access to production data. You can add two-factor authentication (code by email or authenticator app, with backup codes) and sign out a device remotely from Profile › Settings › Identification and security › Security; access to the administration console may require it.

8. User-generated content

Photos, videos and messages posted in an event are visible only to members of that event, according to the access settings chosen by the creator; likewise, private messages are visible only to their participants. Files are served through links that are hard to guess, but anyone who obtains a link can open the corresponding file. MyEvents360 does not review this content except for reports, automated moderation, safety alerts, preservation of evidence or requests from an authority; every review by the team is logged.

8 bis. Local on-device storage — automatic download of chat media

Starting with version 1.1.0, MyEvents360 automatically downloads to your device the photos, videos, voice messages and documents received in your conversations (direct messages, groups, event chats). These media are stored only on your device, in a dedicated MyEvents360 folder visible in your system's Photos / Files app, and are never sent to third parties or kept elsewhere than the Cloudflare R2 storage where they were already hosted at the time their author shared them.

You stay in control: from Profile → Storage & data, you can enable or disable auto-download per file type (photos / videos / voice messages / documents) and per network condition (Wi-Fi / mobile data / roaming). You can delete downloaded media at any time (Profile → Storage → Manage storage).

iOS / Android permission: on first activation, your operating system prompts for permission to access your photo library (iOS) or media storage (Android). If you decline, media are still downloaded inside the app (accessible via Profile → Storage → Manage storage) without appearing in your system Photos / Files app.

Legal basis (GDPR): performance of the contract — to enable offline access to media received in your conversations and sharing outside the app.

9. Minors

You must be at least 15 years old to create a MyEvents360 account. You are asked for your date of birth at sign-up: if it shows an age under 15, the account is not created. If you believe a child under 15 is using the service, report their profile from the app (reason "Under the minimum age") or write to us at contact@myevents360.com: we will take the necessary steps, which may include deleting the account concerned.

Default protections for 15 to 17-year-olds

  • The account is not shown to adult users the teen has no connection with (contact, shared private event or group, mutual contact): adding by profile name answers that no profile matches, address-book matching does not suggest it, their profile cannot be opened from a link and no contact request can be sent to them.
  • Locked until age 18: automatic moderation of private messages stays on; live location sharing cannot be made public; the teen cannot create public events; events restricted to adults and open public events are invisible and inaccessible to them; any ads shown are non-personalized.
  • Set to the most protective option by default: who can see online status and last-seen time (their contacts), the precision of shared location (approximate) and night-time muting of notifications (10 pm to 7 am, local time, with non-urgent notifications grouped into a single reminder at the end of that period); "Message previews" is turned off: a message notification shows neither the sender nor the content (see §4, "Content of push notifications"). The teen can always make them stricter; relaxing them is only possible with the agreement of a supervising adult (see below).

Parental supervision (optional)

A parent or trusted adult who is already a contact of the teen in the app can offer them supervision, or the teen can offer it to them. It only starts once the invited person accepts it; the number of adults who can supervise the same teen is limited. Both the teen and the adult can end it at any time, and the other is notified. It ends automatically when the teen turns 18 according to their declared date of birth, or if either account is deleted.

What the adult sees: the teen's list of contacts (name, profile photo, date connected), the events they joined (title, date, organizer's name), contact requests received in the last 7 days (sender's name, date and type of connection, if any), the state of their protection settings and their pending requests to relax them. The adult is alerted when the teen makes a report (only the type of item reported and the date), accepts a new adult contact (name and type of connection) or joins an event whose organizer is not their contact (title, date and city).

What the adult never sees: message content, photos and videos, location, event addresses, the teen's date of birth, or what the teen reported and why.

While supervision is active, relaxing an adjustable protection setting becomes a request sent to the adult, who approves or declines it; without an answer, it expires after 7 days and the setting stays unchanged. The adult can also strengthen a setting; the teen is informed.

Events restricted to adults

An organizer can restrict their event to adults: it is then neither visible nor accessible to accounts under 18, and those accounts cannot be invited to it. The same applies, with no setting needed from the organizer, to any open public event, that is one that can be joined without an invitation.

Turning 18

When the user turns 18 according to their declared date of birth (at the latest the day after their birthday), the account becomes an adult account: supervision ends and settings are kept, and the user can now change them freely.

Contesting an age decision

If our team changes your account's age group (for example after a report), you are informed and can contest it from the app by sending a photo of your identity card, passport or residence permit. This photo is kept in a private storage area, reviewed by a platform administrator, then deleted as soon as a decision is made and no later than 7 days after it was sent (see §5). We do not carry out systematic identity checks: age relies on your own declaration.

10. Changes

This policy may be updated. Any material change will be notified by email or in the app. The last-updated date is shown at the top of the document.