Privacy Policy

Enlerim (enlerim.com and the Enlerim Android app) is responsible for the personal data described in this policy. You can reach us with the contact form linked at the end of this page.

This policy covers the Enlerim website and the Enlerim Android app. The app shows the Enlerim web service inside the app and adds native notifications, calling and permission handling, so the same practices apply to both.

Websites you open from Enlerim, such as ticket sellers, map services or video sites, have their own privacy policies.

• Account: your email address and name from Google Sign-In (see below).
• Profile: the username, display name, bio, profile photo and cover photo you add.
• Content: posts, photos, polls, comments, likes, saves, ratings, favorites, lists, event reviews, follows and blocks.
• Messages: text, photos, voice messages, shared locations and reactions you send, and reports you submit.
• Contact form: the name, email address and message you send us.

• Request data recorded by our web server: IP address, date and time, the requested address, browser or app user agent and referring page.
• Notification data: a notification token, an app installation identifier, app version and build, language, time zone and notification permission status. For browser notifications: the push subscription and the browser's user agent.
• Call data: who called whom, when, for how long and how the call ended, plus technical connection events used to fix call problems.
• Approximate country: estimated from your IP address with a database on our own server to show regional content. It is not saved to your account.
• Short-lived connection data for online status (see Online status).

Enlerim accounts use Google Sign-In. Google checks your password and sign-in; Enlerim never sees or stores your Google password.

When you sign in, Google shares your name, email address, profile picture address and Google account identifier with Enlerim. We save your email address and name in your Enlerim account. The account identifier and picture address are kept in your encrypted sign-in cookie; some older comment and list features also save the picture address with the item you post.

Your email address is not shown to other users.

Your username, display name, bio, profile photo, cover photo, join date, follower and following counts and your public lists, posts, favorites, ratings and comments can be seen by anyone who opens your profile, including people who are not signed in, and can appear in search engines.

Your name is shown on event reviews only if you turn on review attribution in your profile settings.

• Content is shown to other people according to the feature and the visibility you choose; public content can be seen by anyone.
• Photos you upload are stored on our servers. We re-encode them, which removes embedded metadata such as the location where a photo was taken.
• When a post contains a link, our server fetches that page to build a preview. The linked site sees a request from our server, not from your device.
• You can delete posts, comments, lists and other content with the delete options in the app.

• Messages are private between the people in the conversation. They are stored on our servers and sent over encrypted connections, but they are not end-to-end encrypted.
• Voice messages are recorded only while you use the record control, uploaded when you send them and available only to the people in the conversation. Message photos are also available only to them.
• A shared location contains the exact position you choose to send. It is saved with the message and visible to the other person; opening it shows the position in Google Maps.
• We record when you have read a conversation so that the other person can see that their message was seen.
• When you delete a message, its text is cleared and any voice message file is removed. A deleted message's photo is no longer shown, but the file stays on our servers until the sender's account is deleted.
• If you report a message or user, the report and the details you give are sent to Enlerim for review.

The Android app asks for camera, microphone and notification permissions, and the browser asks when a feature needs them. Granting a permission does not by itself send anything to Enlerim.

• Camera: used when you take a photo to upload or send, or turn on your camera in a video call.
• Photos and files: the system picker gives Enlerim only the files you choose; Enlerim does not browse your gallery.
• Microphone: used only while you record a voice message or are in an audio or video call.
• Enlerim does not record in the background or listen continuously. A photo or recording leaves your device only when you upload, send or call.

• Calls run through Enlerim's own media and relay servers. Audio and video are transmitted in real time over encrypted connections and are not recorded or stored.
• We save call history: participants, start, answer and end times, duration and how the call ended. It is shown in your conversation.
• During a call the microphone (and, for video, the camera) is active, and Android shows an ongoing call notification.
• The app reports technical call events, such as whether a connection or microphone started, so that we can fix call problems. These can appear in our server logs.

• On Android, notifications are delivered through Google Firebase Cloud Messaging. In browsers, they are delivered through your browser's push service.
• We store a notification record for each device, including the token, which is encrypted on our servers.
• Direct message notifications do not include the message text. Other notifications can include the other person's name, such as a new follower.
• You can choose notification types and quiet hours in your settings. Signing out on the Android app turns off notifications for that device.

• When you are signed in, other signed-in users can see your current status: online, busy, away or offline.
• You choose Automatic, Online, Busy, Away or Appear offline. On Automatic you appear online while Enlerim is open and away after a few minutes in the background.
• Appear offline shows you as offline to everyone, even while you use Enlerim.
• People you have blocked and people who have blocked you cannot see your status. Visitors who are not signed in never see it.
• Enlerim does not keep a history of when you were online and does not show a “last seen” time. Live connection data expires about 25 seconds after you disconnect; only your chosen status setting is saved.

• Approximate country: estimated from your IP address to choose regional content, as described above.
• Nearby places: only when you tap the location button, your device shares its precise position. It is sent to our server with that search and used to sort places from Enlerim's own database. It is not saved to your account and is not sent to Google or other providers, but the search address containing it can remain in our server logs for up to about 14 days.
• Shared location messages: saved with the message, as described under Messages.
• The Android app uses location only in the foreground, while you use one of these features. It does not use background location.

• Necessary cookies: your encrypted sign-in session cookie, short-lived security cookies used during sign-in, and a theme preference cookie.
• Local storage on your device: language and theme preferences, your quick list, app and notification device identifiers, dismissed permission prompts and recently used emojis.
• Enlerim does not use its own analytics or advertising cookies. On the website, Google's advertising code may set or read cookies; see Advertising.

Enlerim's website loads Google AdSense code. When it loads, Google receives technical data from your browser, such as your IP address, browser information and cookies, and may use it to show and measure ads under its own policies.

The Enlerim Android app does not load AdSense or any other advertising code, contains no advertising SDK and does not access the Android advertising ID. Enlerim does not receive advertising identifiers and does not sell your personal data.

How Google uses information from sites that use its services

• Our web server logs requests (IP address, time, address, user agent and referrer). Logs are rotated daily and kept for about 14 days.
• Application logs record errors and technical events and are kept for about 14 days.
• Rate limits that protect against abuse use your IP address or account only in memory.

• To create your account and run the features you use.
• To show your profile and content to others according to your choices.
• To deliver messages, calls, notifications and online status.
• To show regional and nearby content.
• To keep Enlerim secure, prevent abuse, review reports and enforce our rules.
• To find and fix problems.
• To answer messages you send us and to meet legal obligations.

We do not sell personal data and we do not use your messages for advertising.

• Google: Google Sign-In (sign-in data), Firebase Cloud Messaging (Android notification token and notification text), Gmail (delivers contact form messages to our inbox: your name, email address and message) and AdSense (see Advertising).
• Browser push services, such as those run by Google, Mozilla, Apple or Microsoft depending on your browser, deliver browser notifications.
• A hosting provider rents us the server where Enlerim's application, database, uploaded files and backups are stored.
• Content sources such as TMDB, RAWG, Open Library, Deezer, Ticketmaster and Google Places provide information about films, series, games, books, music, events and places. Our servers do not send your account data to them.
• Some images, music previews and videos are loaded by your browser directly from those services or from YouTube, so they receive standard request data such as your IP address. Ticket and event links can pass through affiliate tracking links.

• With other users, according to the features you use and the visibility you choose.
• With the service providers listed above, for the purposes described.
• When we are legally required to disclose it.

Enlerim does not sell personal data.

• The website, app traffic and calls use encrypted connections.
• Notification tokens are encrypted on our servers.
• Voice messages and message photos are available only to conversation participants.
• Access to our servers and backups is restricted.

No system is completely secure, but we work to protect your data.

• Account and profile: until you delete your account.
• Posts, comments, lists, ratings and favorites: until you delete them or your account.
• Messages and call history: until they are deleted or an account in the conversation is deleted.
• Temporary photo uploads that are never attached to a post expire after 45 minutes; expired files can stay on our servers until they are cleaned up or your account is deleted.
• Notification devices: until you sign out on that device, the token stops working or your account is deleted.
• Live online status data: about 25 seconds after you disconnect. Your status setting: until you change it or delete your account.
• Server and application logs: about 14 days.
• Database backups: daily backups for 14 days, weekly backups for 8 weeks and monthly backups for 6 months. Deleted data can remain in a backup until that backup expires.
• Contact form emails: kept in our inbox; there is no fixed deletion period.

• Edit or remove your profile details and photos.
• Delete your posts, comments, lists and messages.
• Choose whether your name appears on event reviews.
• Choose notification types and quiet hours.
• Set your online status to Appear offline.
• Block other users.
• Allow or deny camera, microphone, location and notification permissions in your device settings.
• Sign out, or delete your account.

Enlerim does not ask for your age. Signing in requires a Google account, which is subject to Google's own age rules. If you believe a child has given personal data to Enlerim, contact us and we will delete the account.

Enlerim is available worldwide. Our service providers, including Google, may process data in countries other than the one where you live.

We update this policy when Enlerim's features or data practices change. The date at the top of this page shows the latest update.