Privacy Policy
This Privacy Policy explains what personal data PARTIMO collects, how we use it, and your rights regarding your data.
Effective date: November 9, 2026
Data Controller
The data controller responsible for your personal data is:
CLAYPORT Ltd
Company ID (EIK): 208952670
11 Baucher St., entrance B, 4002 Plovdiv, Bulgaria
office@partimo.appBulgaria, European Union
What data we collect
We collect only the data necessary to provide the app's core functionality.
Account data
- Email address (required for sign-up and login)
- Password (stored securely hashed; never visible to us or other users)
Profile data
- Display name (required: you cannot take part in gatherings without one; it need not be your real name)
- Profile photo
- Gender (optional; not shown publicly)
- Year of birth (optional; not shown publicly; used to check that you are 18+ and to order gatherings in your feed, and the host sees your age in full years when you apply to their gathering)
- Bio text (optional)
- Interests / gathering tags (optional)
- City (optional)
Gathering data (created through your use of the app)
- Gatherings you host (title, description, date, location, category)
- Join requests you send or receive
- Chat messages within gathering groups
- Ratings you give or receive after gatherings
- Likes: events, places, landmarks and gatherings you marked with a heart (what and when)
- Votes in the polls of gatherings you take part in
- Attendance votes: after a gathering you mark whether the other participants came, and each person's attendance result is computed from them
Other data from using the app
- Connections: the connection requests you send or receive, which two people are Connections, and when you last had contact
- Direct messages between Connections (text up to 2000 characters)
- Photos: up to 6 photos in your profile gallery and photos added to gatherings (with an optional caption)
- Bug reports and suggestions from Settings: your text, optional screenshots, device data (on the web: browser, window size, language) and the last error, if there is one
Technical data
- Push notification tokens (so we can send you notifications about your gatherings)
- Timestamps of when you accepted the Terms of Use and Privacy Policy
How we use your data
- Authentication, login, and account security
- Creating and displaying gatherings
- Processing join requests between users
- Enabling group chat within gatherings
- Post-gathering ratings and trust/reputation scores
- Sending push notifications: about your gatherings, requests and messages; reminders before a gathering and to rate it afterwards; a weekly overview of upcoming gatherings (Monday); a reminder if you have not logged in for 3 to 14 days (at most one a day, then it stops); and, only if you turned it on in Settings, a weekly overview of new events in your city
- Content moderation and safety (blocks, reports)
- Positive tags participants give each other after a gathering, and your type computed from them (only if you switch it on)
- Suggestions of events and places you send for review: name, link, city, date and note
Who can see your data
- Your display name, photo, bio, and interests are visible to other users on your profile.
- Only your Connections see your birth year; your gender is shown only if you turn it on in Settings, and your email is shown to no one.
- The exact meeting address of a gathering is only visible to approved participants.
- Chat messages are only visible to participants of that gathering.
- Direct messages are visible only to the two people in the conversation. An administrator sees a direct message only while it waits for manual review by moderation because the automatic check could not run; after the decision they no longer see it. If you report a direct message, a quote from it (up to 200 characters) reaches the administrators with your report.
- Your overall rating score is seen by people from a shared gathering with you; new people see it only if you turn off "Hide ratings from new people" in Settings. Individual ratings are anonymous.
- What you liked is seen only by you. Gatherings are the exception: the host, the approved participants and administrators see the names of the people who marked interest in a gathering.
- Votes in a gathering's poll are seen by the host and the approved participants of that gathering.
- What you voted about others' attendance is seen only by you; the result about yourself is seen by you. Others are shown only the total (attended, cancelled early, no-show), according to your visibility settings.
- Connection requests and the link between you are seen only by the two people in it; the number of your Connections is shown according to your visibility settings.
- The photos in your profile gallery are seen only by your accepted Connections, unless you turned that off in Settings; people who are not your Connections do not see them.
- Bug reports and suggestions (text, screenshots, device data) are read by administrators; your text, name and email also reach our team by email, through Brevo.
- Only you see the tags you give; the tags given to you are shown to no one. Your type is never shown publicly.
- Your suggestions are seen by you and by the admins who review them. An approved place or event is shown to everyone, without your name.
- Photos added to a gathering are visible to the host and the approved participants.
Third-party services
We use the following services to operate the app:
- Supabase - database, authentication, and file storage (hosted in the EU)
- Expo Push Notifications - to deliver push notifications to your device
- Vercel - web app hosting
- OpenStreetMap - map tiles for the location picker (sends approximate viewport coordinates and your IP address, which is personal data, to the tile server when the map loads)
We do not sell, rent, or share your personal data with advertisers or data brokers.
Lawful basis for processing (GDPR Article 6)
For each processing purpose we declare the corresponding lawful basis:
- Account creation + authentication → Contract (Article 6(1)(b)).
- Push notifications → Consent (Article 6(1)(a)). You can withdraw at any time via Settings.
- Tags given to you → Legitimate interest (Article 6(1)(f)): positive only, from a fixed list, seen only by the person who gave them, and used for your type only if you switch it on. Computing your type → Consent (Article 6(1)(a)): off by default, and you can switch it off at any time in Settings.
- Suggestions of events and places → Performance of a contract (Article 6(1)(b)): it is a service you ask for. The text check, the limit of 3 a day and 10 a month and the stop after 3 refusals → Legitimate interest (Article 6(1)(f)): keeping the app free of spam and unsuitable content.
- Moderation + safety (reports, blocks, trust level) → Legitimate interest (Article 6(1)(f)).
- Consent timestamps → Legal obligation (Article 6(1)(c)) to prove GDPR compliance.
- Crash reports (Sentry) → Legitimate interest (Article 6(1)(f)). In the browser: technical crash data only; the account id and a small share of performance traces are added only after “Accept”. On the phone: reports are on by default, carry no account id and about 10% of traces; turn them off in Settings → Crash reports. No names, no emails, no session replay.
- One-time launch notice → Legitimate interest (Article 6(1)(f)). Includes one-click unsubscribe.
Sub-processors (detailed)
We use the following processors. Each is bound by a Data Processing Agreement (DPA):
- Supabase - database, authentication, file storage, edge functions. Hosted in EU (Ireland). DPA auto-signed via Supabase ToS.
- Vercel - web app hosting. Global edge. DPA + SCCs.
- Expo (EAS) - mobile build pipeline + push token relay. Hosted in US. DPA.
- Apple Push Notification service - iOS push delivery. US (platform-mandated).
- Google Firebase Cloud Messaging - Android push delivery. US (platform-mandated).
- Brevo (Sendinblue) - Transactional email. Hosting: EU (France). DPA. When someone reports a user, Brevo also carries the letter to the administrator about that report: it holds the names and email addresses of the reporter and the reported person, the reason, the title of the gathering (if the report comes from a gathering), the reporter's note and - for a report of a private message - a quote from it (up to 200 characters).
- Sentry - crash reports. EU region. Self-serve DPA. No session replay; no personal data by default.
- OpenAI - content moderation: the text of direct messages and photos (a gathering's cover and photos, the profile photo and the profile gallery) go through the moderation classifier. The group chat of a gathering and the title and description you write for a gathering are not sent there. Not kept beyond the request. USA. DPA via the API ToS.
- OpenStreetMap Foundation - map tiles for the location picker. Loading the map sends approximate viewport coordinates + IP to the tile server. Not a data processor in the strict sense (public tiles), listed for transparency. Your browser fetches the tiles directly from the OpenStreetMap server, so it sees your IP address, and an IP address is personal data.
- Google (Sign in with Google) - if you choose to sign in with Google, Google learns of the sign-in and returns your email and identifier to us. US. You start it, by pressing the button.
- Apple (Sign in with Apple) - if you choose to sign in with Apple, Apple returns an identifier and an email (real or Apple-relayed, your choice); on the phone we request name and email. US. You start it.
- Map providers - in the browser the tiles in the light theme come from the OpenStreetMap servers (tile.openstreetmap.org) and in the dark theme from CARTO (cartocdn.com), over OpenStreetMap data; the marker icons are loaded from unpkg.com. On Android the map is Google Maps, on iPhone it is Apple Maps. The provider sees the coordinates of the view and your IP address.
- Address search - when you type a gathering's address or pick a point on the map, the text or the coordinates go to OpenStreetMap Nominatim (nominatim.openstreetmap.org) - in the browser and on the phone alike. The service sees what you typed or the point, and your IP address. The app does not read where you are.
- Plausible Analytics (registered in Estonia, the data is processed in the EU) - on the website the script is loaded from plausible.io for every visitor, without cookies; it receives the page address, where you came from, the browser and device type, and the IP address, from which it derives the approximate location: country, region and city (according to Plausible the raw IP address is not stored). Besides the pages you open we also send events for actions, with these details: a gathering created (its type and the city), joining a gathering and an attendance vote (the result), a request approved or declined, a rating (the number of stars), sharing a gathering (the method), a connection request (whether it came from search) and an accepted request, a direct message sent (only its number of characters, not the text), a photo uploaded (the file size), a username chosen (its number of characters), a temporary no-show suspension (the reason) and the first-setup steps (how long it took and which step was filled in). We do not send names, emails, message text or gathering ids. In the phone app the setup, a created gathering, joining and a direct message reach Plausible through our server, together with the phone's IP address and type (User-Agent), as addresses like app://mobile/<event> without numbers. To limit requests, our server keeps for each person how many such events they sent in the current hour; this count is deleted within about two hours. You can turn it off in Settings → “Don't count me in the statistics”: this device then sends nothing to Plausible, neither pages opened nor actions. The choice is kept on the device, so it is made on each one separately.
- Google Maps (Android only) - the map for choosing a gathering's place is drawn by Google; Google receives the map view and the IP address. USA.
- Google Places (place details) - the page of a single place shows Google's data about it: on the website Google's element (photos, rating, reviews, opening hours) is loaded from maps.googleapis.com, in the app the rating, the number of ratings and the opening hours are asked from places.googleapis.com. Google receives the place's Google identifier, the language, the IP address and browser data (in the app, the app's identifier). Only on a single place's page, never in a list. USA.
- Meta (Instagram, Facebook) - when a gathering contains a link to an Instagram or Facebook post, the post is embedded and the browser (or phone) loads Meta's scripts; Meta receives the IP address and browser data. USA.
International transfers (GDPR Chapter V)
Some providers are in the USA: Expo, Apple (APNs and Sign in with Apple), Google (FCM, Sign in with Google, the map on Android and Google Places), OpenAI, Vercel and Meta (embedded Instagram/Facebook posts). The transfer relies on the Standard Contractual Clauses (Decision (EU) 2021/914) or on the adequacy decision (EU) 2023/1795 for providers certified under it. Push notifications cannot work without APNs/FCM - if you do not want this transfer, turn notifications off.
Retention periods (per category)
- Account + personal data (name, email, photo, city, bio, interests, birth year and month, the “I am 18+” stamp): deleted 30 days after the deletion request; until then the profile is hidden, and signing in or „Cancel“ in the email cancels the deletion.
- Inactive account: if you do not sign in for 24 months, the account is deleted as with „Delete account“; we mail you a month before. One sign-in starts the period again.
- Group chat: 12 months after the gathering. Direct messages: while at least one participant has an account; a conversation with no participants left is deleted within 30 days. Other parties' copies are anonymized as "Deleted user".
- Likes, poll votes, attendance votes and Connections: kept while your account exists and deleted with it; those tied to a gathering are also deleted when the gathering is deleted.
- Photos: gallery photos and photos added to gatherings are deleted when you remove them (for a gathering photo, the host can too), with the account of the person who added them, and when the gathering is deleted.
- Bug reports and suggestions, with their screenshots: no other limit, kept while your account exists and deleted with it.
- Ratings: ratings you gave others are anonymized and kept (for their reputation); ratings you received are deleted with your account.
- Email fingerprint after a ban: if a banned account is deleted, we keep a one-way fingerprint (SHA-256) of its email together with the reason for the ban. The email cannot be recovered from it, but it is still personal data (a pseudonym). We use it for one thing only: when someone signs up, we check that the address does not belong to a banned account. Legal basis: legitimate interest - the safety of the community (GDPR Art. 6(1)(f)). We keep it for 5 years from the deletion of the account; then it is deleted automatically. You can object at office@partimo.app.
- Database backups: Supabase's daily backups are kept for up to 7 days and our own nightly copy for up to 30 days; deleted data disappears from the backups within that time.
- Reports + moderation actions: 24 months for auditability. Anonymized after 24 months.
- Exact meeting place: deleted 90 days after the gathering (unless an open report concerns the gathering). In a recurring series each next edition gets a copy of the address, so it is kept while the series goes on and is deleted 90 days after the last edition.
- Person tags and type: tags you gave or received are deleted with your account and when the gathering is deleted; your type is not stored, and once you switch it off it is no longer computed.
- Suggestions of events and places: kept while your account exists and deleted with it. An approved place or event stays in the app, no longer linked to you.
- Log of administrator actions: 24 months.
- Crash reports (Sentry): up to 30 days.
- Plausible web analytics: aggregate visits only, no personal data; kept as long as our Plausible account exists. The count of events per person for the hour (request limit): up to about two hours.
- Email logs (Brevo): 30 days.
- Push tokens: on the phone they are deleted when you turn notifications off in Settings, when you log out, and when the notification service answers that the token is no longer valid; in the browser, when you turn notifications off in Settings, when the service answers that the subscription does not exist, and at the next send if the browser has not checked in for more than 60 days. Both kinds are deleted with the account. If you withdraw the permission only in the phone or browser settings, the token is not deleted at once: it stays until a send is rejected as invalid (in the browser, or until a send finds that it has not checked in for more than 60 days).
Data storage and security
Your data is stored securely in Supabase (Postgres database, Supabase Auth, and Supabase Storage). All connections are encrypted via TLS. Access to the database is protected by Row Level Security (RLS) policies that ensure users can only access data they are authorized to see.
Data retention
We keep your data while your account is active. When you request deletion, your personal data (name, email, photo, city, bio, interests, gatherings) is deleted permanently 30 days after the request; until then the profile is hidden, and signing in or „Cancel“ in the email cancels the deletion (GDPR art. 12(3): answered within one month). Content other people depend on is anonymized, not deleted: your messages in other people's chats and your participation in past gatherings remain as "Deleted user". If the account was banned for a violation, we keep only a pseudonymized record (a hash of the email + the reason) under the legal basis of legitimate interest, so a banned user cannot return clean. Database backups clear on their normal rotation (see the table below).
Automated decisions
Some things are decided automatically (GDPR Art. 13(2)(f)): your trust level is computed from ratings, attendance and reports; repeated no-shows suspend the account for a while; a gathering reported by three participants is hidden; text and photos flagged by OpenAI's classifier are not published (the text can be corrected and sent again). A suspension and a hidden gathering are shown to you in the app and you can contest them - a person reviews the objection. Write to office@partimo.app about any other automated decision.
Your type (only if you switched it on) is computed automatically from the tags most often given to you by at least three different people. It is shown to no one and has no legal or similarly significant effect on you (GDPR Art. 22). You can switch it off at any time, and you get the tags given to you with your data, without the names of those who gave them.
If both you and a gathering's organiser have switched your type on and your top three tags share at least one, the gathering moves up in your recommendations and may be shown instead of another. The same works the other way for your gatherings in theirs. Nothing is hidden or filtered; if either of you switches the type off, this stops.
The name and note of a suggestion pass the automatic filter for blocked words and adult content; a stopped text is not sent and you can correct it. After 3 refused suggestions in 30 days you cannot suggest for 30 days; an admin can lift the stop.
Your rights
- Delete your account and all associated data at any time from Settings.
- Edit or update your profile information at any time.
- Leave gatherings and cancel join requests.
- Block other users to prevent interaction.
- Request access to all personal data we hold about you.
- Ask us to restrict processing in the cases GDPR Art. 18 lists, for example while you contest the accuracy of your data. There is no switch for it in the app and nothing pauses by itself. Write to office@partimo.app; we answer within one month.
- Request a copy of your data in a portable format.
- Object (GDPR Art. 21) to processing based on legitimate interest. Crash reports, the web statistics and news emails have a switch in Settings: “Crash reports”, “Don't count me in the statistics”, “News emails”. For everything else, such as moderation with its automatic checks and the 18+ check, there is no switch in the app: write to office@partimo.app; we assess each request on its own and answer within one month.
- Lodge a complaint with the Bulgarian Commission for Personal Data Protection (KZLD).
We answer every request within one month (GDPR Art. 12(3)). You can also download a copy of your data yourself: on the web Settings → “Download my data”, in the phone app Settings → “Export my data”.
KZLD: 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria
https://www.cpdp.bgChildren's privacy
PARTIMO is not intended for anyone under 18 years of age. We ask for your age after sign-up. If you give an age under 18, you do not get access to the app and no date of birth is kept, but the email, name and photo from sign-up stay until the account is deleted - by you, or after 24 months without a sign-in. If you believe a minor is using the app, contact us: we review the report and remove the account. The deletion is a manual step by an operator, not automatic.
If the age check stopped you after sign-up because you are under 18, the app stays locked for you and you cannot reach the delete-account button in Settings. To have that account deleted, email office@partimo.app from the account's email address: we review the request and remove the account. This is a manual step by an operator, not automatic.
Advertising and tracking
PARTIMO does not display ads, does not use tracking pixels, and does not share data with advertising networks. We do not build advertising profiles.
Cookies
We set only five technical cookies (pa_s, pa_lang, pa_bt and pa_theme for 1 year, pa_k for 1 day): they tell the server whether a sign-in is stored on this device, which language and theme you chose, whether you closed one tip and whether this device keeps your Home screen, so it sends the right page. Your sign-in lives in the browser storage rather than in a cookie, and on logout we delete the old Supabase cookies if an earlier version left any. There are no analytics cookies and no third-party tracking cookies. The full list of what sits in your browser is in the table below. The “Accept” button in the notice sets no cookie: it lets crash reports in the browser carry your account id and a small share of performance traces. “Decline” leaves them without; you can change the choice in Settings.
What we keep in your browser
We set only five technical cookies, which tell the server which page to send you: whether a sign-in is stored on this device, which language and which theme you chose, whether you closed one tip, and whether this device keeps your Home screen. Everything else below is kept in the browser’s own storage (localStorage and sessionStorage) on your device and does not travel to us, except your sign-in, which the requests carry.
| Name | Where | What it is for | How long it lives |
|---|---|---|---|
| pa_s, pa_lang, pa_bt, pa_k | Where: cookie | They tell the server which page to send you: whether a sign-in is stored on this device, which language you chose yourself, whether you closed the bilingual tip, and whether this device keeps your Home screen. Nothing personal, no tracking. | How long it lives: 1 year (pa_k: 1 day), or until you log out, change the language or clear the site data |
| pa_theme | Where: cookie | Tells the server which theme you chose yourself (light or dark), so it sends the page in that theme from the first frame, with no flash. Nothing personal, no tracking. | How long it lives: 1 year, or until you set the theme back to “System” or clear the site data |
| sb-<project>-auth-token | Where: localStorage | Your sign-in. Without it every visit would ask for the password again. | How long it lives: Until you log out or the token expires |
| pa_home_snapshot_v1 | Where: localStorage | Your Home screen as you last saw it (the top bar and the first two cards), so it shows at once the next time you open the app. | How long it lives: Shown for up to 1 day; deleted when you log out or clear the site data |
| cookie_consent_v1 | Where: localStorage | Your answer to the optional-measurements question, so we do not ask again. | How long it lives: Until you clear the site data |
| socialapp_lang, socialapp_lang_explicit_v1, i18nextLng, partimo_lang_decision_reported_v1 | Where: localStorage | The language you picked, that you picked it yourself rather than the device, and that we already noted once which language the browser asked for. | How long it lives: Until you clear the site data |
| theme_mode_v1 | Where: localStorage | Light or dark theme and which colour set. | How long it lives: Until you clear the site data |
| partimo.crashReports | Where: localStorage | Whether you agreed to send us crash reports. | How long it lives: Until you clear the site data |
| partimo.analytics, plausible_ignore | Where: localStorage | Whether you chose “Don’t count me in the statistics” (Plausible). | How long it lives: Until you clear the site data |
| safety_tips_seen, pwa_visit_count, interests_hint_dismissed, moderation-notice-seen:<id>, vibsy_bilingual_tooltip_seen, vibsy_events_add_hint_dismissed_at, notif_prompt_dismissed_<uid>, invite_friend_prompt_last_<uid>, vibsy_ever_signed_in_v1 | Where: localStorage | Which tip or hint you have seen or closed, and when, so we do not show it again or too often. | How long it lives: Until you clear the site data |
| pwa_install_dismissed | Where: localStorage | That you closed the offer to install the app. | How long it lives: 7 days |
| preferred_city_<uid>, city_around_mode, hidden_invites_<uid>, muted_organizers_<uid>, notif_marked_read_at_<uid>, onboarding_completed_<uid>, vibsy_welcome_dismissed_<uid>, vibsy_has_created_invite, ratings_structured_columns_support_v1 | Where: localStorage | Your settings on this device: the chosen city and area, gatherings you hid, organizers you muted, how far you have read your notifications, whether you have seen the welcome and the first setup, and a technical note on what the server supports. | How long it lives: Until the site data is cleared |
| invite_draft_<uid> | Where: localStorage | An unfinished gathering, so you do not lose it on reload. | How long it lives: Until the draft is published or discarded; after 24 hours it is no longer used and is removed the next time the form is opened |
| rl_* | Where: localStorage | Counters that limit how often an action can be done (for example sending a report). | How long it lives: Until you sign out or clear the site data; the daily count starts again each day |
| vibsy_signup_consent_pending | Where: localStorage | Your consent at sign-up, until you confirm your email. | How long it lives: Until the first sign-in after confirmation |
| deep_link_redirect_v1, post_auth_notice, vibsy_feed_pages_v1:*, vibsy_create_from_event, attendance_prompt_dismissed_v1, oauth_login_error_v1, vibsy_auth_redirect_error_v1, vibsy_last_error_v1, vibsy_stale_chunk_recovery_attempted, vibsy_sw_legacy_wiped, vibsy_sw_reloaded, vibsy_proof_nonce_v1 | Where: sessionStorage | Things for this tab only: where you wanted to go before signing in, a question you already answered here, the last error, a gathering started from an event, and a note that the page was already reloaded. | How long it lives: Deleted right after use or when the tab closes |
The five cookies (pa_s, pa_lang, pa_bt, pa_k, pa_theme) carry nothing personal and do not track you; when you log out we also delete old Supabase cookies if an earlier version left any.
Changes to this policy
If we make significant changes to this Privacy Policy, we will notify users through the app. Continued use of PARTIMO after changes constitutes acceptance of the updated policy.
Contact
For privacy questions or data requests, contact us at:
office@partimo.app