Last updated: 12 November 2026
1. Who we are
JoeviL (the website joevil.com and the JoeviL mobile app) is operated by EviLux, a business name registered in Ireland (CRO 776215), Leixlip, Co. Kildare, Ireland ("we", "us"). We are the controller of your personal data under the EU General Data Protection Regulation (GDPR) and the Irish Data Protection Acts 1988–2018.
Contact for any privacy question or request: support@joevil.com.
We have not appointed a Data Protection Officer: the law does not require one for a service of our size and type. Privacy questions are answered at the address above.
2. Who can use JoeviL
JoeviL is for adults only. You must be 18 or older to create an account. When you complete your profile you confirm that you are 18+, and we do not accept a birth year that makes you younger than 18. If we learn that an account belongs to someone under 18, we delete it.
3. What we collect and why
You can read most of JoeviL (country guides, ratings, passport and visa data) without an account. We collect personal data only when you sign in, use the community features, subscribe to JoeviL Pro or write to us.
3.1 Account and sign-in
JoeviL has no passwords. You sign in in one of three ways, and your account is identified by your verified e-mail address – whichever way you use, the same e-mail opens the same account.
| Data | How we handle it | Why | Legal basis |
|---|---|---|---|
| E-mail address | Stored encrypted (AES-256-GCM). For look-up we store a keyed fingerprint (HMAC) that cannot be reversed without our secret key. Never shown to other members. | Identify your account, sign you in, send you account and subscription e-mails and, unless you turn them off, e-mails about new messages (section 3.4) | Contract (Art. 6(1)(b)) |
| Sign-in link | A one-time link in an e-mail, valid for 15 minutes. We store only a hash of it and your encrypted e-mail; it is deleted when used or expired. | Password-free sign-in | Contract |
| 6-digit code | Sent in the same e-mail as a backup, valid for 10 minutes, at most 5 attempts. Only a hash is stored; it is deleted when used or expired. | Password-free sign-in | Contract |
| Sign-in with Google | Google confirms your e-mail address to us. We ask only for "openid" and "email" and receive only your verified e-mail address – not your name, photo, contacts or anything else. For the few minutes the sign-in takes we keep one-time security values (hashed or random) to protect it from misuse. | Password-free sign-in | Contract |
| Session | A random token is kept in a cookie (website) or in your phone's secure storage (app). On our side we store only a hash of it, with its creation time, last use and expiry. | Keep you signed in | Contract |
| 18+ confirmation | The time you confirmed you are 18 or older | Keep minors out | Legitimate interests (Art. 6(1)(f)) – protecting minors and members |
| Language and last visit | The language of your e-mails, and the day you last used JoeviL | Write to you in your language; count monthly active members (section 3.8) | Contract; legal obligation (Art. 6(1)(c)) |
Sessions last up to 400 days and are extended each time you use JoeviL on that device. A session ends when you choose "Sign out" (this device) or "Sign out everywhere" (all devices, for example after losing a phone), and all sessions are deleted when you delete your account.
When you use Google sign-in, Google processes the sign-in as an independent controller under its own privacy policy (policies.google.com/privacy) and knows that you signed in to JoeviL.
3.2 Profile
Name, birth year, gender (optional: woman, man or other), citizenship, country and city where you live (picked from a list of cities), languages, a short "about" text and what you are looking for (dating, friends, travel, language exchange, networking). In People you also choose whom you want to see (women, men or everyone); this choice works both ways – you are shown only to people whose choice includes you – and it is not shown to anyone.
- Who sees it: signed-in members see your name, age (calculated from your birth year – the birth year itself is not shown), gender if you gave it, citizenship, country, city, languages, "about", what you are looking for and your approved photos. People who are not signed in can see plans you publish, with your first name, citizenship and country only.
- Distance: People shows members from your city first, then from other cities by distance. Members see a rough distance between your city and theirs (to 10 km) – never an address.
- Why: to let members find each other and plans. Legal basis: contract.
- Please do not put sensitive information (health, religion, political views, sexual orientation, etc.) in your profile or messages. We do not ask for it.
3.2a People nearby (optional, app only)
Off unless you turn it on. When it is on, and only while the app is open, your phone sends its position to us.
- We snap it to a grid of about 5 km squares before storing it – the exact point never reaches our database. Other members never see your position – only a rough distance ("about N km", at least 5 km), and only if they also turned "People nearby" on; otherwise they see the distance between cities as above.
- The position is kept for at most 2 hours after the app last sent it, then erased automatically. "Stop sharing" erases it at once, and so does deleting your account.
- You can also refuse or withdraw location permission in your phone's settings at any time; the rest of JoeviL works the same.
- Why: to show people close to you first. Legal basis: consent (Art. 6(1)(a)), which you can withdraw at any time by turning it off.
3.3 Photos
You can add up to 10 profile photos.
- Location and camera data are removed twice: the site and app re-encode each photo before upload, and our server removes all remaining metadata (EXIF including GPS, XMP, comments) before storing it.
- Photos are stored in Cloudflare storage in our EU account (at the moment Cloudflare Workers KV, to be moved to Cloudflare R2 later) under a random name and are shown only to signed-in members; they are marked "noindex" so search engines and face-search crawlers do not index them. People you have blocked, or who blocked you, cannot see them.
- Automatic check and human review: before a photo is shown, an AI model checks it for nudity, sexual content, violence, weapons, drugs, hate symbols, identity documents or bank cards, and a child alone. For this check the photo is sent to our AI provider (see section 5). A rejected photo is not stored. If the AI cannot decide, a human moderator reviews the photo, and until then it is visible only to you. Moderators can also review and remove photos after a report. The check is run by Cloudflare Workers AI or, when we use it, Anthropic's Claude.
- Why: to show your profile and keep the community safe. Legal basis: contract (showing photos); legitimate interests (moderation and safety).
The automatic check does not have legal or similarly significant effects on you – a rejected photo is simply not published. If you think a photo was rejected by mistake, write to us and a person will look at it when you send it again.
3.3a Photo verification (optional)
Off until you start it yourself. If you pass, your profile shows a «✓ Photo verified» mark – it shows that your photos match the person who is in front of the camera now.
- How it works: only the front camera is switched on (you cannot upload a ready-made video or file). You put your face in the oval on the screen and hold still for about two seconds. Your phone checks on the spot that it is a live face and not a photo or a screen, using an anti-spoofing model, a liveness model and the small natural movements of a face. Only if it is not sure does it ask you to blink once. It then compares your face with your first (up to 3) approved profile photos.
- What happens on your device: the face-recognition code and its models are loaded from our own servers (about 11 MB the first time), with no request to any third-party service. The camera frames, the video and the numeric face template are created and used only in your browser's memory and are discarded when the check ends. Only one still selfie frame leaves your device, at the end (see the next point). For the comparison, your approved profile photos are loaded onto your device – the same way as when you just look at them.
- What the server receives and stores: your phone sends us the selfie frame (a JPEG; location and other metadata are removed on our server) and, as a hint for the person who looks at it, the phone's own numbers: the liveness scores, whether you blinked and the match percentage. The server never sets the mark from these numbers – a person decides. We keep the selfie in our photo storage only while your request waits for a decision and delete it right after the decision; if nobody decides, it is erased after 30 days. We do not store video or face vectors or templates. After the decision we keep for 30 days only the status of the request (approved or not, and the reason if the moderator wrote one) so that the app can show it to you. For an approved check we store only the date of the check, the method ("manual") and the time you gave consent. In addition, a technical record is created for each attempt: the time, a hash of a one-time code (valid for 3 minutes and usable once) and a short result code; these records are deleted after 30 days.
- Who sees it: the selfie is seen only by the JoeviL team who decide on the request: on a restricted admin page and in the team's private Telegram chat, where our bot sends the selfie and your main profile photo as a notice (Telegram processes it there as our provider, see the list of service providers). After the decision the bot deletes these messages (Telegram allows a bot to do it for 48 hours; anything older the team deletes by hand). Other members never see the selfie; signed-in members see only the «✓ Photo verified» mark itself in People, in plans and on your profile – not the date or the method.
- Biometric data and your consent: comparing your face with photos to confirm that it is the same person is, in our view, processing of biometric data – a special category under Art. 9 GDPR. We therefore do it only with your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR). You tick a box before every check and we store the time of your consent. The check is optional: JoeviL works the same without it, and declining limits no feature.
- How to withdraw consent and delete the result: at any time, tap «Remove the mark» (or «Withdraw the request» while it is waiting) on the check page or in your profile. This removes at once the mark, date, method and consent time, and erases a waiting request together with its selfie (and the copies in the team chat, as far as Telegram allows). Consent also ends, and all of this is deleted, when you delete your account. Withdrawal does not affect the lawfulness of processing before it. The technical records (see above) are erased automatically within 30 days at the latest and contain no images or face data.
- If you change your photos: any change to your photos (a new photo, a deletion, an approval by a moderator) removes the mark and the result at once; to get it back you need to pass the check again. The consent time stays until you withdraw it or delete your account.
- Limits: at most 3 starts of the check per person per day, 10 per IP address per day and 10 submissions per hour per person (the IP address is kept only as a hash, as described in section 3.7).
- What the mark does not mean: a person on our team compares your selfie with your profile photos; this is not an identity-document check and not a guarantee. We do not verify your name, age or identity – only that, in the team's judgement, the photos of your profile show the same person who took the selfie.
- Why: so that members can trust profiles more and meet fewer people using someone else's photos. Legal basis: explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR).
3.4 Plans, requests and chats
| Data | How we handle it | Legal basis |
|---|---|---|
| Plans you publish: type, title, description, country, city, area, date and time, number of places, languages | Visible to everyone, including people who are not signed in | Contract |
| Meeting point of a plan | Stored encrypted; shown only to the author and people the author accepted | Contract |
| Requests to join a plan, with an optional message, and the author's decision | The message is stored encrypted; visible to you and the plan author | Contract |
| Chat messages (plan chats; 1:1 chats, including first-message requests; city chats and meetup chats) | Stored encrypted at rest; visible only to the members of that chat | Contract |
| "Spark" game answers in 1:1 chats | Stored encrypted; the other person sees your answer only after both have answered | Contract |
| City chat (for example "JoeviL · Dublin") | Joining is your choice: nobody is added automatically, and you can join only the chat of the city in your profile. Members see the messages with each author's first name, and the number of members – not the list of members. A "topic of the day" question is pinned at the top. You can leave at any time. If you change the city in your profile, you leave the old city's chat and its meetup that is still gathering sign-ups (not yet confirmed). | Contract |
| Weekly city meetup: your sign-up and whether you chose "I can host" | Others in your city see only how many people have signed up. When 5 have signed up and one of them can host, the meetup is confirmed: a group chat opens only for the people signed up (at most 30), who see each other's first names, and the host's first name is shown with the meetup. Cancelling your sign-up also removes you from the meetup chat. | Contract |
Messages are encrypted on our servers, but they are not end-to-end encrypted: our system can decrypt them in order to show them to the chat members. Our moderation tools do not show message content. If you report someone, please write the relevant part of the conversation in the report.
E-mails about new messages. When someone writes to you in a 1:1 chat (including a first-message request) or a like becomes mutual, we send you an e-mail about it. It contains only the other person's first name and a link to your chats – never the text of the message. You get at most one such e-mail per chat every 6 hours, and none if you opened that chat in the last 15 minutes or if one of you has blocked the other; plan, city and meetup chats do not send these e-mails. For this we store when you last opened each chat and when we last e-mailed you about it. The e-mail is written in the language you last used on the site or in the app. These e-mails are on by default; you can turn them off in your profile at any time, and every such e-mail contains a link to that setting. Legal basis: legitimate interests (Art. 6(1)(f)) – letting you know about messages addressed to you; turning the e-mails off is your objection, and it takes effect at once.
3.4a Push notifications (optional)
Off until you allow them in your browser or phone. When you do, the browser or phone creates a push subscription and we store it with your account: the address of the subscription (endpoint) at your browser vendor's push service, the two encryption keys of that device, whether it is the website or the app, when it was created, when a notification was last delivered successfully and a counter of failed deliveries. We keep at most 5 devices per account (a new one replaces the oldest).
- When we send one: when someone writes to you in a 1:1 chat, a like becomes mutual, someone asks to join your plan, or the plan's author answers your request. The notification contains only the other person's first name and what happened (for example "Anna wrote to you") – never the text of a message or the title of a plan. Nothing is sent if one of you has blocked the other.
- Who delivers it: the notification is encrypted for your device (Web Push standard) and delivered through the push service of your browser or phone vendor – Google (Firebase Cloud Messaging), Mozilla, Apple or Microsoft. They see that a notification for your device was sent, and when, but cannot read it. They are independent controllers under their own privacy policies and may process data outside the EEA (section 6).
- How to turn it off: switch off "Push notifications" in your JoeviL settings (this applies to all your devices), or refuse or withdraw the permission in your browser's or phone's notification settings.
- When the subscription is deleted: when you sign out on that device, when you delete your account, when the push service reports that it is no longer valid (404 or 410), after 10 failed deliveries in a row, if the account is banned, and after 180 days without a successful delivery.
- The Android app (Firebase token): in the app we store, instead of a web subscription, the device's Firebase Cloud Messaging registration token (a random identifier that Google's Firebase issues to the app on your phone), with the same details as above (app or website, creation date, last successful delivery, failed deliveries) and under the same limit of 5 devices. We use it only to send you the notifications described above. Google (Firebase) delivers them for us as our service provider; unlike web push, these messages are not encrypted for your device by us, so Google can see the token and the short notification text (the first name and what happened). You can turn this off in the same ways: in JoeviL settings, in your phone's notification settings, or by signing out, which deletes the token. We also delete it when Firebase reports it as invalid, after 10 failed deliveries in a row, if the account is banned, when you delete your account, and after 180 days without a successful delivery.
- Why: to tell you about messages and answers addressed to you. Legal basis: consent (Art. 6(1)(a)), which you can withdraw at any time by turning notifications off.
3.5 Likes, blocks, reports and moderation
- Likes and passes – to show you new people and to open a chat when the like is mutual.
- Blocks – to hide you and the blocked person from each other everywhere and close your 1:1 chat.
- Reports – reason, optional text, the reported person and plan.
- Moderation decisions – warnings, 7-day blocks, bans and removed content, each with its reason, the time and the moderator, the number of warnings on the account, and the statement of reasons we send you by e-mail.
- Legal basis: contract (likes); legitimate interests and our legal obligations under the EU Digital Services Act (blocks, reports, moderation – Art. 6(1)(c) and (f)).
3.6 JoeviL Pro and the AI assistant
- Subscription status: the date until which your Pro access is paid, whether it will renew, the Stripe customer and subscription reference, and for purchases in the apps the store purchase record described below. These are set only from verified Stripe notifications or from what Apple's and Google's own servers report, never from your device.
- Payments on the website: handled by Stripe. You enter your card details on Stripe's page; we never receive or store your card data. We pass Stripe your account id and e-mail address; Stripe tells us whether the subscription is active and until when. Through Stripe's billing page you can change your plan or card, see invoices and cancel. Stripe acts as an independent controller for its own payment, tax, fraud-prevention and legal obligations – see stripe.com/privacy.
- In-app purchases: in the iPhone app JoeviL Pro is bought through the App Store, and in the Android app through Google Play. Apple or Google processes the payment as an independent controller under its own privacy policy; we never receive your card or payment details. When you buy, the app passes the store your JoeviL account id, so the purchase is linked to your account and to no other. We then ask Apple's or Google's servers about the purchase and keep only the purchase identifiers, the product (plan), the status (active, expired or ended early, for example after a refund) and the expiry date, so that Pro works for your account on the website and in the apps.
- One free trial per person: to give the 7-day free trial only once, we keep a keyed fingerprint of your normalized e-mail address (in lower case, without any "+tag", and for Gmail without dots, because Gmail ignores them) and the date. This record is kept for 3 years, also after your account is deleted.
- Renewal reminders: we e-mail you 3 days before every renewal, with the date and amount.
- AI assistant: your question (up to 600 characters) is sent to our AI provider together with your citizenship, the country and city you live in, the country you are asking about and our own country data. We do not send your name or e-mail address. We store the conversation: every question you ask and every answer you get is saved on our server in your account, encrypted with our data key (AES-256, kept separately from the database), and through the app or site it is readable only by your own account. We keep only the last 60 question-and-answer pairs; older ones are deleted automatically. You can delete the whole conversation at any time with the «Clear history» button, and it is deleted when you delete your account. Signing out does not delete it. To keep the context of the conversation, each question is sent together with the last 8 saved question-and-answer pairs to the same AI provider (Anthropic's Claude or Cloudflare Workers AI). On the website your browser also keeps a copy of the recent messages in its session storage until you close the tab. Reporting an answer: if you tap «Report this answer», that question and answer (and your optional note, up to 500 characters) are stored encrypted together with the report and shown, decrypted, to our moderators (administrators) so they can review it; nobody else sees them. They are kept as described for reports in section 7: until the report is closed and then for 12 months, also if you delete your account (the report is then no longer linked to you). We also keep a monthly count of questions and of AI tokens used per account, to apply the monthly limit and to measure costs. Members without Pro or Platinum can use the assistant only for questions about the app and for support, up to 10 messages a day; these are answered by a cheaper AI model of the same provider (Anthropic's Claude, or Cloudflare Workers AI as a fallback) and without web search. The assistant also helps with how the app works and, if you have a real problem, can prepare a support request (section 3.9a). Daily counters: to apply the daily limits and for fair use, we keep a count of your assistant messages for each UTC day, for 7 days, and a daily total of the estimated AI cost for the whole service (this total contains no personal data). If one account sends an unusually high number of messages in a day (more than 50), our team gets a notice with the account id only (no message content); this serves fair use and abuse prevention (legitimate interests).
- Legal basis: contract (Pro, assistant, limits, reminders); legal obligation (tax and accounting records); legitimate interests (preventing repeated free trials).
The assistant's answers are generated automatically and may be wrong. They are not legal, immigration or tax advice.
3.7 Security and abuse prevention
- Rate-limit records: to stop abuse (code-guessing, spam, mass reports) we count actions per account, per e-mail fingerprint or per IP address in short time windows. The IP address or e-mail is stored only as a hash, together with a counter and an expiry time.
- Blocked and banned accounts: while a 7-day block or a ban is in force we keep the e-mail fingerprint and the reason, so the same address cannot be used to get around it.
- Legal basis: legitimate interests (security of the service and of members).
3.8 Statistics
- We count key actions per day (for example "sign-ups: 12", "messages: 340"). These counters contain no personal data and cannot be linked to anyone.
- We count how many members in the EU are active each month (from the day of your last visit and your profile country), because the Digital Services Act requires us to give this number to the authorities on request. Only the totals are reported.
- We use Cloudflare Web Analytics to see how the site is used (pages viewed, referring site, browser and device type, country). It works without cookies and without storing anything on your device, and does not track you across sites or build a profile of you. Legal basis: legitimate interests (understanding and improving the site).
3.9 E-mails to support
When you write to support@joevil.com we use your message and e-mail address to answer you. Mail to this address is received by Cloudflare Email Routing and delivered to a mailbox hosted by Google. Legal basis: legitimate interests, or contract when it is about your account or subscription.
3.9a Support requests through the assistant
If you have a real problem that the assistant cannot solve, it can prepare a support request for you: a category (bug, payment, account, abuse or other), a short summary, details, the steps you took and what you expected. Nothing is sent to us until you tap «Send to support» in the app or on the site.
- What we store: the request (category, summary and details – the summary and details are stored encrypted with our data key, like the assistant conversation), your account id, the app platform and version, your language, the status (open or closed) and the dates.
- Where it goes: (1) by e-mail, sent through Resend, to our support mailbox – the e-mail contains the request, your public name, account id, language, platform and your e-mail address, so that we can answer you; (2) a short notice to our team's private Telegram chat that contains only the request number, category, summary, public name, account id, language and platform – never your e-mail address and never the conversation.
- Who can read it: only you, the person who sent it, and our administrators.
- How long: until the request is closed and then for 12 months; a request that was prepared but not sent is deleted after 24 hours; all your requests are deleted when you delete your account (copies in the support mailbox are kept like other support e-mails, see section 7).
- Limit: 5 requests a day per account. We answer by e-mail.
- Legal basis: contract (helping with your account and the service) and legitimate interests (fixing problems).
4. Cookies and device storage
- Session cookie `jv_s`: keeps you signed in. It is HttpOnly, sent only to joevil.com, and lasts up to 400 days (extended while you use JoeviL) or until you sign out.
- Google sign-in cookie `jv_oauth`: set only when you choose Google sign-in, used only by the sign-in page to check that the sign-in finishes in the same browser, and deleted after 10 minutes.
- Both cookies are strictly necessary for the service you ask for, so they do not need your consent.
- Device storage: the site stores some settings only in your browser (for example language, chosen passport, rating weights and plan filters). They never leave your device. The app keeps your session token in the phone's secure storage (Keychain / Keystore). The assistant's conversation is saved on our server (section 3.6); on the website your browser also keeps a copy of the recent messages in its session storage until you close the tab. If you turn on push notifications, your browser itself keeps the push subscription (section 3.4a).
- Our fonts are hosted on our own servers – your browser does not connect to a font provider.
- We use no advertising, tracking or social-media cookies and no third-party trackers. Cloudflare Web Analytics (section 3.8) is cookieless.
5. Who processes data for us
We do not sell your data and do not share it for advertising. We use these service providers, bound by data-processing agreements:
| Provider | What for | Where | Transfer safeguard |
|---|---|---|---|
| Cloudflare, Inc. | Hosting of the site and API, database, photo storage, network security, Web Analytics, e-mail routing for support mail; Workers AI for photo checks and the assistant when used | EU and other countries where Cloudflare operates | EU–US Data Privacy Framework (DPF); Standard Contractual Clauses (SCCs) as fallback |
| Anthropic (Claude API) | Photo checks and AI assistant answers, when we use Claude | USA | SCCs |
| Resend | Sending sign-in and subscription e-mails, e-mails about new messages and support-request notices to our team | E-mails are sent from the EU (Ireland); account data and sending logs are kept in the USA | SCCs and DPF |
| Telegram (Telegram FZ-LLC) | Notices to our team's private chat about new support requests (only the request number, category, summary, public name, account id, language and platform – no e-mail address and no conversation); and, for photo-check requests, your selfie, your main profile photo, your name, age and city (the bot deletes these messages after the decision) | Its servers in several countries | Telegram does not offer Standard Contractual Clauses, so we send only this minimum; photo-check images are sent only if you start the optional check with your explicit consent |
| Mailbox for support@joevil.com | USA and other countries | DPF and SCCs |
These are independent controllers, each responsible for its own processing:
| Company | What for | More information |
|---|---|---|
| Stripe | Payments and subscriptions on the website | stripe.com/privacy – Stripe, LLC participates in the DPF; SCCs where required |
| "Sign in with Google"; in-app purchases of JoeviL Pro in the Android app (Google Play) | policies.google.com/privacy | |
| Apple | In-app purchases of JoeviL Pro in the iPhone app (App Store) | apple.com/legal/privacy |
| Google (Firebase Cloud Messaging), Mozilla, Apple, Microsoft | Delivery of push notifications to your browser or phone (section 3.4a) | Their own privacy policies |
AI providers: depending on our configuration, a request goes either to Anthropic's Claude API or to Cloudflare Workers AI. Neither may use it to train AI models: Anthropic's Commercial Terms (section B) say Anthropic may not train models on customer content, and Cloudflare's Workers AI privacy terms say customer content processed by Workers AI is not used to train AI models.
We may also disclose data when the law requires it (for example a valid order from a court or An Garda Síochána), or to protect someone's life or safety, including reporting a suspected criminal offence threatening life or safety as required by the Digital Services Act.
6. Transfers outside the EU
Some providers are in the USA or may process data outside the EEA. We transfer data only with the safeguards listed in section 5: the EU–US Data Privacy Framework where the provider is certified, and otherwise the European Commission's Standard Contractual Clauses. In addition, e-mails, messages, notes attached to plan requests, meeting points and Spark answers are encrypted in our database with keys kept outside it. You can ask us for a copy of the safeguards at support@joevil.com.
7. How long we keep data
Expired and outdated records are removed by an automatic daily clean-up.
| Data | How long |
|---|---|
| Account, profile, photos, plans, requests, likes, blocks, Spark answers | Until you delete the photo/plan or your account. Accounts are not deleted for inactivity. |
| Photo-verification result (date, method) and the time of your consent | Until you remove the mark or delete your account; the mark and result are also removed when you change your photos (the consent time stays until you withdraw it or delete your account) |
| Photo-verification technical records (one-time code hash, time, result code; no images) | 30 days |
| Photo-check selfie and request | Deleted right after the decision (also from the team chat, as far as Telegram allows); if nobody decides, after 30 days. The decision (approved or not, and the reason) is kept for 30 days only, so that the app can show you the status |
| Your chat messages | Until you delete your account – then they are deleted for the other members too. Leaving a city or meetup chat does not delete what you wrote there. Messages in a meetup chat are deleted with the chat 90 days after the meetup day. |
| City chat and meetup memberships, meetup sign-ups, and when you last opened each chat and we last e-mailed you about it | Until you leave the chat, cancel your sign-up or delete your account; for a meetup, at the latest 90 days after the meetup day |
| Weekly meetup records (city, date, theme, status, links to the host and to the meetup chat) | 90 days after the meetup day, then deleted together with the meetup chat; until then the link to the host is removed when the host cancels the sign-up or deletes the account |
| Past plans | Deleted 90 days after the plan date |
| "People nearby" position | At most 2 hours after the last update; at once when you stop sharing |
| Sign-in links and codes | 15 and 10 minutes; deleted when used or expired |
| Google sign-in security values | At most 10 minutes; deleted when used or expired |
| Sessions | Up to 400 days after the last use; deleted on sign-out or account deletion |
| Push subscriptions (device address and keys) | Until you turn off notifications or sign out on that device, or delete your account; also when the push service rejects the address, after 10 failed deliveries in a row, or after 180 days without a successful delivery |
| Rate-limit records | Until the end of their time window (at most 24 hours) |
| Assistant conversation (your questions and the answers, encrypted) | The last 60 question-and-answer pairs; older ones are deleted automatically. All of it is deleted when you tap «Clear history» or delete your account. |
| Answers you report (question, answer and your note, encrypted) | Until the report is closed and then 12 months, also if you delete your account (then without the link to you); visible only to moderators |
| Assistant usage counters | 12 months |
| Daily assistant message counters (per account, per UTC day) | 7 days |
| Daily totals of estimated AI cost (whole service) | No personal data – kept without limit |
| Renewal-reminder records | 60 days (so a reminder is sent only once) |
| Free-trial record | 3 years after the trial, also after the account is deleted |
| Reports and moderation decisions | 12 months after the report, also if the account is deleted, so we can handle complaints and legal requests |
| Banned accounts | E-mail fingerprint and ban reason: as long as the ban is in force. Profile and photos: deleted 6 months after the ban, except content we have passed to law-enforcement authorities, which we keep as long as they require. |
| Support e-mails | 6 years after the last message (Irish limitation period) |
| Support requests (encrypted summary and details, category, platform, language, status) | Until closed and then 12 months; deleted at once with the account |
| Support requests prepared but not sent | 24 hours |
| App Store and Google Play purchase records | As long as your account exists; deleted with the account. Apple and Google keep their own billing records. |
| Billing and tax records | 6 years (Irish accounting and tax rules); most of them are held by Stripe, and for in-app purchases by Apple and Google |
| Daily statistics and monthly active-member totals | No personal data – kept without limit |
Deleting your account: in your profile you can delete your account at any time. Before deletion we warn you that a Pro subscription bought on the website will be cancelled automatically; a subscription bought through Google Play or the App Store must be cancelled in the store, and we show you how. Deletion immediately removes your account, profile, e-mail, sessions, photos (including the files), plans, requests, messages, likes, blocks, Spark answers, city chat and meetup memberships and sign-ups, App Store and Google Play purchase records, your assistant conversation and assistant counters. It also removes all your support requests (copies in the support mailbox are kept like other support e-mails). Only the records listed above as kept after deletion remain (reports and moderation decisions without the link to your account, the free-trial record, billing records and support e-mails). Push subscriptions of all your devices are removed as well.
8. Your rights
Under the GDPR you have the right to:
- access your data and get a copy;
- rectify wrong data – most of it you can edit yourself in your profile;
- erase your data – delete your account yourself or write to us;
- restrict processing in certain cases;
- data portability – receive the data you gave us in a machine-readable format;
- object to processing based on our legitimate interests;
- withdraw consent where processing is based on consent, without affecting earlier processing.
Write to support@joevil.com from the e-mail address of your account. We answer within one month (this can be extended by two months for complex requests, and we will tell you). We may ask you to confirm you own the account, for example by signing in.
You can also complain to the Data Protection Commission, 21 Fitzwilliam Square South, Dublin 2, D02 RD28, Ireland – www.dataprotection.ie – or to the supervisory authority in the EU country where you live or work.
9. Security
We protect your data with, among other measures: encryption in transit (HTTPS with HSTS); encryption at rest of e-mails, messages, notes attached to plan requests, meeting points and game answers, with keys kept outside the database; storing only hashes of session tokens, sign-in links and codes; no passwords that could leak; Google sign-in with signature, audience and one-time checks; random, non-guessable ids; access checks on every request; rate limits; strict browser security headers; metadata removed from photos, which are served only to signed-in members and excluded from search engines; and a minimal number of people with administrative access. No system is perfectly secure; if a breach is likely to put you at high risk, we will tell you without undue delay.
10. Automated decisions
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. The AI photo check only decides whether a photo is published (section 3.3). The «Photo verified» mark is set by a person on our team after looking at your selfie, not automatically; it has no legal effect and is optional (section 3.3a). The order of people and plans you see is based on simple rules (your country and city, whether a profile has photos, how new it is), not on profiling.
11. Changes
We will publish any change on this page with a new date. If a change is important, we will tell you by e-mail or in the app before it takes effect.
See also: Terms of Use · Community Rules · Digital Services Act information