Privacy Policy

Effective date: 29 August 2026
Last updated: 2 November 2026

This Privacy Policy (the “Policy”) explains what personal data MEO Social AI (“MEO”, the “App”, the “Service”) collects and processes, the purposes for which it is used, who it may be shared with, how long it is retained, and the rights available to users.

The operator of MEO and, where applicable, the controller of personal data is:

Aleksandr Lashunin, an individual, Republic of Cyprus
Address: Limassol, Republic of Cyprus
Email: support@meosocial.com

For users in the European Economic Area (“EEA”), the operator is the data controller within the meaning of the GDPR.

By using MEO, you acknowledge that you have read this Policy.

1. Age

MEO is intended only for users aged 18 and over.

During registration, we request your full date of birth to determine your age and enforce age restrictions.

We may also use available age signals provided by Apple or other platforms where such mechanisms are available.

If we determine or reasonably suspect that a user is under 18, their account may be suspended or deleted.

MEO is not designed for the intentional collection of personal data from minors.

2. What Data We Collect

Depending on the features you use, MEO may process the following categories of data.

2.1. Account Data

When you create and use an account, we may collect:

Your display name does not have to match your legal name.

2.2. Referral and Affiliate Programme Data

If you enter an invitation code, share your own code, or participate in the affiliate programme, we may collect the code entered, the link between the referrer and the referred user, the outcome of the bonus award, and hashed device and App Store account identifiers to prevent abuse. For affiliates, we may also collect contact details, payment details, and commission data. See “Referral and Affiliate Programmes” for more information.

2.3. Technical and Device Data

When you use MEO, the App and server automatically process technical data needed to operate the Service, keep it secure, and prevent abuse:

MEO determines the country and network associated with an IP address on its own server using a local geolocation database, without sharing the IP address with third parties. This information is used to prevent fraud and abuse, set regional parameters for rewarded advertising, and, once when an account is created, identify whether the account falls within a region whose laws impose specific requirements on AI companions (see “Regional Requirements for AI Companions”).

3. Signing In with Apple, Google, or Email

If you register through Apple or Google, the relevant provider shares with MEO the information you have authorised it to share and that is necessary for authentication.

This may include:

When using Sign in with Apple, you may use an email address provided through Apple’s Private Email Relay service to keep your email address private.

We use this information to create, authenticate, and protect your account.

If you register with an email address, we store that address and a hashed version of your password. To verify the address, we send an email containing a one-time code to that address during registration; the account is created only after that code is entered. To restore access to a deleted account during the recovery period, we also send an email containing a one-time code to that address. Emails with codes are sent through Resend. Codes are stored as hashes and deleted after use or once they expire; if registration is not completed, the address is deleted together with the code.

For accounts created by the operator by invitation (for example, for creators), the initial password is also stored in an encrypted internal register until the account is permanently deleted, so that it can be provided to the account holder. We recommend changing the password after your first sign-in.

4. What Is Public

By default, the main items of public information for a standard user account are:

Content you intentionally publish through MEO also becomes public, for example:

Publishing means that the relevant information can be viewed by other MEO users.

5. What Is Not Public

By default, MEO does not show other users:

Some of this data is used internally by the Service to provide features and personalisation.

6. AI Character Data

When a user creates an AI character, MEO may store:

Some of this information may be public.

Certain internal settings, such as the system prompt, may not be displayed directly to other users but may be used to shape the AI’s behaviour.

7. User Content

When you publish content, MEO processes:

Media files are stored and delivered using specialist service providers:

Before uploading a video, the App may compress it, reduce its resolution, and prepare a cover frame directly on your device. The prepared file is then sent to the server. Along with the file, MEO stores its technical properties: type, size, resolution, duration, and orientation.

Published media files are accessible through direct links. To speed up loading, copies are temporarily stored (cached) on content delivery network servers in different countries and in the App’s local storage on viewers’ devices (see “Hosting”, “International Data Transfers”, and “Backups and Deletion Delays”).

8. AI Chats

MEO allows users to communicate one-to-one with AI characters and in group chats with several AI characters (there are no other people in these chats).

Local History

The full AI chat history is stored primarily on the user’s device.

MEO does not maintain a conventional server-side archive of the full history of private AI chats that the operator can browse.

Deleting local history or app data may remove that history from the device.

Deleting your MEO account will not necessarily physically delete files that remain stored locally on your device. You can delete the relevant app data or uninstall the App.

In addition to chat history, the App stores operational data and cached content on the device, such as images and videos from the feed, to improve performance. The cache is cleared automatically or when the App is uninstalled.

Processing When Generating a Response

To enable the AI to respond, MEO sends the AI provider the data necessary for the particular interaction.

Depending on the feature and settings, this may include:

Before the first such transfer, MEO provides a separate notice about processing by a third-party AI provider and requests the relevant permission.

If signs of a risk to life are automatically detected in a message, the context sent to the AI provider includes an internal instruction to take what has been said seriously. This applies to all users. For users in regions with specific requirements for AI companions, additional instructions require the character to answer truthfully when asked whether it is human and to remind the user about crisis support services (see “Regional Requirements for AI Companions” and “Crisis Protocol”). These instructions contain no personal data.

Character-Initiated Messages

While the chat screen is open, an AI character may initiate a message, for example, to continue a thought or return to something said earlier if you have been silent for a while. These messages are generated in the same way as replies: the App sends recent conversation context to the server, which forwards it to the AI provider. This happens only while the chat is open on your device. When the App is not open, the character does not generate messages or send notifications on its own behalf.

Conversation State

To maintain a coherent conversation, MEO briefly stores operational session state on the server, such as the current conversation mode, a simulated emotional state for the character, message counters, and similar parameters, without message text. This state is automatically deleted two hours after the last activity.

Group Chats

In a group chat, you communicate with several AI characters at once. Messages and necessary context are sent to the AI provider in the same way as in a one-to-one chat. To operate a group chat, MEO stores session information on the server: the topic, selected characters, conversation mode, message count, and activity times.

Reporting a Message

If you report a message in an AI chat, MEO receives the text of that message together with the report and the information needed to review it: the message author (you or the character), the character, the chat type, and, for a group chat, its topic. The MEO operator may view that message. The rest of the conversation is not sent with the report (see “Reports and Moderation”).

9. OpenAI

MEO currently uses the OpenAI API for text-based AI conversations and supporting AI features, and the OpenAI Realtime API for voice calls with AI characters.

Supporting features include, for example, generating searchable representations (embeddings) of AI Memory entries, as well as automatically translating and improving text entered by a creator when setting up a character (name, description, and communication style).

OpenAI receives only the context necessary to provide the relevant AI feature, subject to the arrangements described above.

MEO does not use users’ private AI conversations to train its own AI models and does not share user data for training OpenAI models.

Under OpenAI’s policies, API data is not used to train OpenAI models by default and may be retained temporarily (generally for up to 30 days) to provide the service and prevent abuse. Processing is also governed by OpenAI’s applicable terms and current privacy and data processing documentation.

10. Permission for AI Data Processing

Before transferring personal data to a third-party AI provider, MEO may display a separate “AI & Privacy” screen.

The user can select:

If permission is not granted, features that require data to be sent to an AI provider, such as AI chat or AI voice conversations, may be unavailable.

There is no separate setting in the App for withdrawing this permission. You can withdraw it by stopping your use of AI features, deleting your account, or contacting support@meosocial.com.

Once permission is withdrawn, MEO stops making new transfers of personal data for AI features that require that permission. This does not necessarily result in the immediate deletion of data already held by a data processor within its permitted retention period.

11. AI Memory

MEO may use a server-side AI Memory feature.

Memory is designed to store individual facts or notes that allow an AI character to remember information between conversations.

Memory is not a complete copy of the chat history.

AI Memory is enabled by default. You can disable it in the App’s settings under “Memory”. If you tell a character about your health, experiences of loss, relationships, or other personal circumstances, Memory may save that information as relevant to future conversations.

A Memory entry may contain the text of a fact or note, a brief summary, an importance score and emotional context, and a numerical representation of the text (an embedding) that helps retrieve relevant entries. The entry’s text is sent to OpenAI to generate this representation.

Each entry is stored together with the original conversation excerpt from which it was derived: for a chat, the user’s message and the character’s reply (usually together with the character’s preceding message); for a group chat, the user’s message and the characters’ replies to it; and for a voice call, text from the end of the conversation (up to 2,000 characters, which may be the entire conversation for a short call). The beginning of the excerpt is visible on the entry card as “Original Text”. For entries from group chats, a short quotation from the excerpt may be included in the context sent to characters who took part in that chat when the user later speaks with them individually. The excerpt is retained and deleted together with the entry.

Depending on the available app version, users may be able to:

Each user–character pair has an entry limit. When the limit is exceeded, the oldest low-importance entries are automatically deleted, while important entries are retained. In addition to Memory entries, MEO stores, for each character, ongoing communication preferences inferred from conversations (for example, form of address and tone) and records of questions the character has already asked about you to avoid repetition. These are used only in conversations with that character and are deleted when the account is deleted or all Memory is cleared.

When Memory is disabled, no new entries should be created.

Deleting Memory removes the relevant note from MEO’s active systems, except for limited technical copies that may remain until the normal backup and deletion cycle is complete.

12. Sensitive Information

MEO does not request information about the following as standard profile fields:

However, users may voluntarily mention this information in an AI conversation.

In that case, the information may be processed as part of the message and conversation context to provide the requested AI response.

If Memory is enabled, individual details from conversations and the excerpts from which they were derived may potentially be saved in Memory. Users can view and delete individual Memory entries or disable Memory entirely at any time (see “AI Memory”).

All users’ messages are automatically checked for signs of suicidal thoughts and self-harm so that the character can respond seriously. Users in regions with specific requirements for AI companions are also shown a notice about crisis support services. The result of this check is not saved in the user’s profile or used for any other purpose (see “Crisis Protocol”).

MEO does not use this information for advertising targeting.

13. AI Voice Conversations

Voice Calls

MEO allows users to speak with an AI character by voice.

To provide this feature, the audio stream is sent to the AI provider, currently the OpenAI Realtime API, for processing and AI response generation.

In its current architecture, MEO:

During a call, the AI provider converts the user’s speech into text in real time (for the “speaking” and “listening” indicators and safety features), and the character’s responses are accompanied by a text version. MEO holds this text in server memory during the call and until post-call processing is complete. If the user has enabled AI Memory, the conversation text (not the audio) is sent to the AI provider once after the call ends to extract individual facts for AI Memory, in the same way as chat messages are processed (see “AI Memory”). Each Memory entry derived from a call is accompanied by an excerpt from the end of the conversation (up to 2,000 characters, which may be the entire conversation for a short call) as its source. The excerpt is retained and deleted together with the entry. The remaining conversation text is deleted. If Memory is disabled or the call is too short, the conversation text is deleted as soon as the call ends, without being sent to the AI provider for this purpose. If there is nothing to remember, it is deleted immediately after that transfer.

Data is nevertheless sent to OpenAI for processing and may be subject to the applicable OpenAI API data retention and security policies.

MEO stores technical information about the call: the character, duration, number of tokens deducted, and estimated call cost for internal accounting.

Character Voice Replies

A character may reply to a chat message by voice: the AI provider (OpenAI) converts the response text into speech, which is played in the App. The character decides whether to reply by voice based on the conversation context and whether the feature is available under your plan. The audio file of a voice reply is stored locally in the App on your device for replay; it is not stored on the server.

Voice Messages

If you send a voice message to an AI character, the audio recording is sent to MEO’s server and the AI provider for speech-to-text conversion. The recognised text is processed as a regular chat message. MEO does not retain the voice message recording after transcription.

13A. Regional Requirements for AI Companions

The laws of certain US states (currently California, Colorado, Connecticut, Georgia, Hawaii, Idaho, Iowa, Nebraska, New York, Oregon, Rhode Island, and Washington) impose specific requirements on services offering AI companions: to notify users that they are interacting with AI, repeat that notice periodically, and apply a response protocol when signs of suicidal thoughts or self-harm are detected.

Data processed. To apply these requirements only to the users concerned, MEO determines once, when an account is created, whether the request’s IP address corresponds to one of the states listed above. It stores a single value in the account: the state code (for example, “NY”), or no value. The location is determined on MEO’s server using a local geolocation database. The IP address itself is not retained for this purpose, and addresses belonging to data centres and VPN services are disregarded. The value does not change on subsequent sign-ins or when the user travels. The operator may change or remove it at the user’s request.

Effect on the Service. For accounts with this value, MEO:

The Service operates as usual for all other accounts.

Legal basis. Compliance with legal obligations applicable to MEO in the relevant regions, and MEO’s legitimate interest in protecting users.

Retention. For as long as the account exists; deleted when the account is permanently deleted.

13B. Crisis Protocol

MEO is not an emergency or crisis support service. The protocol described below is an automated safety measure in AI chats and voice calls for the accounts specified in “Regional Requirements for AI Companions”.

13B.1. What Is Detected

User messages are automatically checked for signs of suicidal thoughts, suicide, or self-harm. In voice calls, the check is performed on the speech transcript generated by the AI provider in real time. MEO does not retain the transcript for this check (see “AI Voice Conversations” for information about what is retained after a call).

For all other users, a simpler check applies: a dictionary-based search on MEO’s server. If a match is found, the character receives an instruction to take what has been said seriously. These users are not shown a notice about crisis support services, and the check result is not retained.

13B.2. How the Check Works

The check is performed automatically using three methods. A trigger from any one of them is sufficient:

No MEO staff member reads messages as part of this check.

13B.3. What Happens When the Protocol Is Triggered

To avoid repeated notices within a single conversation, the notice is shown no more than once every ten minutes.

13B.4. What Data Is Retained

For reporting required by certain state laws, MEO keeps a count of notices shown that direct users to crisis support services, aggregated only by date and state, without user identifiers or message text. A record of the trigger, including the detection method and state, is written to the server’s technical log, also without a user identifier or message text. The check result is not saved in the user’s profile, does not affect access to the Service, and is not used for personalisation or advertising.

MEO does not disclose information about these messages to authorities, support services, or other third parties, or contact the user about them, unless required by law.

13B.5. Limitations

Automated detection is not infallible: it may miss a message or trigger without justification. The protocol does not constitute monitoring of a user’s condition or an assessment of their health. If you or someone nearby is in danger, contact local emergency services.

Legal basis. Compliance with legal obligations applicable to MEO in the relevant regions and protection of the user’s vital interests. Health information voluntarily disclosed by the user in a conversation is processed only to the extent necessary to display the notice and is not retained as part of this check (see “AI Memory” regarding storage in AI Memory).

14. Personalisation

MEO may use user data to personalise the Service.

This may include:

This data may affect:

MEO does not use this personalisation to make decisions that have legal or similarly significant effects on the user.

15. Likes, Follows, and Social Activity

MEO may store:

This information is used to:

Likes, follows, and comments are not private: your name, username, and avatar are visible to the character’s creator and other users in the relevant lists (see “What Is Public”).

16. Comments

Public comments are currently the main form of direct interaction between users in MEO.

When you post a comment, we store:

A comment may be visible to other users until it is deleted or restricted.

17. Block Creator

If a user uses Block Creator, MEO stores a record of the block, such as:

This data is needed to:

Blocking data is not public.

When an account is unblocked, the relevant active block is deleted or its status is changed.

18. Notifications

MEO may display in-app notifications and send push notifications.

Push notifications are sent if they are enabled in your device’s system settings. To deliver them, MEO stores your device’s push notification token, platform, time zone, language, and country. Notifications are delivered through Expo (650 Industries, Inc., USA) and Apple’s or Google’s system push notification services. Expo stores the push notification token but does not retain notification content.

Notifications may concern:

Reminders take your time zone into account to avoid disturbing you at night.

You can disable push notifications in your device settings at any time. This does not affect other MEO features.

In-app notifications are retained for no more than 30 days. MEO also keeps a log of sent push notifications (type, text, time, and delivery outcome) for diagnostics and to prevent duplicate sends.

19. Reports and Moderation

If a user submits a report, we may process:

MEO uses user reports, manual review, and Block Creator to address inappropriate or unlawful content. MEO may introduce additional automated moderation tools. If third-party services that receive user content are engaged for this purpose, this Policy will be updated.

Media storage and delivery providers (ImageKit and Cloudflare) process files only for technical purposes and do not make moderation decisions.

When reviewing a report, an MEO staff member or the operator may view the reported content, including the text of an AI chat message if the report concerns that message, and the information necessary to review the report.

This does not mean that moderators have general access to the full history of a user’s private AI chats.

If action is taken in response to a report, the character’s owner receives a message stating the reason. If the selected reason is “Other”, your written explanation may be included. The reporting user’s identity is not disclosed to the owner.

20. Diagnostics and Sentry

MEO uses Sentry to diagnose errors and crashes in the production environment.

We may send Sentry technical data such as:

MEO does not send Sentry:

We apply the principle of data minimisation and configure error reporting to exclude this information from diagnostic data.

Error data is stored in Sentry’s EU region (Frankfurt, Germany). Certain administrative metadata relating to MEO’s Sentry account may be processed in the US.

MEO’s technical server logs may contain excerpts from chat messages, character replies, and voice call text, including the source text of AI Memory entries. These logs are not a conversation archive, are not used to restore or routinely browse conversations, and are retained within the hosting provider’s operational log retention period (see “Retention Periods”).

The App may also send its own technical performance measurements to MEO’s server: device model, operating system and app version, operation durations, interface responsiveness metrics, and media loading metrics, together with the internal user ID. This data is used only to identify and resolve app performance issues.

21. Subscriptions and Purchases

MEO may process data relating to subscriptions and in-app purchases (IAP), including:

Payments on iOS are processed by Apple, rather than directly by MEO.

MEO does not receive the user’s full payment card number from Apple.

22. RevenueCat

MEO uses RevenueCat to manage subscriptions and entitlements and to verify purchases.

RevenueCat may receive:

After an account is deleted, RevenueCat retains purchase history linked to the account’s internal ID. This is needed to transfer and restore subscriptions, maintain accounting records, and handle refunds. On request to support@meosocial.com, we will delete this data unless doing so would conflict with record-keeping obligations.

23. Meo Tokens

MEO stores the information necessary to manage Meo Tokens, including:

The token balance is needed to determine the availability and use of AI features.

When an account is permanently deleted, its regular token balance is deleted or anonymised along with the account, except for transaction records that must be retained for accounting, tax, fraud prevention, or other legal reasons.

A new account receives welcome tokens only once per email address, Apple ID, or Google ID. To prevent deletion and re-registration from resulting in another award, a hash of that identifier, irreversibly transformed using a secret key, is retained after account deletion. The email address or identifier cannot be reconstructed from the hash. It is used only for this check and when deciding whether to award an invitation-code bonus (Section 24). The hash is deleted no later than 3 years after the welcome tokens were awarded.

24. Referral and Affiliate Programmes

MEO offers a “Refer a Friend” programme and an affiliate programme for creators and bloggers. Participation is voluntary: an invitation code is not required to use MEO.

Data processed. If you enter an invitation code, we record the code itself, the link between your account and the referrer’s account (attribution), the date, the outcome of the bonus award, and the reason for refusal if no bonus is awarded. To prevent abuse (multiple accounts belonging to one person or self-referral), we process the device’s identifier for vendor (IDFV), the App Store transaction identifier (App Transaction ID), and your account identifier (email address, Apple ID, or Google ID) in hashed form, irreversibly transformed using a secret key. We also process technical characteristics of the request, such as the IP address and whether it belongs to a data centre. If you share your code, we show you the number of referred users, dates, bonus statuses, and the reason why a bonus was not awarded (for example, the referred user previously had an MEO account, their device or App Store account has already received a bonus, the account has been deleted, or the activation condition was not met). Referred users’ names and other details are not disclosed.

Affiliates. For affiliate programme participants, we also process their name or business name, contact details, payment details (payment service email address or bank details), accrued commission amounts, payout requests, and payout history. Affiliates receive anonymised statistics for each referred user: the date of registration using the code, plan, number of paid periods, and payment and refund amounts and dates, without names, contact details, or other identifying information. When a user enters an affiliate code, they automatically follow the affiliate’s characters. Like any creator, the affiliate receives a standard new-follower notification (username and avatar), without any indication that the follow resulted from a code.

Purposes and legal bases. Awarding bonuses and calculating commissions (performance of the programme terms), preventing fraud and abuse (legitimate interest), and accounting and tax records for payouts (legal obligation).

Retention. Attribution and commission records are retained for as long as the account exists and thereafter for the periods necessary to account for payouts. Hashed device and App Store account identifiers are retained after account deletion; otherwise, deletion and re-registration would allow bonuses to be received repeatedly. These records do not identify individuals and are used only to protect the programme against abuse, for example, to check whether a device or account has already received a bonus. They are deleted no later than 3 years after their last use. While the account exists, these hashes are also stored in it, including to detect self-referral. For this purpose, each time the App launches, it sends the device identifier (IDFV) and App Store transaction identifier to the server. The server stores only their hashes, for all signed-in users, not just programme participants. Affiliate payment details are retained for the duration of the affiliate relationship and thereafter for the applicable record-keeping periods.

Sharing. The invitation code used to register is sent to RevenueCat as a subscription analytics attribute (Section 22). Programme data is not shared with other third parties, except with payment services when paying affiliate commissions or where required by law.

25. Rewarded Advertising

MEO uses Google AdMob to display rewarded advertisements.

When advertising is used, Google and associated advertising technology providers may process technical and advertising data, including, depending on the device, consent, and settings:

MEO does not send private AI chat content or AI Memory content to AdMob for advertising targeting.

MEO also does not use a user’s age, gender, or private AI conversation content as its own signals for advertising personalisation.

To confirm that rewards have been issued and prevent fraud, MEO stores reward session information: session ID, reward amount, status, and daily limits, as well as the IP address, the country and network determined from it, the device identifier, and IDFV. Sessions in which a reward was issued are retained as part of the token credit history. Incomplete and rejected sessions are deleted after 30 days, and technical ad delivery logs after 7 days. When requesting an advertisement, MEO sends Google the reward session ID and your internal account ID (a random operational code, rather than your name or email), so that viewing confirmation is associated with your particular session. For server-side reward verification, Google sends MEO the reward session ID. For each ad impression, MEO also receives from Google and stores, linked to the session, impression revenue information (amount, currency, and estimate precision) to calculate reward amounts and reconcile records with the advertising network.

The reward amount depends on the country determined from the IP address. If the country cannot be determined, or a VPN, proxy, or data centre address is used, the minimum reward applies (see “Reward Tokens and Advertising” in the Terms of Use).

On iOS devices, before displaying the first advertisement (on the free tokens screen), MEO requests system permission for tracking through App Tracking Transparency. If you allow tracking, Google may use the device’s advertising identifier (IDFA) to select and measure advertisements. If you decline, advertisements are shown without it and may be less relevant; this does not affect the reward amount. You can change your choice in iOS settings (“Privacy & Security” → “Tracking”).

26. Advertising Consent

For users in the EEA, the UK, and Switzerland, MEO uses Google’s User Messaging Platform or another applicable consent management platform (CMP) to obtain and manage advertising consent where required.

Where applicable, users can:

Declining consent to personalised advertising should not automatically prevent use of MEO as a whole. Depending on the region and availability, non-personalised or limited advertisements may be used.

27. We Do Not Sell Private Conversations

MEO does not sell private AI conversations or AI Memory for money.

MEO does not provide private AI conversation content to advertising networks for advertising targeting.

However, some privacy laws use specific legal definitions of “sale” and “sharing” that may cover certain transfers of data through advertising technologies even where no data is sold for money.

If applicable law classifies the operation of an advertising SDK as a sale or sharing of data, MEO provides the relevant notices and opt-out or consent mechanisms where required.

28. Hosting

MEO’s main server infrastructure, database, and cache are hosted by Render in the European Union (Frankfurt, Germany).

Media files are stored by specialist providers:

To speed up loading, copies of media files are cached on ImageKit and Cloudflare content delivery network servers worldwide.

MEO nevertheless uses international data processors, so we do not claim that all user data is stored exclusively within the EU (see “International Data Transfers”).

29. Third-Party Providers

MEO may currently use the following main categories of service providers:

Provider Main Purpose
Render Backend, database, and cache hosting (EU, Germany)
OpenAI AI chat, real-time voice calls, and supporting AI features
ImageKit Image storage, processing (size and format), and delivery
Cloudflare Video storage (R2) and video delivery through a content delivery network
Expo Push notification and app update delivery
Resend Sending emails with one-time codes to verify the address during registration and to restore account access
RevenueCat Subscriptions, purchases, and entitlement management
Google AdMob / UMP Rewarded advertising and advertising consent
Sentry Crash and error diagnostics (data stored in the EU region)
Apple App Store, in-app purchases (IAP), Sign in with Apple, and push notification delivery
Google Google Sign-In, related authentication services, and push notification delivery on Android

MEO requires data processors to process user data in accordance with applicable contractual obligations and privacy and security requirements, and to provide a level of protection consistent with applicable law and App Store requirements.

The list of service providers may change as MEO develops.

This Policy will be updated if there is a material change in how data is processed.

30. How We Use Data

We use personal data for:

31. Legal Bases for the EEA and the UK

Where the GDPR or UK GDPR applies, we rely on one or more of the following legal bases.

Performance of a Contract

Where processing is necessary to provide features requested by the user, for example:

Legitimate Interests

Where processing is necessary for our legitimate interests and those interests are not overridden by the user’s rights, for example:

Consent

Where the law requires consent, for example for:

Legal Obligation

Where data must be processed or retained for:

32. International Data Transfers

Some of MEO’s data processors are located or process information outside the EEA, including in the US and India.

Personal data may therefore be transferred to:

For example, OpenAI, RevenueCat, Google, Apple, Cloudflare, Expo, Resend, Render, and Sentry are US companies (although Render’s servers and Sentry’s error data are located in the EU). ImageKit is an Indian company: MEO’s image files are stored in the EU (Germany), while operational data and delivery logs are stored in the US. Copies of media files delivered through content delivery networks are temporarily stored on servers in different countries, closer to where they are viewed.

Where the GDPR or UK GDPR requires an appropriate transfer mechanism, we use or rely on the following, depending on the service provider and circumstances:

33. Retention Periods

We do not retain personal data for longer than necessary for the relevant purpose, unless a longer retention period is required by law.

The main rules are:

Category General Retention Period / Criterion
Account and profile data For as long as the account exists, plus the applicable deletion/recovery period
AI Memory Until the user deletes an entry or all Memory, or the account is deleted. Disabling Memory stops new entries from being created but does not delete entries already saved
Full private chat history Stored locally on the device, rather than as a permanent MEO server-side history
Group chat information For as long as the account exists
State code for regional AI companion requirements For as long as the account exists
Crisis protocol The message check result is not retained. The count of notices shown, aggregated by date and state without personal data, is retained for the statutory reporting periods
OpenAI API inputs and outputs According to the applicable OpenAI configuration. For most API use cases, OpenAI specifies up to 30 days, subject to exceptions
Public user content For as long as it remains published or until the user deletes it. Comments are deleted with the account. AI characters and their posts that the user has not deleted remain after account deletion (see “Characters After Account Deletion”). A character deleted by the user, together with its posts, comments, and likes, is retained in an internal archive for 30 days to allow restoration on request, and is then permanently deleted. Copies of media files in content delivery network caches and on devices remain until the cache expires
Block Creator records For as long as the block is active or the data is needed for security purposes
Reports and moderation For as long as necessary to review reports, take action, prevent abuse, handle appeals, or address legal claims
Referral and affiliate programmes Attributions and commissions: for as long as the account exists and for the applicable record-keeping periods. Hashed device and App Store account identifiers: stored in the account for as long as it exists (to detect self-referral), and for up to 3 years after last use (to prevent repeat bonus awards). Affiliate details: for the duration of the affiliate relationship and for the applicable record-keeping periods
Subscription and token data For as long as the account exists. Payment event records (event type, product, price and currency, storefront country, transaction identifiers, and internal account ID) are retained longer, for the applicable accounting and tax record-keeping periods. The hash of the identifier of an account that received welcome tokens is retained after account deletion to prevent repeat awards, but for no longer than 3 years after the tokens were awarded (Section 23)
Rewarded advertising Sessions in which a reward was issued: as part of the token credit history. Incomplete and rejected sessions: 30 days. Technical ad delivery logs: 7 days
Technical data and security logs Rate-limiting records: 7 days. Server request logs and device information: for as long as needed for security and abuse prevention, but no longer than the account exists (including the deletion period). Server operation logs held by the hosting provider: within its operational retention period (generally no more than a few weeks)
Voice call conversation text During the call and until post-call processing is complete. If AI Memory is enabled, until the one-time transfer to the AI provider to extract facts immediately after the call ends. An excerpt from the end of the conversation attached to a Memory entry as its source is retained for as long as that entry exists
Operational chat session state 2 hours after the last activity
Push tokens and notifications Token: while notifications are enabled and the account exists. In-app notifications: up to 30 days. Push notification delivery log: for as long as the account exists
Diagnostics (Sentry and internal measurements) Within the configured operational retention period and for as long as needed for diagnostics and security
Support correspondence For as long as necessary to resolve the request and for related legal and business purposes
Backups Until deleted during the normal backup rotation cycle

Where an exact retention period cannot be determined in advance, we apply criteria based on necessity, legal obligations, security, and normal technical deletion cycles.

34. 30-Day Account Deletion Period

Users can initiate account deletion directly in MEO.

Following a deletion request, the account may enter “Pending Deletion” status for 30 days or, if a paid subscription period remains active and ends later, until the end of that period.

During this period, the account and associated data are retained so that the user can cancel deletion and restore the account.

You can restore your account using the “Restore Account” button on the sign-in screen or by contacting support (support@meosocial.com), subject to reasonable identity verification. If, during this period, you sign in using the same Apple ID or Google account, or register again using the same email address, a new account is created and the previous account is immediately and permanently erased and can no longer be restored.

If the user restores the account during this period, the deletion process stops.

If the account is not restored, MEO begins permanently deleting or irreversibly anonymising the relevant data after this period ends.

MEO may permanently delete the account before this period ends if the Terms of Use are violated or at your request to support.

35. What Is Deleted When an Account Is Permanently Deleted

Upon permanent account deletion, MEO deletes or irreversibly anonymises the following, where applicable:

AI characters you created and their posts are not automatically deleted when you delete your account. See “Characters After Account Deletion”.

Limited records may continue to be retained where necessary for:

36. Active Subscriptions and Account Deletion

Deleting an MEO account does not automatically cancel an Apple App Store subscription.

If the user has an active paid subscription period that ends more than 30 days after the deletion request, the account remains pending deletion until that period ends. During this time, the account can be restored and paid access is preserved. Permanent deletion begins after the paid period ends.

After permanent deletion, limited purchase information may still be retained where required by accounting, tax, fraud prevention, or other legal obligations.

37. Characters After Account Deletion

Deleting your account does not automatically delete AI characters you created or their posts (text, images, and videos). If you want a character or individual posts to be deleted, delete them in the App before deleting your account.

Characters you have not deleted continue to exist in MEO as independent characters:

If, after deleting your account, you want a remaining character or its posts deleted, for example because they contain your photographs, email support@meosocial.com.

38. Backups and Deletion Delays

Deletion from active systems does not necessarily mean immediate physical deletion from every backup or every data processor’s systems.

Limited copies may remain in:

until they are removed through normal retention and deletion cycles.

These copies must not be used for the routine operation of the deleted account.

39. Access to Data

Depending on applicable law, users may request:

Requests can be sent to: support@meosocial.com

MEO may require reasonable verification of the user’s identity before fulfilling a request.

40. Data Rectification

Some information can be changed directly in MEO’s settings.

For data you cannot change yourself, contact: support@meosocial.com

41. Right to Erasure

Users can initiate account deletion directly in MEO.

Certain data can also be deleted without deleting the entire account, for example:

The right to erasure may be limited where the law permits or requires continued retention of certain information.

42. Data Portability

Where applicable law provides this right, users may request their data in a structured, commonly used, machine-readable format, within the scope provided by law and to the extent that the data is technically available.

43. Withdrawal of Consent

Where processing is based on consent, users may withdraw that consent at any time.

Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.

In particular, users can manage:

After consent is withdrawn, the relevant feature may stop working if the processing is objectively necessary to provide it.

44. Automated Processing and Recommendations

MEO uses algorithms for:

Recommendations may take behavioural signals and profile data into account.

MEO does not use these systems to make decisions based solely on automated processing that produce legal effects concerning the user or similarly significantly affect them within the meaning of Article 22 of the GDPR.

Moderation decisions may be based on automated signals, but users may have a right to an explanation or to appeal where provided by MEO’s rules or the law.

45. Rights of EEA Users

Users covered by the GDPR may have the following rights:

If you believe that the processing of your personal data infringes the GDPR, you may also contact the competent supervisory authority.

46. Other Jurisdictions

Users in the UK, the US, Canada, Australia, New Zealand, and other countries may have additional personal data rights under local law.

Depending on applicable law, these rights may include:

MEO will honour these requests where the relevant law applies to MEO.

47. Security

We use reasonable technical and organisational measures to protect data against:

These measures may include:

No online service can guarantee absolute security.

48. Data Breaches

If a personal data breach occurs, MEO takes reasonable steps to:

where the relevant notification is required by applicable law.

49. Third-Party Links and Services

MEO may contain links or redirects to third-party websites and services.

After following such a link or redirect, users may be subject to the relevant third party’s privacy practices.

MEO does not control independent data processing by third-party websites that users choose to open outside MEO.

50. Changes to This Policy

We may amend this Policy in response to:

The date of the most recent update is shown at the beginning of this document.

If a change materially affects users’ personal data rights, MEO may provide an additional in-app notice or request renewed consent or permission where required.

51. Contact Details

For questions about privacy and personal data:

Aleksandr Lashunin, operator of MEO

Address: Limassol

Country: Republic of Cyprus

Privacy email: support@meosocial.com