Privacy policy (draft)

DRAFT — to be reviewed by a lawyer. This privacy policy takes effect only once we publish it without this mark.

Version 1.0 of 13 October 2026. This is an English translation of the Polish privacy policy. The Polish version is binding; where the two differ, the Polish version prevails.

1. Who is responsible for your data

The controller of your personal data is «OPERATOR NAME», «ADDRESS», tax ID (NIP) «NIP», «REGON/KRS» — the provider of Flikki (in this policy: “we”).

For everything to do with your data, write to [email protected]. We have not appointed a data protection officer.

This policy covers the phone app, the browser app at app.flikki.app, the Chrome extension and our website. Words such as “item”, “run” or “plan” mean the same as in the terms.

2. In short

We try to keep as little as possible. We do not ask for your surname, address or phone number, we do not know your Vinted password and we never receive your card details. The exception: if you create an account through Google or Apple, we save the name from that account as your nickname — often it is your full name. You can change it in settings.

We show no ads, do not sell data, use no third-party analytics tools and do not track you on other websites. Our website stores nothing on your device and loads no scripts from elsewhere.

3. What data we collect, why and on what legal basis

The legal bases are those of the GDPR, Article 6(1): point (b) — the data is needed to perform the contract with you (the terms) or to take steps before entering into it; point (c) — we must process it by law; point (f) — our legitimate interest, which we describe for each such case. We do not base any processing on consent.

Account — email address, first name or nickname, country, language, currency, whether the email address is confirmed, password (if you set one; we keep only its hash), the date the account was created, settings, and, if you sign in through Google or Apple (today only on app.flikki.app), the identifier of that account; if you create the account that way, also the name from that account as your nickname (when there is none, the part of the email address before the “@”). Why: to run the account and sign you in. Basis: the contract (point b).
Sign-in link request — when you ask for a link, we save the email address, the first name or nickname entered at sign-up and the language. This also applies to a sign-up you do not finish. Why: so that the link works. Basis: steps before entering into the contract, and the contract (point b).
Signed-in devices — the type (phone, browser, extension), the device name (for example “Chrome on MacBook” — given by the app or, when connecting with a QR code, read from the description the browser sends), when the device was connected and last used, and which device connected it. We do not record an IP address or location with them. When connecting with a QR code, for a few minutes we keep a hash (with a secret key) of the network the browser asked to connect from — not the address itself — so that the phone can tell you whether it is the same network. Why: so that every device can be seen and disconnected, and to detect an account takeover. Basis: the contract (point b) and account security (point f).
Your items — photos (cleaned, section 4, and their touched-up versions), titles, descriptions, brands, sizes, categories, condition, colours, materials, prices, acquisition dates (if you enter them), batches (with the amount and purchase date, if you enter them), sales (amount, place, date), listings (the listing’s address and number on Vinted), runs and their results, settings, remembered categories, and the history of our suggestions together with your note for the description. Why: this is the service. Basis: the contract (point b).
Plan limits — how many items, runs, descriptions, photo touch-ups and refreshes have been used in the current period and on individual days. Why: to enforce the plan’s limits. Basis: the contract (point b).
Payments — when you buy a plan: the customer, subscription and payment identifiers at Stripe, the plan, the billing period, the subscription status, the period dates, the number of failed payments, the date and reason the subscription ended, the periods of Minis you bought and — for a refund or a dispute with your bank — its type, amount and currency. We never receive your card details, full name or billing address — Stripe collects them. Why: to switch on a paid plan, switch it off after failed payments or a refund, and handle payment matters. Basis: the contract (point b), and our interest in settling refunds and disputes and in protection against abuse (point f).
Messages to us — the subject and content, and, if you write from the app or the extension: the app or extension version, the full description of the browser or phone that the device sends (the so-called user agent), the type and address of the last error the app showed, and the request number it appeared with. We do not save a reply-to address with the message — when sending, we take your account’s email address and reply to it. The message also arrives by email in the team’s inbox (section 6). Why: to reply to you and find the cause of an error. Basis: the contract, when you write about your account (point b); in other matters, our interest in handling requests (point f).
Two questions after sign-up — what you use today to sell on Vinted (with the option of typing the name of another tool, up to 80 characters) and — only in countries where Vinted has Vinted Pro, so not in Poland — whether you have access to the Vinted Pro API. Answering is optional: you can skip them. We look at the answers only in aggregate. Why: to know what to build next. Basis: our interest in developing the service (point f).
How you use Flikki — the date the account was created, the days on which items were added or changed, the date of the first listing and of the first computer connection. We look at them in aggregate, as numbers for whole sign-up weeks. Why: to know where people get stuck. Basis: our interest in developing the service (point f).
Reminder about items that are not selling — unless you turn it off, once a week we send an email listing items that have been on Vinted for more than 30 days: their names, prices, a suggested lower price and how many days they have been up. We write only when, since the previous message, at least 5 more items have been up for more than 30 days, and only if Flikki has been used on one of your devices in the last 60 days. It comes from [email protected], so a reply goes to the team’s inbox. We save only whether the reminder is on, when we sent the last one and from when we count; we do not keep the content of the messages. You turn it off in settings or with the link in any such message, without signing in. Why: so that items that are not selling do not slip out of sight. Basis: our interest in the service being useful to you (point f); you object by turning the reminder off.
Security — a record of sign-ins and sign-ups (with the method used), of setting and removing a password, of connecting and disconnecting devices, of reuse of an old token, of deletion of the account (by you or by us), of its final erasure, and of blocking and unblocking. The record contains a pseudonym of the account (a hash of its identifier with a secret key) and the session identifier, without an IP address. After a password is added, changed or removed, we email you a warning. To limit the number of sign-in attempts and other actions, we keep a hash — with a secret key — of the email address, the IP address (for IPv6: the part shared by the home network), the account identifier or the session identifier; we do not record the IP address itself. Why: to protect accounts against takeover and the service against abuse. Basis: our interest in security (point f).
Technical data — for every request to the server we record the method, the address pattern in the app (without parameters), the result, the response time, the account identifier and the request number, which the app may show with an error. No IP address and no browser description. Why: to fix errors and find a specific problem when you write about it. Basis: our interest in a working service (point f).
Team actions — if we block an account, we record the reason; if we grant you a plan, we may add a note you do not see. Every such action goes into the administration log with the account identifier. Why: so that it is known who changed something and why. Basis: our interest in accountability and in protection against abuse (point f).
Reports of illegal content, complaints and withdrawals from the contract — what you write to us and our reply. Basis: obligations under the Polish Consumer Rights Act and the Digital Services Act (point c), and our interest in defending against claims (point f).

Giving an email address and a nickname is voluntary, but without them you cannot create an account. Everything else you give by using the service, and you decide what to enter.

4. Photos, suggestions and photo touch-ups

Cleaning photos. Shortly after a photo is uploaded, we save it again — as JPEG, PNG or WebP (a HEIC photo from an iPhone as JPEG), at most 2,048 pixels on the longer side: rotated the way it should be viewed, and without the hidden data the phone or camera added to the file — among other things, without the location where the photo was taken (GPS), the date, the camera model and the author’s name. We delete the file in the form in which it reached us 20 minutes later — we store and show only this cleaned copy. We clean touched-up versions of photos in the same way.

Suggestions. When you add an item or ask for a new suggestion, we prepare a title, description, category, brand, size, condition, colours, materials and price. We do it like this:

We send the item’s first photos (today up to six), saved as JPEG 1,600 pixels wide, to Google, to the Gemini API service (section 6). With them goes what is already known about the item — title, brand, size, condition, who it is for, your note for the description — your country, language and the currency of Vinted in that country, and our lists of categories, colours and materials.
Google’s software recognises what is in the photos and sends us back a suggestion. We then send only what was recognised, without the photos, to pick a category from our list. If one of the photos shows a label, we send that one photo again to read it accurately.
We enter the suggestion into the item and save it in its history together with your note. You can change it or ask for a new one. Nothing goes to Vinted until you start a run.

In doing so we do not send your email address, nickname or account identifier — only the photos, the item’s details and your note. We use the paid tier of the Gemini API. Under Google’s terms for that tier, Google does not use such requests or responses to improve its products, and keeps them for 55 days solely to detect and prevent violations of its usage policies.

We do not make decisions about you based solely on automated processing that produce legal effects concerning you or similarly affect you: a suggested price or category is only a suggestion, and you decide on it.

Photograph the items only: if someone’s face or a document ends up in a photo, it goes to that company together with the rest of the photo. Also do not write anything about yourself in the note for the description.

Photo touch-ups. “Improve quality” and “Remove background” work on your phone: on an iPhone with a built-in system feature (Apple Vision), on Android with the Google ML Kit library built into the app. The photo is not sent anywhere for this. We upload the finished touched-up version to Flikki next to the photo from before the touch-up, which stays unchanged.

Google ML Kit in the phone app. The app uses the same Google library to read the QR code when connecting devices (on iPhone and on Android). The camera image and photos are processed on the phone and do not go to Google. According to Google, however, the library sends Google diagnostic data: information about the device (manufacturer, model, system version) and about how the features work (for example processing time), and, when scanning codes, also a random identifier of the scanning session. We do not attach any of your account data to it.

5. The Chrome extension — what data passes through it

What it stores in the browser. Once connected to the account: the Flikki session token and session identifier (in the extension’s storage, which survives closing the browser) and a short-lived access token (in storage the browser clears on closing). During a run also: the run number, the item it is filling in at the moment — with its details and the signed addresses of its photos, for a price change with the address of the listing on Vinted and the new price, and for a refresh with the address of the old listing and the title it was listed with (also when it has to wait, for example for you to sign in, and also after the browser restarts) — the title of the last item, which it shows in its pop-up, the number of the tab it works in, whether Vinted asked for a sign-in, and failure reports waiting to be sent. It does not store the Flikki password or anything from your Vinted account. Disconnecting the extension from the account removes everything except the saved descriptions of Vinted’s form, which are the same for everyone and contain none of your data — including the item it was filling in and results that the Flikki server has not yet accepted (before removing them the extension tries to send them, and the pop-up warns that whatever it does not send will be lost). Only when the extension’s session is ended by the Flikki server (it expires or the account is blocked) do such results — an item that may already have reached Vinted, with the title, the values entered in the form including the description and price, the listing’s address, and the run, task and account numbers — stay, so that the same item is not listed twice, and the extension sends them when you connect it to the same account again.

When it works. Only on Vinted’s pages and only in a run you start in the Flikki app. It is built to work in one tab, which it opens when the run starts; it fills in further items in the same tab, also when you switch to another one. If you close the browser during a run, when you start it again the extension returns to that run and opens Vinted by itself — unless you pause or stop the run in the app. It does not resume a refresh run by itself: it waits until you resume it in the app or with the “Resume” button in the extension’s pop-up. Before it takes an item from the run, and when you open its pop-up, it checks whether this browser is signed in to Vinted: it sends one background request to Vinted with the Vinted cookies the browser has, and reads from the response only its status and the address where it ended — not its content — and keeps one word from that (signed in, signed out or “unknown”), which it shows in the pop-up and in the Flikki app.

Price change. At your instruction in the Flikki app, the extension also changes the price of your listings that are already on Vinted: it opens the listing, goes to edit it, enters the new price and saves the change. It then checks on the listing’s page whether the new price can be seen. We change the price in Flikki only when the new price is visible on the page of that same listing, or when you confirm in the app that it is already there.

Refreshing a listing. At your instruction in the Flikki app — only once we switch this feature on, and only for listings posted at least 14 days earlier — the extension deletes your old listing on Vinted and lists the same item again from the current details in Flikki, one item at a time, at the same pace as listing. It first opens the old listing and checks that it really is that one (its number and title); if it is not sure, it deletes nothing. Just before pressing “Delete” and before listing the new one, it asks the Flikki server whether it may. After deleting, it checks on the old listing’s page that it is gone. The old listing loses its favourites and views. If Vinted asks for confirmation that you are human, the extension clicks nothing there and pauses the run.

What it downloads and sends.

It downloads from the Flikki server the details of one item (title, description, price, category, size, condition, colours, materials, brand) and its photos — from signed addresses valid for 15 minutes — and enters them into Vinted’s form in your browser.
After adding the listing, it sends Flikki its address and number on Vinted and what it entered into the form, including the value read from the form where we leave the choice to Vinted (for example the category Vinted suggested).
For a price change, it downloads from the Flikki server the address of the listing on Vinted, the item’s title (it shows it in its pop-up) and the new price. After saving, it reads the price visible on the listing’s page, but only compares it with the new price in the browser and does not send it. It sends Flikki the listing’s address, the new price entered and whether the new price was visible. If it was not, or if after saving the page of a different listing opened, it sends the same as for any failed step (next point).
For a refresh, it downloads from the Flikki server the address of the old listing on Vinted and the title it was listed with, and, to list it again, the item’s details and photos as for any listing. It compares the title visible on the listing’s page with that title in the browser and does not send it. It sends Flikki a request for permission before deleting and before listing (only the task number), then that the old listing is gone or the reason it did not delete it, and after listing the same as when adding any listing.
When a step fails, it sends the path of the form’s page (without parameters and without the title Vinted adds to the listing’s address — only the number stays), its structure (the names of fields and page elements, without text and without values) and a description of the element it did not find (up to 300 characters). That description may contain the category or brand of your item, if that is what it was looking for in the form.
It also sends reports of what stopped the run: Vinted’s sign-in page (the path only), when refreshing — Vinted’s request to confirm that you are human, no permission to access Vinted, a closed tab, a needed extension update, an invalid description of the form, and, for an error in the extension itself, the first line of the error message (up to 200 characters). With each report it marks whether it happened during listing, a price change or a refresh.
With every result and report it includes the extension version and the browser name with its version number (for example “Chrome 128”) — not the full browser description.
It does not read cookies or passwords and does not read pages other than Vinted. It connects only to Vinted’s pages, the Flikki server and — to download the items’ photos — Flikki’s photo storage at Cloudflare (section 6).

The listing you add, the new price you set and the deletion of the listing you refresh go to Vinted. What happens to them on Vinted is Vinted’s responsibility, under its privacy policy.

Companies that process data on our behalf. Each gets only what it needs for its task and acts under a data processing agreement.

Hosting provider — the servers Flikki runs on, the database and our websites. It stores all the data described in section 3.
Cloudflare (Cloudflare, Inc., USA) — the R2 service: storage of item photos and data export archives (until they are deleted, section 8).
Resend (Resend, USA) — sending emails (over SMTP): with a sign-in link, with a warning that a password was added, changed or removed, with a link to a data export (the link leads straight to your archive), with confirmation that the account was deleted, the weekly reminder about items that have been on Vinted for more than 30 days (with their names and prices), and messages to the team’s inbox.
Provider of the team’s email inbox ([email protected]) — it receives your messages from the app, with your account’s email address as the reply-to address, the content and the technical data; your replies to our emails; aggregate notifications of failures of Vinted’s form, without account data; and notifications of refunds, disputes and payment problems — with the account identifier, Stripe identifiers (including the customer identifier) and amounts.
Google (the Gemini API service) — recognising items in photos and writing suggested titles, descriptions and prices (section 4). It receives the photos, the item’s details and your note, never account data. It processes them as a processor, under Google’s data processing terms for services in which Google processes data on behalf of the customer (Data Processing Addendum).

Payments — Stripe and Link. Payment for Mini, Pro and Max is handled by Link, a Stripe service, as the seller in this payment. When you go to payment, we pass Stripe your account’s email address (or, if you have paid before, your customer identifier at Stripe), our account identifier, the chosen plan and billing period, and the language of the payment page. You give your card details, full name, billing address and the rest of the data needed for the payment directly to Stripe — we do not receive them. Stripe and Link process this data as a separate controller, under the Stripe and Link privacy policy: they send you emails about payments (receipts, invoices, refunds, renewal reminders), handle payment matters and disputes with banks, protect payments against fraud, and on link.com you can see your payments and manage the subscription. Stripe keeps its own customer record, which does not disappear together with the Flikki account. You can ask Stripe to delete your payment data and Link account — Stripe then cancels the subscription bought through Link and deletes that data, also from our Stripe account.

Google — ML Kit in the phone app. The Google ML Kit library (section 4) sends Google diagnostic data about the device and about how its features work, without photos and without account data.

Signing in with Google or Apple (today only on app.flikki.app). If you choose this method, Google or Apple learns that you are signing in to Flikki, and passes us your email address, account identifier and name. It does so as a separate controller, under its own privacy policy. The Google or Apple script loads only when you click the button to sign in with Google or Apple on the sign-in page.

Vinted. What you list through the extension goes to Vinted at your instruction (section 5). Vinted is a separate controller of that data.

Authorities and courts. We may hand over data when the law requires it, at the request of an authorised body.

Who in the Flikki team sees what. People with administrator rights see — to the extent needed to handle requests and protect against abuse: the email address, nickname, whether the address is confirmed, sign-in methods, language, country and currency, the plan and the use of limits, the subscription (with the customer identifier at Stripe) and granted plans, the numbers of items, batches, sales, runs, listings and messages, the total of sales, signed-in devices, the reason for a block and the history of administrators’ actions; your messages to us with the technical data; aggregate answers to the questions after sign-up; reports from the extension assigned to the account (the page’s path, the description of the element — which may contain the item’s category or brand — the form’s structure, the first line of an error). The titles, descriptions and photos of your items are not in the administration panel.

7. Data outside the European Economic Area

Cloudflare and Resend are companies from the USA, and the data we entrust to them may be processed in the USA — according to Resend, data from its service is stored in the USA. Google, under the Gemini API terms, may store data from requests transiently or in a cache in any country where it has infrastructure — including outside the EEA. We base such a transfer on the European Commission’s decision finding an adequate level of data protection under the EU-US Data Privacy Framework — for companies that have joined that framework — and on the standard contractual clauses approved by the European Commission, which are part of these companies’ data processing agreements (Article 45 and Article 46(2)(c) GDPR). You can get a copy of these safeguards by writing to [email protected].

Stripe, Apple and Google — for sign-in and in the ML Kit library — transfer data outside the EEA as separate controllers, on the terms described in their privacy policies.

8. How long we keep data

Account. As long as you have an account. You delete the account in settings; within 30 days you can come back by signing in with the same email address — with a link, a password (if you have one) or through Google or Apple. Connecting with a QR code does not restore the account. At deletion we stop a run in progress and cancel everything that was waiting to be done in the background — for example descriptions to be written, preparing freshly uploaded photos, a data export or sending your message to the team’s inbox; that does not come back with the account. We cancel the subscription (monthly or yearly) in Stripe straight after deletion; if you come back before that happens, the subscription stays. Minis you bought and granted plans stay. After 30 days we erase all the account’s data, photos and the payment data we hold (if the cancellation of the subscription in Stripe is still in progress, we wait until it finishes). What remains is an entry that the account was erased: a hash (SHA-256) of its identifier and the dates of deletion and erasure. This is pseudonymised data, not anonymous data: someone who knows the account identifier can match it to the entry.

After the account is erased, these also remain: entries in the administration log — not linked to the account, but with the text of a block reason or a plan note, if there was one; logs, until the end of their retention period; messages in the team’s inbox; emails we have already sent; and the customer record at Stripe, if you paid.

Items and what you delete one by one. A deleted item, photo, batch, sale or listing does not disappear from the database at once — it is hidden until the account is deleted. Only an item can be restored; you cannot restore a deleted photo, batch, sale or listing in the app. Deleting a batch for good detaches the items from it. A cleared description is erased at once. A touched-up version of a photo that you replace or undo is erased after 24 hours.

Other data:

Runs and their progress — 90 days after the run finishes or is stopped; a run that never started stays until the account is deleted. The information that an item was listed (the listing’s address) stays in your inventory.
Data export archive — the link works for 24 hours; we erase the archive within an hour after the link expires.
Photos uploaded but not assigned to any item — 24 hours; photos from an unfinished photo session on the phone — up to 7 days.
Sign-in link — valid for 15 minutes, works once; the entry with the email address, name and language is erased an hour after it expires, also when the sign-up was not finished.
QR code for connecting a device — valid for 90 seconds (once scanned, it gets a minute for each further step); we erase it an hour after it expires.
Signed-in device — the session expires after 180 days of no use on the phone and after 30 days in the browser and in the extension; each use extends this time. The entry about the device, also a disconnected one, is hidden until the account is deleted.
Traces of sign-in attempts and other limits — an hour. The entry about failed sign-in attempts — 2 days after the last failed attempt; the block itself lasts at most an hour.
Reports from the extension — 30 days. Aggregate reports of failures of Vinted’s form — while the failure lasts, and 180 days after it is fixed.
Messages to us, answers to the questions after sign-up, the days you used Flikki, limit counters, the history of suggestions, payment data — until the account is deleted.
The server’s task queue (including the content of messages to us before they reach the team’s inbox) — 7 days after the task is done, or 30 days if it failed, together with its data; for a failed task we record only the type of error, without its content. The record of responses to repeated requests (so that a repeated request does not do something twice) — 24 hours.
Identifiers of notifications from Stripe — 90 days.
Server logs — 30 days; the security event record — 400 days.
Messages in the team’s inbox — as long as we need them to handle the matter and to defend against related claims.
Reports of illegal content, complaints and withdrawals from the contract — until the limitation period for related claims expires.

9. Logs

We try to keep your data out of the server logs, and we do it like this: the record of a request contains only the method, the address pattern, the result, the time, the account identifier and the request number — without the IP address, the browser description and parameters. Before anything goes into a log, we cut out email addresses, paths and address parameters (including those of signed photo addresses) and tokens in the “Bearer” and JWT form, and we replace fields with names such as email, title, description, note, name, password, token or address with the mark “removed”. We deliberately do not log the content of messages to us, or what we send to Google in suggestion requests and what we get back from it.

We do not promise, however, that your data will never end up in a log: the full message of an unexpected error — for example from the database or when reading a response from Google — may contain a fragment of a title, description or suggestion, and the filter will not recognise tokens without such a form (for example from a sign-in link). These are gaps we have on record to fix. For a background task that failed, we record only the type of error, without its content.

When it fails, the extension does not send text or values from Vinted’s page — except what we describe in section 5 (the element’s description, the first line of an error).

10. Your rights

Access and a copy of your data — in settings you can download, free of charge and on any plan, a ZIP archive: JSON files with the data of your account, settings, sign-in methods, devices, items (including deleted ones), descriptions, photos (with touched-up versions), photo sessions on the phone, batches, sales, listings, correction requests, runs, suggestions, your own category assignments, limits, subscriptions, granted plans, exports, the days you used Flikki and the answers to the questions after sign-up; CSV files with items and sales; the photo files in the form in which we store them (cleaned, section 4), and their touched-up versions. We will email you the link to the archive; it works for 24 hours. The archive does not include: messages to us, reports from the extension, the security event record, the reason for a block, team notes, Stripe identifiers or records of refunds and disputes — you can ask for these by writing to [email protected].
Rectification — you change your nickname, items and settings in the app. You cannot change the email address in the app — write to us.
Erasure — you delete the account in settings (section 8). You can also ask by email for individual data to be erased.
Restriction of processing — you can ask for it, for example when you contest the accuracy of the data.
Objection — you can object to processing based on our interest (point f) by writing to [email protected]. We will stop, unless we show compelling grounds that override your interests, or the data is needed to defend against claims. You turn off the reminder about items that are not selling in settings, without writing to us.
Data portability — this is the same export: JSON and CSV files that any program can open.
Complaint — you can lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland) or with the supervisory authority in the country where you live or work.

We reply to messages about data within one month at the latest. We may ask for a message from your account’s email address, to make sure it is you writing.

11. Cookies and browser storage

Our website does not use cookies or anything that is stored on your device, and loads no scripts from elsewhere. It has no analytics.
app.flikki.app does not use cookies. In the browser’s storage (localStorage) it keeps the token that keeps you signed in, the chosen language, the last choice of department (who the item is for) on the add screen and the number of the data export you are waiting for; in the tab’s storage (sessionStorage) — the page you return to after signing in, and whether the questions after sign-up are behind you. All of this is needed for the app to work, so we do not ask for consent. There are no analytics or ads there. If you click sign-in with Google or Apple, their script loads on the sign-in page and works under their rules. The payment page belongs to Stripe and works under Stripe’s rules.
The phone app keeps the sign-in token in the system’s secure storage (Keychain on iPhone, Keystore on Android). It saves the sales export file temporarily, only until it is shared, and deletes it at the next export and when you sign out.
The extension keeps the data described in section 5 in the extension’s storage in the browser.

12. Security

We keep passwords as Argon2id hashes; session tokens, sign-in links and device-connection codes only as SHA-256 hashes; the traces of limits as hashes with a secret key. The app connects to the database as a user that sees only the data of the signed-in account; background tasks, sign-in, the administration panel and the erasure of accounts work with permissions that do not have this restriction. Connections to Flikki are encrypted. We share photos at signed addresses that expire. If a personal data breach occurs that may seriously affect you, we will notify you of it.

13. Changes to this policy

We will email you about an important change to this policy before it takes effect. We give the version number and date at the top.

14. Contact

For everything to do with your data: [email protected].