Privacy Policy
This policy explains how Kontagram processes personal information through its website and Android and iOS applications, including account, vehicle QR, social and notification features.
Service operator: Mirilham Həsənov, an individual based in Azerbaijan, operating under the Incitel name.
Privacy and support contact: [email protected].
Kontagram is intended for people aged 13 and over. You can request account deletion in account settings or through our account deletion page, without reinstalling the app.
1. Information we process
- Account information: email address, username, account identifiers, password verification data, verification and recovery records, account creation and closure dates, active sessions, and the version and time of your terms acceptance. Passwords are stored as salted hashes, not readable passwords.
- Optional Google sign-in: if you choose it, we receive your Google account identifier, email address and verification status to create or access your Kontagram account. We do not request your Google password, contacts, files or profile photos. Google access and refresh tokens are not retained.
- Optional Apple sign-in on iPhone: we receive an Apple account identifier and a verified email address, which can be an Apple private relay address if you choose Hide My Email. We do not request your Apple password or full name. An Apple refresh token is encrypted on our server so that we can revoke the connection when your Kontagram account is deleted. Matching email addresses alone do not cause accounts to be merged.
- Profile and content: the optional display name, biography, profile photo and banner you provide; vehicle names, descriptions, photos and QR identifiers; posts, photos, captions, comments, replies and mentions.
- Social and safety activity: follows, likes, blocks, reports, report descriptions and evidence, moderation decisions and related security events. User searches and mention suggestions send your search query to our service to find matching accounts.
- Vehicle contact requests: the selected reason, vehicle and participants, request time, delivery status, response and expiry. A signed-in sender's identity can be shown to the vehicle owner. Guest requests use a guest identifier and are presented as guest requests. These requests are not audio or video calls.
- Device and notification information: a randomly generated installation identifier, platform, language, last activity, notification preferences, push delivery tokens and browser push subscription details. Our backend stores encrypted Expo push tokens linked to your account and device. Firebase processes installation identifiers and technical information needed for Android notification delivery.
- Approximate location and email events: Cloudflare processes your IP address and IP-derived country information. Brevo records delivery, opening and link-click events associated with transactional email recipients, including events generated by email privacy proxies. These measurements do not always establish that you personally opened a message.
- Network and support information: connection information such as IP addresses is processed to deliver and secure the service. Our application uses protected derived values for request limiting; infrastructure providers may maintain their own network and security logs. We process notification delivery and failure records to operate and troubleshoot the service. Local diagnostic records stay on your device unless you choose to share them. If you contact support, we receive your email and the information or diagnostics you include.
We do not request your device's contacts, precise GPS location, microphone access, or telephone/SMS history for these features. Photo selection gives us the image you choose to upload, not general access to your photo library. Uploaded images are re-encoded without the original EXIF/GPS metadata; anything visible in the image itself remains part of your content.
2. Why we use this information
We use information to create and secure accounts, verify email addresses, recover access, display profiles and content, deliver vehicle requests and social notifications, operate social features, respond to support requests, investigate abuse and enforce service rules.
Where applicable law requires a legal basis, processing is based on providing the service you request, our legitimate interests in operating and protecting it, compliance with legal obligations, or consent where required. You may withdraw consent for optional processing without affecting earlier lawful processing. Disabling optional notifications does not delete your account.
Network traffic and transactional email event measurements help us monitor service operation and email delivery. The current service does not use Firebase Analytics, Crashlytics, BigQuery exports, AdMob or Google Ads integration, and does not build targeted advertising profiles. This does not disable Cloudflare traffic measurements or Brevo email tracking.
3. What other people can see
Your published username, display name, biography, profile images, vehicle information, posts and comments can be visible to other users and, where public pages allow it, people without an account. Mentions link to the mentioned profile. Follow and like information is shown according to the service's visibility rules.
Your email address, password verification data, session credentials, push tokens and private reports are not published as profile information. Authorized administrators can access information needed for support, security and moderation. Vehicle request details are available to the relevant participants and authorized administrators.
Follow notifications can contain the follower's display name or username. Comment notifications use general text rather than the comment itself. Vehicle request alerts include the request reason; the app retrieves further request details from our backend. Alerts may appear on a device's lock screen according to its settings. Other people may copy or capture content you make public; deleting it from Kontagram does not automatically erase independently saved copies.
4. Service providers and other disclosures
Information is processed by the providers needed to operate the features you use:
- Cloudflare handles website/API traffic, IP addresses, IP-derived country, requested paths, traffic measurements and security events. We can view individual IP addresses in its security tools. Our backend uses derived IP values for rate limiting, not a stored country profile. Cloudflare also processes network data for its own security and service purposes under its policy.
- Brevo receives your email address, our sender details, message subject and content, including the verification or password-reset link, and a delivery job reference. Opening and click tracking is enabled. Our backend does not additionally send your username, display name or IP address; tracking requests from email software can separately disclose connection information to Brevo.
- Expo Push Service receives the Expo push token, notification payload and delivery information, then routes Android notifications through Google Firebase Cloud Messaging and iOS notifications through Apple Push Notification service. Payloads include the identifiers and request or social notification details needed to deliver and open the relevant screen. EAS build/distribution tools are separate from this runtime notification service.
- Google processes sign-in requests when you choose Google sign-in. Your browser communicates with Google, and our backend verifies the resulting identity before creating a Kontagram session.
- Your browser's push provider handles subscription and delivery information when you enable web push. Platform operators, including Google Play and Apple, may process their own installation, diagnostic or service information under their policies.
We may disclose necessary information in response to a valid legal requirement, to protect users and the service, or at your request. We do not publish private information merely because someone requests it.
Providers may process information outside Azerbaijan and your country of residence. The applicable location, safeguards and retention depend on the provider and service. Contact us for information about the arrangements relevant to your request; this policy does not imply that all processing takes place in one country.
5. Cookies, local storage and permissions
The website uses session cookies for sign-in and security. Browser storage holds settings such as text size, installation identifiers and notification preferences. Mobile devices store session credentials using operating-system secure storage and retain local preferences and temporary files needed for the app. Guest access information allows a guest to view their own request's response.
Google sign-in uses a short-lived security cookie and a temporary verification value held in your browser tab or mobile app. Sign-in transactions expire after 10 minutes. Google-only accounts can confirm deletion through Google instead of a Kontagram password; you can also set a Kontagram password through verified email recovery. Deleting your Kontagram account does not delete your Google account. The Google account identifier is removed with ordinary account data and is not copied into the limited security archive.
Deleting your Kontagram account does not automatically remove the connection shown in your Google account or Google's own records. You can manage that connection in Google account settings; removing it there does not submit a Kontagram deletion request.
If you choose Apple sign-in, Apple processes the sign-in request and, if selected, forwards service email through its private relay. An Apple-only account can be deleted in the iPhone app by confirming again with Apple. To use the website, first reset a Kontagram password using the account email shown in Settings. Deleting Kontagram does not delete your Apple Account. We queue revocation of the encrypted Apple token when the account closes and erase that token after Apple confirms success; outages are retried. A non-readable digest of the Apple identifier remains for up to ten minutes after success to reject old login attempts, then is cleaned up by the running service. Apple identifiers and tokens are not copied into the limited security archive.
Mobile sign-in sessions last up to 180 days and are renewed when the app refreshes the session during use. Web sessions last 30 days. Short-lived access credentials are renewed automatically. Signing out, resetting a password, deleting an account or revoking a session can end access earlier. A valid session and enabled device registration are needed to receive account notifications.
You can control notifications and photo permissions in device/browser settings. Android full-screen request alerts require the applicable special access. Without it, standard notifications may still be available if notification permission is enabled. Clearing browser storage or uninstalling the app does not itself submit an account deletion request.
6. Retention and deletion
While your account is active, we keep the information needed to provide your account, content and related features. Updating a normal profile or vehicle text field does not create a separate history of its old values, except where report evidence must be preserved.
- Ordinary deletion — 72 hours: deleting an account immediately closes access, revokes sessions and QR links, and hides its content. Ordinary account data and files are scheduled for permanent deletion after 72 hours. Deleted posts, comments, vehicles and replaced images follow the same period from their first deletion/replacement; later account deletion does not restart an earlier deadline.
- Replies: when a deleted comment has replies from others, its text and author link are removed and a “Deleted comment” placeholder may remain to preserve those replies. Deleting an entire post removes its comments too.
- Limited security archive — 90 days: separately restricted records retain the current email at account closure, account identifiers and dates, and necessary vehicle/QR, request, security and moderation events. This supports abuse investigations, disputes and support relating to the closed account. The period starts at account closure, not when the 72-hour cleanup finishes. Password hashes, session/push tokens, ordinary images, biographies and comment text are not transferred to this archive.
- Banned accounts: access is closed and the username is released. Account data is kept for a 90-day support appeal period. On expiry, ordinary data is deleted and the limited archive period of a further 90 days begins. A verified request for earlier deletion starts the 72-hour deletion process.
- Reports: necessary evidence of reported content is retained until the last relevant open report is resolved. Post/comment evidence reflects the content at the time of reporting. An account report preserves the reported username and stable account identifier. Deleted content remains unavailable publicly. Once review ends, evidence is cleared when its original deletion deadline has passed, or when that deadline is reached.
- Legal preservation: a documented legal proceeding or valid authority requirement may extend retention of necessary limited archive records until that need ends. This does not automatically preserve ordinary photos, biographies or comments. Releasing the hold does not restart the original archive period.
- Backups and interruptions: managed backups under our control have a maximum lifetime of 72 hours and are removed earlier when required by a deletion deadline. Technical outages can delay processing; overdue cleanup resumes when service is restored. Restoring a backup must respect current deletion decisions.
Brevo transactional logs are configured for one month; email previews are not retained. Cloudflare's dashboard currently shows approximately 30 days of analytics history; this visibility period is not a deletion deadline for every provider record.
Signing out disables the backend notification registration without immediately erasing its stored token. Account deletion schedules that record for the ordinary cleanup period. It does not automatically delete Expo/Firebase installation records. Expo retains push tokens to provide delivery and says notification content is kept only as needed for forwarding. Provider identifiers and operational records follow the provider's separate retention and deletion procedures, not our 72-hour database deadline.
Support correspondence and providers' own delivery, security and operational records are separate from the account database. Their retention depends on resolving the request, security needs, applicable requirements and the provider's processing arrangements; they are not automatically erased by our database cleanup. Contact us to include these records in a deletion request. We handle requests concerning providers processing data for us through the relevant provider mechanisms.
7. Your choices and requests
You can edit available profile fields, delete your posts/comments, manage notification preferences, block or report users and review active sessions. To delete an account, open Settings → Account actions → Delete account and confirm with your Kontagram password or, for a Google-only account, fresh Google verification. Alternatively, use our web deletion instructions. If you cannot sign in, recover access or contact support.
Depending on applicable law, you may request access, correction, deletion, a copy of your information, restriction of processing, or object to certain processing. Send privacy requests to [email protected]. We may request proportionate information to verify your identity. Never email your password or one-time verification code. We respond within applicable legal time limits and explain any justified retention or refusal. You may also complain to the relevant data protection authority where applicable.
8. Security
We use HTTPS for service connections, salted password hashing, access controls and restricted administrative access. Certain credentials are encrypted or stored as protected digests. These measures do not mean that all stored data is encrypted or that any system is completely secure. Please protect your account and report suspected unauthorized access to support.
9. Age and young users
Kontagram is intended for people aged 13 and over and is not directed at children under 13. Where local law requires a higher age or parental authorization, those requirements apply. If you believe an underage person has provided information contrary to these requirements, contact us so we can investigate and take appropriate action, including deletion where required. A 13+ audience does not remove our responsibility to protect young users.
10. Changes and contact
We will update this page and its date when our practices change. Material changes will be communicated as required, and any necessary new consent will be requested separately. Reading this policy or continuing to use the service is not a blanket consent to unrelated processing.
Contact: Mirilham Həsənov, Incitel, Azerbaijan — [email protected].