Tikit is an app where people sell and buy event tickets to one another. This policy explains what data of yours we process, why, and for how long. It is written to be read from start to finish.
1. Controller
The controller responsible for your data in the Tikit app and website is:
- Jurģis Rudaks (a private individual)
- Email: support@tikit.lv
- Website: https://tikit.lv
No data protection officer has been appointed. Send any question about your data to the email address above.
2. What data we process
We process only what the app needs in order to work, and nothing beyond that:
- Phone number — to create your account and to confirm sign-in with an SMS code. You cannot create an account without it; it is the only way to sign in. The account record also carries a technical placeholder e-mail address derived from the number; no e-mail is ever sent to it.
- First and last name — you enter these when you set up your profile. On listings, other users — including people who have not signed in — see your name abbreviated (first name and the initial of your last name); in a conversation the other party sees your full name and profile photo. A seller who marks tickets as sold to you sees your full name next to that listing in their account, and when choosing the buyer sees the name, photo and last message of each person who wrote to them about it.
- Seller history — the month you joined Tikit and the number of deals you have completed, or that you are a new seller. These are shown on your listings to everyone. A completed deal means that you named a buyer and the event has passed; it is not a payment Tikit has checked.
- User ID — the internal account number we use to link your profile, your listings and your conversations. It is not shown as text on any screen, but it is part of technical identifiers that other users’ devices handle — for example the address of your profile photo and the identifiers of your conversations — it is sent to our processors to identify your account, and it is included in the notifications Apple delivers to your own phone. It is used for nothing else.
- Profile photo — optional. The app works the same way without one. It is shown in conversations, to a seller choosing a buyer, and on the list of users you have blocked.
- Approximate location — only after you allow it in the iPhone system dialog, which the app shows on first launch or when you turn on the “Nearby” filter. The app rounds your coordinates to roughly a kilometre and sends them to our server solely to show events near you first on the home screen and sort them by distance. We do not store them or link them to your account; you can switch the filter off at any time, and the permission in iPhone Settings.
- Listings and ticket details — the event date, the price, the number of tickets, the ticket type or section label and your note to buyers. Listings are visible to everyone using the app, including people who have not signed in. When you edit a listing, we keep the previous and the new price, ticket count and note.
- Chat content — messages between a buyer and a seller and the images, videos or files attached to them. Photos are re-encoded before upload, which removes camera metadata such as location; videos, GIF and WebP images and small PNG images are sent as they are. Tikit also writes system messages into a conversation — a safety note when it starts, notices when a listing is edited, sold, withdrawn or expires, notices when the event date is cancelled, postponed, moved to another time or venue or reinstated, reminders when a buyer is waiting for a reply, and the outcome of a report — and some of them name the other party.
- Search text — what you type into search is used to find matching events; part of that is a semantic match computed by Google (section 4). Recent searches are remembered only on your phone.
- Submitted events — if you submit an event: its name, date, venue, link, description, category, whether entry is ticketed and whether you are the organiser, plus the link between your account and the submission so that you can see its status. Our team reviews the submission but does not see who sent it; your name is not shown on a published event. If you write to us about a submission (its reference is in the email subject), support can link your email address to that submission. Google turns the name and description into a numerical representation so we can find whether the event is already in the catalogue (section 4).
- Reports about users — if you report someone or someone reports you: the reason you choose and the listing or conversation it concerns. Your report is also registered with Stream, our chat provider, under your name as the reporter, so that the conversation can be reviewed. Some reports are created by the app itself (section 3).
- Reports through the web form — if you report content at /report: the category you chose, your description of where the content is and what is wrong with it, and — if you give them — your name and email address. The name and the email are optional; without an email we cannot tell you the outcome.
- Reports of mistakes in event details — if you report that something in an event’s details is wrong: what you ticked (for example, the date or the venue), your note if you write one, the event the report is about, and the link to your account. If you report the same event again before we have reviewed your earlier report, we add the new one to it. Our team reviews the report; the review tool does not show who sent it.
- Moderation and audit records — the app automatically checks message text for signs that a conversation is being moved away from Tikit: a phone number or a reference to another messaging app; the server checks it again. A mark about such a message is kept against its author and used as a risk signal for 30 days, and the message is marked at Stream so that the reminder is shown only once per conversation. We also keep records of actions that matter in a dispute: who was designated the buyer of a listing and any change of buyer, blocks made after a sale, a new listing for an event date you had already sold tickets for, edits to a listing, and the decision taken on a report.
- Automatic checking of chat — every message you send is checked automatically by Stream, our chat provider: block lists and Stream’s AI language models, which read the message text in context to spot harassment, hateful content, sexual harassment or ticket fraud. The message is always delivered — nothing is blocked automatically — and a flagged message goes into a review queue that we, not Stream, look at; the queue is hosted by Stream.
- Blocks — whom you have blocked and who has blocked you.
- Device notification token — only if you allow notifications. The token is stored with our chat provider Stream and, for notifications Tikit sends itself (section 3), in our own database in the EU together with whether it is a test or a production build of the app and when the app last registered it. The app asks for it to be removed from both when you sign out, and asks Stream to remove it when you turn notifications off while the app is open.
- Notification settings and delivery log — your choices for the two notification categories (section 3), and a record of each notification we prepare for you: which category, which event date or listing it is about, when it is due, and whether it was sent, skipped or failed.
- Technical data — the IP address and the device or browser description stored with your active session, the SMS code together with the number it was sent to while the code is valid (a few minutes), the date and version of the terms you accepted, plus server request and error logs.
In the App Store privacy section the same data is labelled with the categories “phone number”, “name”, “user ID”, “photos or videos”, “emails or text messages”, “other user content” and “purchases” (who was designated the buyer of a listing), all linked to your account. Three more categories are not linked to your account: “coarse location” for the “Nearby” filter, and “device ID” and “crash data” for the app’s update check at Expo (section 4) — the randomly generated installation identifier and the short error description after a failed start. None of these categories is used for tracking — that is exactly what the app’s privacy manifest declares.
Photos for your profile and for chat can be taken with the camera or chosen from your library; recording a video in chat uses the microphone. The app asks for each of these permissions only when you use the feature.
Event information — titles, dates, venues, descriptions and posters — comes from the organisers’ and ticket sellers’ public pages and may include contact details they publish. We process it to show the event catalogue; it is not data about you.
We do not process payment data: Tikit takes no money and is not involved in settlement between a buyer and a seller. We do not ask for and do not process special categories of data (health, political opinions, religion and the like) — please do not send them in chat either.
3. Purposes and legal bases
- Providing the service — your account, listings and the conversation between a buyer and a seller. Legal basis: performance of a contract (GDPR Article 6(1)(b)).
- Confirming the account with an SMS code — so that every account belongs to a real phone number. Legal basis: performance of a contract and our legitimate interest in preventing fake accounts.
- Finding events — the search text you type is matched against the event catalogue; the semantic part of that match is computed by Google’s Gemini API (section 4). Legal basis: performance of a contract.
- Showing nearby events — the home screen shows events around you first, based on your approximate location (section 2), but only after you have allowed it in the iPhone system dialog. Legal basis: your consent (Article 6(1)(a)); access to your device’s location also requires your consent (Directive 2002/58/EC, Article 5(3)). You can withdraw it at any time (section 6).
- Reviewing submitted events — we check whether the event is already in the catalogue, review the submission and, if we publish it, add it to the catalogue; to find similar events the submission’s name and description are processed by Google’s Gemini API (section 4), and the link to your account lets you see the status and the decision. Legal basis: performance of a contract.
- Accurate event details — we review reports of mistakes in event details, check them against the source and, where needed, correct the event catalogue. The link to your account lets us combine your repeat reports about one event and limit how many reports can be sent per day. Legal basis: our and other users’ legitimate interests (Article 6(1)(f)) — accurate information about events.
- Safety, fraud prevention and handling reports — blocking, withdrawing listings and temporary pauses on accounts with an open report. This also covers the automatic check of message text: if we spot a phone number or an invitation to move to another messaging app, a one-time safety reminder appears in the conversation and a mark stays against the message’s author. The mark alone restricts nothing — it is a signal if a report about that account comes in. It also covers the automatic checking of chat at Stream (section 2): block lists and Stream’s AI language models read the message text to flag harassment and fraud for a human to review. Neither check blocks a message or applies any consequence to you on its own. Legal basis: our and other users’ legitimate interests (Article 6(1)(f)) — an environment where a ticket buyer does not get scammed.
- Automatic safety rules — a few rules run without a person deciding, and every one of them lifts on its own: while a report about your listing is open, you cannot edit that listing, change its buyer or post another listing for the same event date; if two different users report you for fraud or for not delivering tickets, creating new listings is paused until we have reviewed the reports; and if you have marked tickets as sold to a buyer and do not reply to them for about a day (a few hours when the event is close), we remind you in the conversation, and if you still do not reply, the app records this as a report and pauses new listings and buyer changes until you answer — at the latest 7 days after the event; if the event date has been announced as cancelled, 30 days after the event or after the cancellation was announced, whichever is later; and if the event has been postponed with no new date yet, 97 days after the original date. Legal basis: the same legitimate interests.
- Notifications — about new messages and reactions to your messages, a sale confirmed to you or a change of buyer, reminders when a buyer is waiting for your reply, and the outcome of a report about a listing. Legal basis: your consent (Article 6(1)(a)). You can withdraw it at any time in iPhone Settings → Tikit → Notifications; your phone then shows no more notifications.
- Service notifications — when the date of an event you have a listing, a purchase or a conversation for is cancelled, postponed, moved to another time or venue, or reinstated, and when a conversation you started about a listing is closed because the tickets went to someone else or the listing is no longer available. Tikit sends these itself through Apple (to an older version of the app, as a conversation notification through Stream), at most one per change. A change to the event date is also written into each conversation about the listing; a closed conversation already shows its closing message. Legal basis: for sellers and for buyers to whom tickets were marked as sold, performance of a contract (Article 6(1)(b)) — the deal depends on the event taking place; for people who only wrote to a seller, our and their legitimate interest (Article 6(1)(f)) in knowing that the conversation is over. Your phone shows them only if you have allowed notifications in the iPhone dialog. You can turn off each category — “Event changes” and “Listing and chat status” — in Account → Notifications, or all notifications in iPhone Settings; the notice in the conversation stays either way.
- Receiving and handling reports about content — both in the app and through the web form. The Digital Services Act (Regulation (EU) 2022/2065, Article 16) requires such a reporting route to exist and the reports to be handled. Legal basis: a legal obligation (Article 6(1)(c)).
- Availability and abuse prevention — rate-limit counters that stop a single account or IP address from overloading the service. Legal basis: legitimate interests.
We do not take automated decisions that produce legal effects for you. Whether a report is upheld, and whether a submitted event is published, is always decided by a person; the system itself applies only the temporary pauses described above, and you can contest them by writing to us. After an upheld report you cannot create or edit listings for 90 days; the Terms of Use describe how to ask for a review.
4. Processors and where data is stored
The following processors handle data on our behalf:
- Supabase — the database: account, listings, reports, moderation records, device notification tokens, notification settings and the notification delivery log. Stockholm, Sweden.
- Vercel — the website and the app server. Server functions run in Stockholm, Sweden; the connection is accepted, and the sign-in check for website pages runs, on the node of Vercel’s global network closest to you.
- Stream — chat and the files attached to it, previews of links pasted into chat, device notification tokens, reports, and the automatic checking of message content (see section 2). Our chat app is hosted in Dublin, Ireland; the connection goes through Stream’s global edge network, and Stream does not guarantee a location for uploaded attachments. For a link preview Stream reads the linked page’s title and picture, but the preview picture itself is then loaded by the devices in the conversation straight from the linked site, which therefore sees their IP addresses.
- Twilio — the SMS with your sign-in code. Ireland; the message itself is then delivered through the mobile networks.
- Upstash — rate-limit counters. Frankfurt, Germany.
- Cloudflare R2 — profile photos. EU jurisdiction. Your phone uploads the photo directly to Cloudflare, and other users’ devices load it from there, so Cloudflare sees the IP addresses involved.
- Cloudflare (Workers and Images) — event posters and the images in event descriptions. The app loads them from Tikit’s image service on Cloudflare, which fetches each image from the organiser’s or ticket seller’s site and passes it on resized. The request is served by the node of Cloudflare’s global network closest to you, so Cloudflare sees your IP address; the images are kept only in a temporary cache, and we keep no log of these requests. The original sites now receive requests from Cloudflare, not from your device. The one exception: if Cloudflare cannot reach a site at all (for example, because of a broken security certificate), the app loads that image directly from the original site, which then sees your IP address.
- Google (Gemini API) — when you search, the search text is sent to Google to compute a semantic match with events. When you submit an event, its name and description are sent to Google to find similar events in the catalogue; your name and account are not sent. Google also helps us prepare event descriptions from the organisers’ public pages, which involves no data about you. USA.
- Expo (EAS Update) — when the app opens it checks whether an update to the app’s code is available. Expo receives the IP address, the app version and platform, the identifiers of the installed update, a randomly generated installation identifier that is not linked to your account (Expo also uses it to count how many installations run each update) and, if the previous start failed, a short technical error description. USA.
Your account data, listings, conversations and photos are stored in the EU and the EEA. There are three exceptions: (1) the automatic checking of chat — Stream may use sub-processors outside the EU/EEA for that analysis under Stream’s data processing agreement; Stream’s public sub-processor list names both EU and US providers for moderation, and Stream does not guarantee that this check stays within the EU/EEA; (2) the update check at Expo, which happens in the USA and receives only the technical data listed above; (3) the semantic part of search and the matching of submitted events, for which your search text and a submitted event’s name and description are sent to Google in the USA. In all cases the transfer takes place under that provider’s data processing terms.
Besides our processors there are independent recipients:
- Apple — the Apple Push Notification service delivers notifications to your iPhone. The notification text (an excerpt of the message), the sender’s name, the event name, the number of unread conversations, the technical identifiers of the conversation and message, your user ID and the device token reach it. For the service notifications Tikit sends itself (section 3), our server sends Apple the event name, one sentence about what changed, the technical identifiers of the event, date, listing and conversation, and the device token. Apple is an independent controller for that delivery; the transfer happens on Apple’s own terms, and we cannot guarantee that this delivery path stays within the EU/EEA. If you would rather it did not, turn notifications off in iPhone Settings — everything else in the app works the same way.
- Google — while you are in chat, the app checks about once a minute whether the internet is reachable by contacting a Google server; only the request itself, with your IP address, reaches Google.
We may also hand data to law enforcement and supervisory authorities (for example the police or the Consumer Rights Protection Centre) where the law requires it or where it is necessary to resolve a dispute. We do not sell data and we do not pass it to advertisers.
5. How long we keep it
- Account and profile — for as long as the account exists. When you delete the account, the phone number, the name and the profile photo are irreversibly removed, sessions and sign-in credentials are revoked, and active listings are withdrawn from publication. A de-identified account record remains so that the deal history below stays attributable to an account.
- Chat — at least 12 months after the event date. Tikit takes no payments, so the conversation is the only evidence of the deal that was agreed if a dispute arises or authorities have to be given information. Conversations are not deleted when one is closed either, and today we do not delete them automatically after the 12 months; after you delete your account they remain, but a deleted account is shown in your place.
- Listings and ticket records — kept attached to the account record for as long as the chat: they are part of the same deal. That includes listings you removed yourself and the edit history.
- Submitted events — the link between your account and a submission is kept for as long as the account exists; when you delete the account it is removed. The event details themselves stay in the catalogue or the review history with no link to you.
- Reports of mistakes in event details — for as long as the account exists, including after the report has been reviewed. When you delete the account they are deleted, notes included. If an event is removed from the catalogue, the reports about it are deleted with it.
- Reports about users — for as long as they are needed to resolve disputes and apply safety measures; today we do not delete them automatically. A restriction imposed after a decision lasts 90 days from the day of that decision.
- Reports through the web form — 12 months after the report has been handled and closed. There is no automatic deletion today; we delete the rows ourselves.
- Moderation and audit records — the same as reports: for as long as they are needed to resolve disputes and apply safety measures; today we do not delete them automatically. Only records from the last 30 days are used as a risk signal.
- Blocks — until you unblock. When you delete your account, your own blocks are removed; blocks that others placed on you stay with their accounts.
- Sessions — until you sign out, delete the account, or 365 days pass without the app being opened.
- Device notification token — at Stream until you sign out or delete the account, or turn notifications off while the app is open; in our database until you sign out or delete the account. If Apple reports that a token is no longer valid, we stop using it.
- Notification delivery log — 60 days after the notification was sent, skipped or failed; when you delete the account your pending notifications, settings and tokens are deleted at once.
- SMS code — together with the number it was sent to, until it is used or expires (a few minutes).
- Our service providers’ logs — Vercel, Supabase, Stream and Expo keep their own operational logs and delete them on their own schedules. Vercel deletes runtime logs after the period set by its plan; on the plan in use today that is one hour.
- Rate-limit counters — only for the length of the relevant limit window, from a few minutes up to two days.
- Backups — we keep occasional backup copies of the database ourselves; a deleted account can remain in a backup copy until that copy is deleted.
6. Your rights
You have the following GDPR rights over your data:
- Access — to get confirmation that we process your data and a copy of it.
- Rectification — you can correct your name and profile photo yourself in the app: Account → Edit profile.
- Erasure — in the app: Account → Delete account. Deletion is irreversible: the phone number is removed, so signing up again creates a new account. Only what must not be lost in a dispute remains — the chat and deal history under a de-identified account record.
- Objection — to processing based on legitimate interests. For the notice that a conversation is closed you can do this yourself: Account → Notifications → “Listing and chat status”.
- Restriction of processing — while we handle your objection or your challenge to the accuracy of the data.
- Data portability — to receive the data you have given us in a machine-readable format.
- Withdrawal of consent — turn notifications off in iPhone Settings, or a single category in Account → Notifications; stop location use by turning off the “Nearby” filter or revoking the permission in iPhone Settings → Tikit → Location. Withdrawal does not affect processing that happened before it.
To exercise the rights of access, restriction, objection or portability, write to support@tikit.lv. We normally answer support mail within 2 working days, and we fulfil a data subject request no later than within one month.
If you believe your data has been handled wrongly, you can lodge a complaint with the supervisory authority — the Data State Inspectorate (Datu valsts inspekcija, www.dvi.gov.lv).
7. No tracking
- There are no ads and no advertising identifiers in the app.
- There is no analytics or crash-reporting SDK in the app — we do not follow what you do in the app beyond what the feature itself needs.
- We do not combine your data with data from other apps or websites and we do not pass it to advertising networks.
- We do not sell data.
That is why tracking is marked “no” for every data type in the app’s privacy manifest, and the app never asks for tracking permission.
This website uses only strictly necessary cookies: the sign-in session cookie and the operator console’s unlock cookie. There are no analytics, advertising or tracking cookies, which is why the site has no consent banner.
8. Children
Tikit is not intended for people under 18. By creating an account you confirm that you are at least 18 years old. If we learn that an account belongs to a minor, we delete it. If you know of such an account, write to support@tikit.lv.
9. Changes and contact
If we change this policy materially, we publish the new version on this page and change the date at the top of the page; if a change is significant, we will let you know before it takes effect — for example in the app or by SMS to the number on your account. The date of this version is 2026-10-11.
Questions about this policy and data requests: support@tikit.lv, Jurģis Rudaks.