Privacy Policy
1. Who processes the data and what this policy covers
The controller of personal data for ConvoyMeet is Dzemyanovich Aliaksandr, Viale John Fitzgerald Kennedy 169, 04100 Latina (LT), Italy; requests about personal data: info@convoymeet.com. ConvoyMeet is a mutual-help service for drivers with a map, statuses, chats, parking information and an SOS feature. This policy applies to the website convoymeet.com, the Telegram Mini App and the ConvoyMeet app for Android. The ConvoyMeet app for iOS (iPhone) is covered in section 13: unless that section says otherwise, what this policy says about the Android app also applies to the iOS app.
Role and contact. The person named above decides on the purposes and means of processing (controller, “titolare del trattamento”, Art. 4(7) GDPR) for all ConvoyMeet services, including ConvoyMeet Jobs. For any question about personal data write to info@convoymeet.com (subject “GDPR”); we may ask you to confirm that the request comes from the account holder.
ConvoyMeet is not an emergency service. If there is an immediate threat to life or health, contact your local emergency services (112 in the EU).
2. What data we receive
- Telegram and account: Telegram ID, username and name (first_name) when you sign in via Telegram; an internal account identifier and a service address used by Supabase Auth, which is not a user mailbox and is not used for mailings. We do not ask drivers for an email address to register in the Telegram Mini App. The data available to us from Telegram depends on what the platform passes on.
- Signing in to the Android app: with a Google account (Google Sign-In) or with an email address and a one-time code. When you sign in with Google, we receive from Google your verified email address, the permanent identifier of your Google account and your name if Google provides it (it becomes your profile name, which you can change). We do not store your email address in plain form — only its hash (SHA-256), which we use to find your profile the next time you sign in; the Google identifier is stored so that the same Google account always returns to the same profile. When you sign in with a code, the address is used to send you the email with the code; the code is stored only as a hash and is valid for 10 minutes.
- Android device: the technical Firebase Cloud Messaging (FCM) notification delivery token, the app build version, the time the token was registered and delivery results. Your sign-in session is stored on the device in Android’s protected storage. The app does not use the Advertising ID; it requests permissions for location (only while the app is in use), notifications, internet access and network state.
- Profile: your chosen name, languages of communication and of the interface, and, if filled in, the make and model of your truck; registration date, whether initial setup was completed, location and notification settings, time of last activity.
- Location: coordinates for statuses, SOS, parking search and route calculation, as well as derived data (search area, geographic cell, sometimes a city). Visibility details are in section 4.
- Messages and actions: texts of personal and parking chats and SOS chats, photos, SOS descriptions, contact requests, responses to SOS, blocks, favourite parkings, ratings, information about amenities, free-space reports and feedback.
- Places added by drivers: if you add a parking, a shop or a warning to the map, save places or shops as favourites, answer questions about a place, report an incident there or ask for a place to be corrected or removed, we store the place (coordinates, type and the details you entered), your account identifier as its author, and your answers, marks, favourites and a log of these actions. Other drivers see the place and summarised details about it, but not who added it. After an automatic location check, a new place may be sent to a moderator for manual review. Messages in the chat of such a place are handled like parking chat messages.
- Messages sent via “Contact us”: the text of your message and, if you choose to provide it, an email address for the reply. Providing an email address is optional. It is used to send you a reply and to contact you about your message, and it is not used for marketing mailings.
- Reports: the reason, an optional comment, the type of object (message, photo, driver or SOS request), a copy of the specific message or SOS description together with its photo if there was one, information about the chat/parking, participant identifiers, time, processing status and the moderator’s decision. After the author of a message deletes their account, a pseudonymous hash of their identifier (for Telegram, the Telegram ID) may remain, which cannot be reversed by ordinary viewing; such a hash may still be personal data.
- Usage statistics (since 1 October 2026; clarified on 19 October 2026): service events about actions in the service without their content — for example, “status turned on”, “message sent” (without text, photo or recipient), “SOS created” (without description or coordinates) — and the advertising campaign code of the link you came from. Separately, overall usage totals not linked to you: how many times per hour the app and its sections were opened, a parking filter was selected, parking cards and driver lists were opened, the tutorial was completed, SOS and driving-ban cards were opened, first-launch steps were passed, and the results of location permission requests and route calculations; technical error codes are counted the same way. These totals contain no account identifier, session or IP address — only the action, a value from a predefined list, client and platform type, build version, country (ISO code determined by the hosting provider from the request, without storing the IP address) and a number. Only with your consent (“Extended statistics” in Settings): the same interface events linked to your account (app opens, first-launch steps, parking cards viewed — only the parking's country, result of route calculation). Coordinates, texts, photos and information about whom you viewed are not included in statistics. Without consent, to count returning users, we keep for each account only the dates of the last two days on which the app was open on screen (no time, location or actions).
- Technical data: IP address, User-Agent, session and server log identifiers; localStorage data on the device needed for settings and a local chat cache. Some third-party resources receive your IP address when they are loaded.
3. Purposes and legal bases
Providing the service and performing the terms of use (Art. 6(1)(b) GDPR): creating the account and profile, showing the statuses you choose, contact requests, chats, SOS, parking features, storing your settings and deleting the account. Some data is required for the respective feature: without Telegram identification the Telegram Mini App is not available; without location the features that depend on it are not available.
Android app: signing in with Google or with an email code and delivering notifications through Firebase Cloud Messaging are necessary to operate your account and the features of the service (Art. 6(1)(b) GDPR). Notification permission is requested by Android; you can withdraw it in your phone settings and turn off notifications in the app settings.
Permission and, where applicable, consent (Art. 6(1)(a) GDPR): access to the device location is requested separately through the system mechanism of Telegram/Android/iOS. You yourself turn on statuses and SOS, which publish coordinates. The system GPS permission and the acknowledgement that you have read this policy are not the same action; the acknowledgement on its own does not replace consent where consent is required by law. The device permission can be withdrawn in its settings; a status that has already been published should also be turned off in the app.
Legitimate interests (Art. 6(1)(f) GDPR): preventing spam and abuse, keeping the service secure, limiting the frequency of requests and reports, handling reports, technical diagnostics and protecting users' rights. When relying on this basis we take into account the expected consequences for users and their rights; in the cases provided for by the GDPR you have the right to object.
Messages to us: the text of your message and any email address you voluntarily provide are processed to review your message, reply to it and contact you about it (legitimate interest in handling enquiries, Art. 6(1)(f) GDPR). You can also send a message without an email address; in that case we cannot reply to you by email.
Usage statistics: interface events linked to your account (“Extended statistics”) are collected only with your consent (Art. 6(1)(a) GDPR); you can give or withdraw it in Settings, and on withdrawal these events are deleted. Overall usage totals not linked to you and technical error codes are collected without consent on the basis of legitimate interests (Art. 6(1)(f) GDPR) — to keep the app working and improve it: they contain no identifiers, are not combined with account data and are used only for this service. Server-side service events about completed actions (without content) and the acquisition campaign code are also processed on the basis of legitimate interests — to understand whether the service is useful, find errors and evaluate acquisition channels. You may object to processing based on legitimate interests (see the section on your rights). No advertising profiles are built; the data is not sold or shared with advertising networks. The dates of the last two visit days are also processed on the basis of legitimate interest — to know how many drivers come back to the service; they are not used for advertising or for decisions about you. You can object at any time by writing to info@convoymeet.com: the dates will be deleted and your account excluded from this count. If you have declined “Extended statistics”, no visit dates are kept for your account.
Legal obligations (Art. 6(1)(c) GDPR): processing or retaining data where applicable law or a lawful request from a competent authority requires it. We do not use data for sale to advertisers and do not make solely automated decisions with legal or similarly significant effects.
4. Location: when exact coordinates are visible to others
Location is normally determined on the device. We do not build a travel history or a continuous route in our database: the relevant record stores the current or last point, not a sequence of all movements. However, the transfer of coordinates to external map and geo services when using certain features is described in section 8.
In the Android app, access to location is requested through the Android system dialog and is used only while the app is in use; the app does not request background location access. The rules on who can see your coordinates are the same as described below.
“Parked here” and “Looking for company”: while the status is on and has not expired, the exact coordinates may be seen by other signed-in drivers who share at least one selected language with you and are viewing the corresponding area of the map. There is no additional distance limit on visibility; the map area limits a specific request but does not mean that only the nearest drivers see you. The coordinate of such a status is the point where it was set and is not updated as you move normally.
“Looking for parking”: this status is not shown to other drivers as a normal point; the position and search area are used to find parkings and to check whether contact is possible. Contact: seeing a driver's card does not by itself guarantee the right to send a request; the app additionally checks the applicable contact conditions.
SOS: active SOS signals in the viewed area of the map are available to all signed-in users regardless of language. For the “Vehicle problem” and “Info” categories, exact updated coordinates, the description and the author's name may be shown. For an emergency SOS, the exact point of the incident and the city are shown, but not the author's name in the public card. The SOS chat and photos are available only to participants who have been granted access. An emergency SOS does not replace calling the emergency services.
To determine the country for an SOS, coordinates may be sent to BigDataCloud directly from the device. For routes and the search area, coordinates are sent to map services; the exact conditions depend on the feature used. If you share your location, other users may see or record it outside our control.
5. Communication, blocking and reports
A personal chat becomes available after a request provided for by the app has been sent and accepted. Depending on the feature, messages and the author's name are seen by the other person or by the participants of the respective parking/SOS chat. If Telegram push notifications are on and the recipient is not in the app, Telegram may receive the sender's name and the first 200 characters of the message. Notifications already delivered cannot be guaranteed to be removed from the recipient's Telegram.
In the Android app, notifications are delivered via Firebase Cloud Messaging (Google): for delivery the service receives the device token and the same short notification text — the sender’s name and up to 200 characters of the first line of the message. A notification is shown only for the account signed in on that device; when you sign out, the token is deleted.
In a personal chat you can permanently block the other person. After blocking, new personal messages, contact requests and related personal push notifications between this pair are prohibited in both directions; there is no separate unblock function. Blocking does not deprive the person of access to shared parking chats and SOS. The technical blocking record is kept as long as the corresponding account exists.
You can report someone else’s message (including one with a photo) in a private chat, a parking chat or an SOS chat, a driver in a private chat, and someone else’s SOS request: choose a reason and optionally add a comment. The report is stored together with a copy of the specific message or SOS description and its photo if there was one; only authorised ConvoyMeet moderators see it in a protected admin panel, and their actions are logged. The author is not told about the report, and no one else’s personal data is passed to the person who reported. Submitting a report does not by itself delete the message or block the author; after review a moderator may delete the message. The frequency of reports is limited to prevent abuse. A notification about each new report is sent to the support address — only its number, type, reason and time, without chat text or photos; storing the report does not depend on whether the email is sent.
6. Retention periods
Statuses: until turned off or until the chosen period expires; expired records are normally deleted within 5 minutes. The interface limits the maximum duration of regular statuses to 45 hours, and of parking search to 60 minutes. SOS: up to 3 hours for an emergency SOS or 6 hours for the others, and may be closed earlier; after closing it is deleted after approximately 30 minutes, taking periodic clean-up into account. Free-space reports: about 5 hours.
Messages: 7 days from sending; the daily clean-up means that in practice they are kept for up to about 8 days; SOS chat messages may be deleted earlier together with the SOS. Photos: deleted when no message or SOS refers to them any more; uploaded but unattached photos are cleaned up after approximately 15 minutes. A photo from a message that has been reported is kept together with the report. Files are deleted asynchronously and may require a retry.
Contact requests: 7 days after activity ends. Feedback and reports: up to 12 months. Unused sign-in sessions: deleted if not refreshed for 30 days; the service log of cron jobs: 14 days. Blocks, ratings, favourites and the profile: until the account is deleted or another deletion provided for. Automatic deletion of inactive accounts is not provided for as of this version. Request-rate limit counters (account number, hour or day, request type, count) — no longer than 3 days; records of exceeded limits — no longer than 30 days.
Signing in to the Android app: the email address hash and the Google account identifier — until the account is deleted; one-time sign-in codes — up to 2 days; the notification token — until you sign out on the device or delete the account; invalid tokens are disabled.
The reply email address is stored together with the message and deleted together with it: when the retention period for messages expires or when the account is deleted. The notification about a new message (its text and the email address, if provided) and any further correspondence about it are kept in our mailbox at Aruba; these emails are not deleted automatically together with the database record — we will delete them on request to info@convoymeet.com.
Usage statistics: interface events linked to an account are kept for up to 90 days; server-side service events and the daily activity summary used to calculate metrics (without the content of actions) for up to 400 days; overall usage totals not linked to you for up to 25 months. A protective request-rate counter is kept for no more than 2 hours as an irreversible code. After these periods only aggregated figures without direct identifiers remain (for example, the number of active users per day). The account's statistics card (acquisition source and date, registration and first-activity dates, last client, build version and country at sign-in) is kept while the account exists. When an account is deleted, statistics are unlinked from it: the account identifier is replaced with a random key and the mapping is not stored anywhere. The log of administrator actions in the control panel is kept for 2 years. Dates of the last two visit days — no longer than 30 days.
Places added by drivers stay on the map as shared information until they are withdrawn, hidden or removed after review; your favourites, answers, marks and the log of your actions with places are kept until you delete them or your account. E-mails sent to info@convoymeet.com or support@convoymeet.com are copied into our protected control panel for no longer than 30 days; the mailbox itself is covered above.
Retention periods of logs and backups of infrastructure providers depend on their actual settings and rules; the exact periods as of the date of this version require separate confirmation. In exceptional cases certain data may be kept longer if the law or the justified resolution of a dispute requires it.
7. Account deletion and residual data
You can delete your account in the ConvoyMeet app: Profile → Account → “Delete account”, and confirm the action. The current server procedure deletes the profile, related statuses, chats, SOS, requests, blocks, ratings, favourites, sign-in sessions and related photos, taking asynchronous clean-up into account. Opening the Mini App again after deletion can create a new account only in accordance with the current registration sequence.
For Android app accounts, the email address hash, the link to the Google account and the notification tokens are deleted together with the account. The account data on the device and the sign-in session in protected storage are also cleared.
Your favourites, answers, marks and incident reports relating to places and the log of your actions with places are deleted together with the account. Places you added remain on the map as shared parking information but are no longer linked to your account.
Messages sent via “Contact us” are deleted together with the account, including the reply email address provided. Emails about such messages in our mailbox are covered in section 6.
After deletion the following may remain: push notifications previously delivered in the recipients' Telegram; the chat cache on other users' devices; short-lived technical responses of server calls (up to 6 hours in the previously checked configuration); providers' logs and backups until their actual periods expire. Reports you have submitted are deleted together with your account. Reports about your messages may be kept for up to 12 months with a copy of the message and a pseudonymous hash of your Telegram ID without a direct link to the deleted profile. The hash is not fully anonymous.
If you have no access to the app or have difficulties with deletion, write to info@convoymeet.com. We may ask for reasonable confirmation that the request comes from the account owner. Public instructions: convoymeet.com/delete-account.
8. Recipients of data and international transfers
ConvoyMeet uses: Telegram (Mini App sign-in, bot and push); Supabase (database, authentication, files, server functions; the main database region is Frankfurt); Vercel (hosting of the Mini App/website and server functions for routing); OpenRouteService/HeiGIT (calculation of routes and search areas); BigDataCloud (reverse geocoding); OpenFreeMap and Esri (map layers); Google Fonts, unpkg and jsDelivr (loading fonts and software libraries). If you choose an external route, destination data may be passed to Google Maps or Apple Maps on your action.
Google — Firebase Cloud Messaging (delivering notifications in the Android app) and Google Sign-In (signing in with a Google account). SendPulse — sending emails with one-time sign-in codes: the service receives the email address the message is sent to and the message with the code itself.
Aruba (Italy) — the email service for the convoymeet.com domain. Notifications about new messages sent through “Contact us” (with their content and the reply email address, if provided) and about new reports (only number, type, reason and time) are delivered to our service mailbox through Aruba’s SMTP server; we also use this service to reply to emails.
OpenAI (USA) — an AI assistant used only by the operator in the protected control panel to sort e-mails sent to our addresses, summarise them and prepare draft replies, and to analyse aggregated service statistics. For this it receives the sender’s name, the subject and the text of the e-mail (up to 3,000 characters, with e-mail addresses and phone numbers masked). The legal basis is our legitimate interest in handling enquiries (Art. 6(1)(f) GDPR). Every reply is checked and sent by the operator; no decisions about you are taken automatically. Under OpenAI’s API terms, this data is not used to train its models by default.
Information may be processed outside the European Economic Area, including by infrastructure and providers with global networks. Vercel server functions for routing run in the Frankfurt region (fra1). Even a European region for the main servers does not rule out international transfers through Telegram, global CDNs, support and subcontractors. For transfers falling under Chapter V GDPR, valid legal mechanisms must apply (for example, an adequacy decision or standard contractual clauses, where applicable). We do not claim the existence of unconfirmed signed agreements. You can request information about the applicable safeguards at info@convoymeet.com.
9. Cookies, local storage and external resources
The Telegram Mini App does not use advertising pixels or third-party analytics services. The device's localStorage is used for interface settings, onboarding and a cache of recent messages; it also stores your usage-statistics choice and, if you consented before registering, a random anonymous identifier that is deleted once the account is created. Without consent no such identifier is created. The cache may remain on the device until it is cleared by the app, the browser/WebView or the user; server-side deletion does not guarantee deletion of copies on other people's devices. The public website uses the functional cookie cm_lang for about one year and localStorage cm-site-lang to remember the chosen language; there are no analytics trackers on the website. The administrators' control panel keeps the login session only until the browser tab is closed. External fonts, libraries and maps may receive your IP address and technical information when they load.
The Android app contains no advertising SDKs and no third-party analytics; Firebase Cloud Messaging is used only to deliver notifications. Interface settings and the cache are stored in the app’s data on the device. If new SDKs, analytics, advertising identifiers or other ways of storing data are introduced in the apps, the policy and the app store disclosures will be updated before they are used.
10. Security and your rights
We use access control to the database, authorization checks, rate limiting, time-limited links to photos and removal of unnecessary image metadata in the updated client. However, transmission of data over the internet and via other users' devices cannot be absolutely secure. Do not publish in chats and SOS information that you do not want to disclose to the respective participants.
In the cases and to the extent provided for by the GDPR, you have the right to request access to your data, rectification, erasure, restriction of processing, data portability, to object to processing based on legitimate interest, and to withdraw consent where it is the legal basis. Withdrawal of consent does not affect the lawfulness of processing before the withdrawal. Send requests, including requests for a copy of your data, to info@convoymeet.com; identity verification may be required to protect the account. We reply within the periods set by applicable law, usually within one month, with extensions permitted by law.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular the Garante per la protezione dei dati personali (Italy), or the competent authority of the country of your habitual residence, place of work or of the alleged infringement. Garante contact: www.garanteprivacy.it.
11. Children, changes to the policy and contact
ConvoyMeet is intended for drivers, not for children. If we become aware that a child's personal data has been obtained without the necessary legal basis, we will consider a request to delete it. If the ways of processing change significantly, we will update the policy and the version date and, where necessary, notify users or ask for separate consent. The current version is published at convoymeet.com/privacy. Questions about personal data: info@convoymeet.com.
12. ConvoyMeet Jobs: job ads and the employer dashboard
ConvoyMeet Jobs is a platform where employers themselves publish their own job ads for drivers. ConvoyMeet does not search for or select staff, does not collect CVs or applications and does not take part in hiring: drivers contact the employer directly using the contacts in the ad. The controller is the same as in section 1.
- Employers: work e-mail for sign-in with a one-time code (the code is stored only as a hash and is valid for 10 minutes), dashboard language, company details (name, country and registration number, type — direct employer or agency, and for agencies the details of their authorisation), representative and position, phone, e-mail, website, bases, job ads with contacts, acceptance of the rules version, moderation history and the activity log.
- Drivers: Jobs does not collect CVs, documents or applications. When ads are viewed, the server increases anonymous counts of impressions, opens and contact taps per day and channel; a temporary key, deleted after 2 days, prevents inflated counts. The employer sees only these totals.
- Reports: reason, optional text, channel, the reporter’s account ID if signed in and — only if provided — an e-mail address for the confirmation of receipt and the decision. The reporter’s identity and e-mail are not disclosed to the employer.
Legal bases: performance of the service terms (Art. 6(1)(b) GDPR) — dashboard, publishing and showing ads, service e-mails; legitimate interest (Art. 6(1)(f)) — company checks, moderation, fraud prevention, handling reports and anonymous statistics; legal obligations (Art. 6(1)(c)) where required by law.
Publicity: job contacts are published on the website and in the ConvoyMeet apps for Android and Telegram and may appear in search engines — the company provides and chooses them. Do not put personal data into an ad that should not be public.
Retention in Jobs (instead of the general periods in section 6): an unused draft — 90 days after its last change; a closed, expired or withdrawn job — 90 days after closing or expiry the contacts and the address are deleted and an anonymised record remains for the moderation history; a decided report — 90 days after the final decision the text, the link to the reporter and the e-mail are deleted, the reason and the decision remain; notification e-mails — removed from the sending queue after 90 days; the moderation and activity log — up to 12 months; active employer accounts and ads — as long as they are needed to provide the service. In a dispute, a suspected fraud or where the law requires it, only the necessary data are kept longer, for a documented reason and a limited period. Anonymous statistics without personal data may be kept longer.
Your requests: write to info@convoymeet.com from the company’s work e-mail (subject “GDPR”). We check that the request comes from the account holder, reply within one month (in complex cases the period may be extended by two further months, with notice) and record the request and the reply. On an erasure request we close the ads and delete or anonymise the personal data; the company name, country and registration number and moderation decisions without personal data may be kept where needed to prevent fraud and repeated violations or for legal claims. Rights: access, rectification (the company sees and edits most data in the dashboard), erasure, restriction, objection and portability; you may also complain to the Garante per la protezione dei dati personali.
Recipients: Supabase (database, sign-in, server functions; Frankfurt region), Vercel (website and dashboard), SendPulse (sending sign-in codes and Jobs e-mails, including e-mails to reporters), Aruba (our mailbox that receives notifications and replies).
Browser storage: the dashboard stores in the browser the sign-in session, the chosen language and an unsent copy of the job form (deleted on sign-out); the Jobs catalogue remembers the chosen filters on the device. These are strictly necessary and functional data; there are no advertising or analytics cookies in Jobs. The fonts of the Jobs pages and of the dashboard are loaded from our own server.
13. ConvoyMeet app for iOS (iPhone)
The iOS app works like the Android app: the same servers, the same account and the same functions. Differences:
- Signing in: with Apple (Sign in with Apple), with a Google account or with an email address and a one-time code. From Apple we receive a permanent identifier of your Apple account for ConvoyMeet, a verified email address — your own or a private relay address of Apple’s “Hide My Email” service, as you choose — and, at the first sign-in only, your first name if you choose to share it. As with Google, we store only the hash (SHA-256) of the email address and the Apple identifier, so that the same Apple account always returns to the same profile.
- Notifications: on iPhone, Firebase Cloud Messaging (Google) delivers notifications through the Apple Push Notification service (APNs). For this the device receives a notification token, which we store like the Android token (with the build version and the registration time). Notifications are sent only if you allow them in iOS; you can turn them off in the iOS settings at any time.
- Storage on the device: the sign-in session is stored in the iOS Keychain; settings and the local chat cache are stored in the app’s own storage. The app contains no advertising SDKs and no third-party analytics, does not use the advertising identifier (IDFA) and does not track you across apps and websites of other companies.
- Permissions: location — only while the app is in use; the app does not request background location. Your position becomes visible to other drivers only when you turn on a status or SOS yourself (section 4). Notifications — see above. Camera — only when you choose to take a photo for a chat or an SOS request. Adding to the photo library — only when you tap “Save”.
- Account deletion: Profile → Account → “Delete account”, as in the Android app (section 7). Together with the account we delete the email address hash, the link to the Apple or Google account and the notification tokens; the session is removed from the Keychain. If you signed in with Apple, we also revoke ConvoyMeet’s Sign in with Apple authorization through Apple’s service; you can check this in your Apple Account settings (“Sign in with Apple”).
- Recipients: in addition to section 8 — Apple (Sign in with Apple, APNs and distribution of the app through the App Store). Apple processes this data under its own privacy policy.
Version date: 14 November 2026. Contact: info@convoymeet.com.