ReadIM
FrançaisHome

Privacy Policy

Last updated: 30 September 2026
This policy explains how the ReadIM service and Android application access, collect, use, store and share user and device data. It also explains the choices and deletion options available to users.

1. Service and privacy contact

This policy applies to the ReadIM service and the ReadIM Android application. For any privacy question, request or complaint, contact support@readim.com.

2. Data ReadIM may process

Depending on the features used, ReadIM may process:

3. Android permissions and files

The Android application requests permissions only when a related feature needs them. Location is used for location/proximity features; camera and microphone are used for capture, voice messages and calls; notifications are used to deliver ReadIM alerts. When the user selects a photo, video or file, Android's system picker is used: ReadIM does not need general access to all files on the device for that action.

For optional profile-photo verification, camera frames and face embeddings are processed locally on the device/browser by the verification component. ReadIM does not store the verification camera image or a reusable facial template on its server. The server receives the verification result values needed to validate the check and retains a verification status, date, photo version and a cryptographic fingerprint of the published profile photo.

4. Why the data is used

Data is used to create and secure accounts; provide profiles, groups, search, contacts and private messaging; deliver media; calculate proximity or location results when requested; provide notifications and email reminders; enable calls; prevent abuse; process reports and moderation; maintain and improve the service; measure usage; and comply with legal obligations.

5. Legal bases and user choices

Depending on the data and feature, processing may be necessary to provide the service requested by the user, based on ReadIM's legitimate interests in security and service operation, required by law, or based on consent when consent is legally required. Device permissions remain under the user's control and can be refused or withdrawn in Android settings. Refusing an optional permission only disables the features that require it.

6. Profiles, groups and search visibility

Profile information and user-generated content may be visible to other members according to the relevant group, search and messaging settings. Public group content is visible according to that group's access rules. Search results can use profile data, recent activity, country, city, age range, gender and other filters that the service makes available.

7. Private messaging, media and calls

Private messages and media are intended for the participants in the conversation, subject to technical processing needed for delivery, safety and moderation. Private conversation files are protected from public access and certain private-message storage is encrypted at rest.

Some private media are described as ephemeral. Depending on the feature, these files may expire automatically, including after viewing or after a limited technical availability period. A user may also delete their own local copy of a conversation while another participant can retain their copy.

Audio/video calls use WebRTC. ReadIM currently uses a direct peer-to-peer connection when technically possible and Cloudflare STUN to establish connectivity, without a ReadIM TURN media relay. Audio/video streams are not stored by ReadIM as part of the call feature. A direct WebRTC connection can expose network information such as public IP addresses to the connection infrastructure and, as inherent to peer-to-peer communication, to the other endpoint.

8. Location and reverse geocoding

When a user chooses a location feature, coordinates can be sent to ReadIM and stored for the purposes of proximity, city recognition and search. ReadIM may send the coordinates to BigDataCloud to convert them into a city, region and country. The resulting geographic information may be stored and used in ReadIM search. Precise coordinates are not intended to be publicly displayed when only a city, area or distance is needed.

9. Notifications and email

ReadIM uses Google Firebase Cloud Messaging (FCM) for push notifications. ReadIM stores a notification token and limited device/platform information. Notification delivery can transmit to Google the token and notification metadata such as a title, sender username, event type and navigation information. Private message text is not used as the notification body in the current private-message flow.

When email reminders are enabled, ReadIM can use Mailjet. The recipient email address and the information required to send the reminder are then transmitted to Mailjet. ReadIM reminder emails use a generic description of the event and do not include the private message text.

10. Payments

When a user purchases a paid ReadIM service on the web, payment is processed by PayPal. ReadIM may store the PayPal order and capture identifiers, product, amount, currency, payment status, payer email returned by PayPal when available, acceptance timestamp and the access-expiry information needed to provide the purchase, provide customer support, keep accounting records, prevent fraud and handle disputes. ReadIM does not receive or store the payer’s full bank-card credentials.

11. Reports, moderation and safety

When a user voluntarily reports content or an account, ReadIM may retain the reported item, a limited surrounding context, the reporter and reported account identifiers, the selected reason, moderation decisions and limited history needed to prevent abuse, protect users, investigate disputes or meet legal obligations. For an ephemeral private medium, an evidence copy can be created when the recipient reports it while it is still available.

12. Cookies, local storage, analytics and advertising

ReadIM uses cookies or local storage needed for authentication, security, preferences, PWA/app operation and interface state. ReadIM also uses internal service statistics.

ReadIM may use Google Analytics to measure use of the website/service. Google may receive technical and navigation information. In the Android application, Google Analytics is not loaded until the user explicitly enables the optional analytics choice; that choice can later be changed in ReadIM settings. Where another consent mechanism applies on the website, Analytics follows the choice collected there.

The ReadIM website may display advertising through Google AdSense. Depending on the configuration and user choice, Google and its advertising technology partners may use cookies, identifiers, IP addresses or similar technologies for delivery, measurement or personalization. Advertising and analytics disclosures must remain consistent with the consent configuration actually used.

13. Service providers and data recipients

ReadIM does not sell personal and sensitive user data. Data may be processed by service providers only when necessary for their role, including hosting/infrastructure providers, Google/Firebase for notifications, Mailjet for email delivery, BigDataCloud for reverse geocoding, Cloudflare STUN for WebRTC connectivity, PayPal for web payments, and Google Analytics or advertising providers when those services are active. Technical content libraries may also be delivered through a CDN; this can expose ordinary connection metadata such as IP address and browser information to that CDN.

Data may also be disclosed when legally required, to protect users or the service, or as part of a legally compliant business transfer with appropriate notice.

14. Retention

Account and profile data are generally kept while the account is active and as needed to provide the service. Ephemeral private media follow the availability rules shown in the interface and may have short technical expiry periods. Notification tokens are removed when no longer attached to the relevant account/device or when the account is deleted. Technical logs, security records and aggregated statistics are kept only for periods appropriate to their purpose.

After account deletion, ReadIM deletes the account directory and account/profile/sign-in data that is no longer required. Content already delivered or published can remain in another member's copy or in group history when needed to keep conversations understandable, generally marked as coming from a deleted profile. Limited moderation, fraud-prevention, security or legal evidence may be retained where necessary and is subject to access restrictions.

15. Security

ReadIM uses measures intended to prevent unauthorized access, including authenticated sessions, access controls, separation of public/private storage, encryption for certain private conversation data at rest, and HTTPS for the public web/app service. No online service can guarantee zero risk; users should also protect their account credentials and avoid sending information they do not wish to share.

16. Your rights and account deletion

Depending on applicable law, including the GDPR where it applies, users may have rights of access, rectification, erasure, restriction, objection and portability, and may withdraw consent for future processing. Users may also complain to their competent data-protection authority.

ReadIM provides account deletion from within the application. A deletion request can also be made without the application using the public account deletion page. Privacy requests can be sent to support@readim.com. Proportionate identity verification may be requested to prevent unauthorized account access or deletion.

17. Changes to this policy

This policy may change when ReadIM, its providers, its data practices or applicable rules change. The update date at the top of the page identifies the current version.

The privacy policy and the Google Play Data safety form must describe the application's actual behavior. When ReadIM changes how it handles user data, both disclosures must be reviewed and updated.