Parlen

Obvestilo o zasebnosti

Različica: 2026-10-29-en33 · besedilo je v angleščini

Summary

  • Parlen is an AI assistant you message on WhatsApp or iMessage. To help you, it processes the messages you send it and the data you choose to connect.
  • We do not sell your data, we do not use it for advertising, and neither we nor our AI providers train AI models on it. On iMessage, our delivery provider Blooio has its own terms about this (section 8).
  • Nothing is sent or changed on your behalf (emails, calendar) without your explicit YES.
  • You can ask us at any time to show, export or delete your data.
  • This is an early beta: some features described here are still being built. The website shows which ones work today; everything else is described as planned.

1. Who we are

DOERS, dejavnost oglaševalskih agencij, d.o.o., Vesca 16, 1217 Vodice, Slovenija, Matična št. 7284187, ID za DDV SI99045362.
Contact: sandi@bistrisistemi.si

We are the controller of your personal data. We have not appointed a Data Protection Officer; please use the contact above for any privacy question.

2. What data we process

  • Early-access request: email, language, the ad or link you came from (UTM), an invite code, the time and version of the terms you accepted, your confirmation that you are 18 or over and understand that Parlen is an AI, your choice about product news, a one-time link to confirm your email (we store only its hash), and a salted hash of your IP address for abuse protection (we do not store the IP address).
  • Optional answers after you confirm your email: whether you want it for personal use, work or both, the first task you would give it, the app you write in most, and whether you want a WhatsApp message when your access opens. The first task is used only to plan which tasks we open first; it never goes into analytics.
  • Linking WhatsApp: when you send us your one-time START code, we store your WhatsApp number with your request.
  • Writing to us on iMessage: iMessage reaches us through our provider Blooio. We receive your iMessage address — your phone number or the email address of your Apple ID — and the messages you send. If you write from the phone number of an account whose WhatsApp you already confirmed, we link the two, so you can use either. You can also link the email address of your Apple ID to your account: write "poveži moj iCloud mail" ("link my iCloud email") from your phone, and within 10 minutes send the one-time code we give you from the device that writes from that email. We keep only a hash of the code and when it was made and used, for 30 days. We confirm the link in both chats and show the address in part there. Messages from that address then belong to your account, and we answer where you last wrote from. Write "odstrani povezan iCloud mail" ("unlink my iCloud email") from your phone to remove it. Everything else is the same as on WhatsApp. We tell you about Blooio here and in the Terms rather than in the first chat message.
  • Trying Parlen on WhatsApp or iMessage (trial): when you press “Text Parlen” on our website, we record your consent (the sentence shown next to the button, its version and the time), a salted hash of your IP address for abuse protection, and the hash of a one-time code that WhatsApp or iMessage then sends with your first message. If you write to our number without a code, we answer once with the same terms and you can agree by answering YES (DA) — or another clear yes, such as “ja”, “ok” or a 👍 on that message; then we record that consent without an IP address. If the prepared first message carries a short ad tag (for example “(g1)”), we record which ad or link it stands for, as a category, with the start of your account, and may use it to pick the first example we show you. From your first message with the code, or your YES, you have a trial account: your WhatsApp number or iMessage address and the same data as when using the service (below), limited to the features that work today and a small number of requests for a short time. We open only a limited number of new trials each day; when today's places are taken, we tell you so and do not start a trial. If we can write back to you on that channel, we then keep your WhatsApp number or iMessage address (not only its hash) and your language, only to send you one message when your place opens; that place is then held for you for 24 hours. We delete them when that time ends, after 7 days at the latest, or at once if you write STOP. If you send us an invite code in the chat, we check it and, until you answer YES, keep which invite you sent with the hash of your number or address; with your YES you get full access (no trial) even when today's places are taken, and the invite is recorded as used by your account (a code we share ourselves can be used by several people; we record each use). The person who shared the code is not told who used it; they only see that it was used, and we may tell them so in the chat. If you send the assistant your email address, it becomes your early-access request with the same consent and your WhatsApp number already linked.
  • Writing to us before you have access: we keep no content of your message, only a keyed hash of your WhatsApp number or iMessage address, the time of our automatic reply and of your STOP, the time we offered you a trial, the day we told you that day's trial places were taken, how many times you tried a START, trial or invite code that day (or, in the last hour, a code to link an Apple ID email), which invite code you sent while we wait for your YES, and a log entry for each automatic reply or failed code (without content), so that we answer at most once a day and respect STOP. All of this is deleted automatically after 12 months. These replies are pre-written, not generated by AI.
  • Using the service: your WhatsApp number and/or iMessage address, the messages and media you send the assistant and its replies, notes you ask it to remember, reminders, research questions, emails received at or sent from the assistant's email address, drafts, and a record of what you approved or declined. If you tell the assistant your name, we keep it to address you and to sign emails sent for you, and we use it for your personal assistant address (see the next sentences). If you have full access (not a trial) and tell the assistant your name when it asks at the start, we create a personal assistant email address from your first name (for example name@mail.parlen.ai, or name382@mail.parlen.ai with three random digits if that address is taken) and tell you in the chat. We do this only once and only if you never had a personal address. You can choose a different personal address later; a change takes effect only after your YES. We process the address we created, the address you chose, or the one we suggested from your name. Every recipient of an email the assistant sends for you sees this address. Your first, random assistant address stays yours as well. A personal address is easier to guess, so it may get more unsolicited mail. To protect you, after 30 emails in one day (Ljubljana time) from senders you never wrote to, we no longer store or announce further emails from such senders; their sender is not told. Emails that are verifiably from your own email address or from places the assistant wrote to for you (checked with the sender's domain authentication, DMARC) still get through.
  • Voice messages: if you send the assistant a voice message, our server fetches the recording from WhatsApp or Blooio and has it transcribed into text by OpenAI (section 8). Only the recording of that voice message is sent to OpenAI, and only for the transcription. We keep only the transcript, as the text of that message in your conversation, and it is then handled like a message you typed (section 4). We do not keep the recording, and we do not use your voice to recognise or identify you. Voice messages longer than 2 minutes or larger than 10 MB, and audio formats we cannot read, are not transcribed and are not sent to OpenAI. A yes, no or approval code in a voice message never approves anything that waits for your approval: you have to type it.
  • Watches ("tell me when …"): if you ask the assistant to watch something, we keep what you asked to watch, until when, and the outcome of each check. Most watches are checked once a day with a public web search (Brave, section 8). You can also watch two official public sources: ARSO weather warnings for one of ARSO's five regions in Slovenia (we keep only the region, checked up to four times a day, and which warnings we already told you), and the government's regulated petrol and diesel prices on gov.si (we keep the fuel, your price limit and the first price we saw). For these two, our server downloads the same public file for everyone; nothing about you is sent to ARSO or gov.si, and no search or AI model is used. We message you when the condition is met (for ARSO: once for each new warning), with the source's link.
  • Comparison pages: when you ask the assistant to find and compare things to buy, it can also make a comparison page of what it found and recommends (products, prices, shops, links, the shop's product image, notes) with the first name you gave it, at a private link sent in your chat (parlen.ai/r/…). Anyone you share the link with can open it. The page holds nothing else about you (no phone number, address or messages). Product images load directly from the shop's website when the page is opened, so that shop sees the viewer's IP address; we send it no other information. The page is deleted after 30 days, or with your account.
  • Draft edit pages: when the assistant asks you to approve an email, it may add a private link (parlen.ai/d/…) where you can see the recipients, subject and text of that draft and change the subject and text. The link works once and only while the draft waits for your approval (up to 24 hours); anyone you share it with can open it. Saving a change sends nothing: the assistant shows you the new draft in the chat and it goes out only after your typed yes there. We store only a record of the link (which draft, until when, whether it was used), never the text, and delete it as soon as it is used or expires.
  • Shared lists: if you ask the assistant to share one of your lists with another Parlen user, we use the phone number or email address you type to check whether that person uses Parlen. If they do not, nothing is sent to anyone and we keep only the fact that a check was made (not the number). If they do, we send them one message asking whether they accept; it shows your name (or, if we do not know your name, your phone number) and the list's name. Only after they answer YES can both of you see and change that one list, including who added each item (their first name, if known). Nothing else of yours (notes, emails, reminders, other lists, your conversation) becomes visible to them, and nothing of theirs to you. Either of you can stop sharing at any time by writing "stop sharing the list"; the other person is told in one short message, and the list stays with its owner.
  • Invites: after the first task in which Parlen actually does something for you (for example saves a note, sets a reminder or finds search results; a plain chat does not count) we create five personal invite codes for you, and one more each time someone you invited starts using Parlen (at most ten in total) (the code, its slot and whether it was used). We send them to you once in the chat and show them again when you ask. We record when we told you. The invite page shows the first name of the person who invited you, if they gave it. Full access that starts by itself is recorded with the reason (an invite, two such tasks, or the open beta).
  • Data about other people: your messages and emails may mention or come from other people (for example the sender of an email you forward, or a recipient you ask it to write to). We process this only to carry out your request.
  • If you connect Google: only the data covered by the permissions you grant (section 7).
  • Visiting our website: to see which ads and parts of the page help people start, the page sends our server a few events without cookies: that the page was opened, which parts you scrolled to, which button you tapped and whether Messages opened. They carry only the kind of device (for example iPhone), whether you came through the Instagram or Facebook in-app browser, the page language and the ad you came from (UTM). The events have a random ID made for that one page view and kept only in your browser's memory; we do not store your IP address with them. We forward them to PostHog as product analytics.
  • Technical data: error and security logs and product usage events. These never contain the content of your messages.

3. Why we process it and on what legal basis

PurposeLegal basis
Providing the assistant you asked for: replies, notes, reminders, research, drafts, and carrying out actions you approvedContract (GDPR Art. 6(1)(b))
Placing an order in a web shop that you asked for — a shop whose checkout we have checked, a shop you named or one a web search found for your request — and approved with YES (the shop receives your name, delivery address, phone number and your assistant email address and is responsible for your order as its own controller)Contract (GDPR Art. 6(1)(b))
Sending a booking or web form that you asked for and approved with YES (the website receives what the form holds)Contract (GDPR Art. 6(1)(b))
The free trial on WhatsApp or iMessage you started by clicking “Text Parlen” or answering YES, and your consent recordContract (Art. 6(1)(b)); keeping proof of your consent: legitimate interest (Art. 6(1)(f))
Managing the early-access list and invites, confirming your email, your optional answers and linking your WhatsApp numberSteps before a contract (Art. 6(1)(b))
A WhatsApp message when your access opens (only if you ask for it)Your consent (Art. 6(1)(a)), which you can withdraw at any time by writing STOP
Telling you when a trial place opens, after you asked for a trial and today's places were takenSteps before a contract at your request (Art. 6(1)(b))
Automatic replies to people who write to our WhatsApp number or iMessage address without accessLegitimate interest in answering and preventing abuse (Art. 6(1)(f))
Processing other people's data contained in your requestsLegitimate interest in providing the service you asked for (Art. 6(1)(f))
Sharing a list you or the other user asked for, and the one invitation messageContract (Art. 6(1)(b)); for the invitation before the person answers, legitimate interest in passing on a Parlen user's request (Art. 6(1)(f))
Security, abuse prevention, fixing errors, keeping approval recordsLegitimate interest (Art. 6(1)(f)); legal obligations where they apply (Art. 6(1)(c))
A short message from the assistant after two days without your messages (at most two in a row)Legitimate interest in helping you use the service (Art. 6(1)(f)); you can object at any time by writing "ne piši mi prvi" or STOP
Passing feedback you send to our team in the chat ("feedback: …") on to us by emailLegitimate interest in improving the service (Art. 6(1)(f))
Linking an Apple ID email you choose to your account, with a one-time codeContract (Art. 6(1)(b))
Product analytics without message contentLegitimate interest (Art. 6(1)(f))
Occasional product newsYour consent (Art. 6(1)(a)), which you can withdraw at any time

4. How the AI works with your data

Your requests are processed by an AI model from Anthropic, used through its business API. Voice messages you send are first transcribed into text by OpenAI, used through its business API (see section 8). Under their business terms these providers do not train their models on your data. We do not train models on your data either.

The assistant does not make decisions about you that have legal or similarly significant effects (GDPR Art. 22). It prepares answers and drafts; you decide.

Content from emails, websites and search results is treated as information, never as instructions. When the assistant writes to someone for you, it introduces itself as your AI assistant.

We send you messages you did not just ask for (reminders you set, notices about new emails to your assistant address) only after you asked for such a feature, with one exception: if you have not written to the assistant for two days, it may send you one short message in the daytime — for example about something you left open, a reminder coming up or a list — and, if you do not answer, at most one more at least five days later; then nothing until you write again. Our AI model provider writes it from your recent conversation (the last 14 days), your lists, reminders and watches, and the titles of comparison pages we made for you in that time; nothing else is used and we keep only the record that it was sent. Write "ne piši mi prvi" ("don't text me first") to turn this off, and "lahko mi pišeš prvi" to turn it back on. About five working days after an order the assistant placed for you (in a web shop, or by email once the shop has answered), we may ask you once whether the parcel has arrived, unless the shop's shipping email or your own message already told us; we use only the order record (the shop's website, its address, the order number shown by the shop and the date). If you answer that it has not arrived, the assistant prepares an email to the shop, which is sent only after your YES. We ask only once and never remind you about it. If a new email comes from an address the assistant emailed for you in the last 30 days, and its sender is verified (DMARC), the notice (when it is a normal message: always on iMessage, on WhatsApp within 24 hours of your last message) and the assistant, when it reads that email, say so and name the subject of that earlier email; this tells you who wrote, not that the email answers yours. Write STOP to turn them off and START to turn them back on.

5. Sensitive data

Please do not send the assistant health data, passwords, payment card details, or other special categories of data (GDPR Art. 9). If you send such data anyway, we process it only to carry out your request and do not use it for anything else; you can ask us to delete it at any time. The assistant is designed not to store passwords or card details as notes.

6. When a person may see your content

Nobody at Parlen reads your messages or connected data, except: (a) when you ask us to, for example for support; this includes feedback you send to our team by writing "feedback: …" in the chat, which we receive by email; (b) when needed to investigate abuse or a security incident; (c) when the law requires it.

7. Google user data

Connecting Google Calendar is optional and available to a limited group during the beta. Connecting Gmail is also optional, available to a limited group during the beta, and read only. We ask only for these permissions, and only when you connect:

PermissionWhy
openid, emailto know which Google account is connected
calendar.freebusyto see when you are free or busy, without event details
calendar.events.ownedto show your events and, after your YES, create, move or cancel them on calendars you own
gmail.readonlyto search and read your email when you ask; never to send, change or delete

Parlen's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is never used for advertising or to train AI models, and people do not read it except as described in section 6. This applies to Gmail too: the content of the emails you ask about is sent to our AI model provider (Anthropic, section 8) only to do what you asked about those emails: to find and summarise them, to list what they ask you to do (a reminder or calendar event is set only after your YES), or to help draft a reply you asked for. It is not used to train AI models or for advertising.

Parlen searches and reads your Gmail only when you ask it to. It never sends, changes or deletes anything in Gmail. If you want to reply, the assistant sends the reply only from its own email address and only after your YES, never from your Gmail. Attachments are not read. We keep no copy of emails from your Gmail in our database (section 10).

You connect through a one-time link sent in your chat with Parlen on WhatsApp or iMessage (valid 15 minutes). The connection becomes active only after you confirm in that chat, with the short code shown there, which Google account was connected. Parlen never invites or notifies other people and never changes events that other people organise or attend; every change in your calendar needs your YES first. You can disconnect at any time by writing "disconnect Google" or "disconnect Gmail" (either one ends access to both Google Calendar and Gmail): we then ask Google to revoke access (if Google cannot be reached, access ends on our side anyway), delete the access tokens immediately and delete cached Google data within 30 days (or sooner where Google requires).

8. Who receives your data

We use these service providers (processors). For Anthropic and Vercel, their data processing terms are part of the business terms we use them under; where we have not yet confirmed a provider's data processing terms, the table says so. Providers marked “planned” do not receive any personal data until the related feature starts working; we will update this list before that happens.

ProviderPurpose — where
Supabase (in use)database hosting — EU (Frankfurt)
Meta Platforms (WhatsApp Business Platform) (in use)delivering WhatsApp messages — EU and US
Blooio (in use)delivering iMessage messages between you and the assistant (your iMessage address and the message content). Blooio's own privacy policy says it stores message content while our account is active and may use it after the account is closed to improve its product, including training models. We have asked Blooio for a data processing agreement that excludes this; if you do not want your messages to pass through Blooio, use WhatsApp once it is available, or do not write to us on iMessage — US
Vercel (in use)website and application hosting (your messages pass through our application code there) — EU (Frankfurt) for the application; Vercel is a US company
Anthropic (in use)AI model (processing your requests, including the content of emails from your Gmail when you ask about them; Anthropic deletes inputs and outputs within 30 days, unless it must keep them longer to enforce its usage policies — up to 2 years — or by law) — US
Brave Search API (under Brave's Search API Data Processing Addendum) (in use)public web search for research tasks (the search query only, kept by Brave for up to 90 days; our servers block queries containing contact details, street addresses or sensitive data they recognise — such filters are not perfect) — US
OpenAI (OpenAI Ireland Ltd, under OpenAI's Data Processing Addendum with the Standard Contractual Clauses) (in use)transcribing voice messages you send the assistant into text: only the recording of that voice message is sent (not your other messages, notes or emails), and only for the transcription. OpenAI states that for this transcription service it keeps neither the recording nor the transcript for abuse monitoring or as stored application data, and it does not train its models on them — US
Browserbase (in use)a cloud browser for orders in web shops and for bookings and web forms that you ask for and approve — in a shop whose checkout we have checked, or on a website you named or one a web search found for your request: the pages the assistant opens and what it types there (your name, delivery address, phone number, email address, the date, time and number of people, your message). When you take over the browser through a secure link, what you type there (for example a password or card details) goes from that browser to the website; the assistant does not see it. Sessions are not recorded or logged. A browser runs only while the assistant works on your request (at most 10 minutes at a time) or while you use it through a secure link (at most 15 minutes); between steps Browserbase keeps only that browser's cookies (for example your cart, or a login you typed yourself) until the order or form is sent or cancelled; we delete them within 24 hours, and if our browser provider cannot be reached at that time we keep trying and our operator is alerted — EU (Frankfurt); Browserbase is a US company
Resend (in use)sending and receiving the assistant's emails, and our emails to you about your early-access request, and forwarding feedback you send to our team to us (sending region EU) — US and EU
PostHog (in use)product analytics without message content: events with a pseudonymous ID and categories only (for example which feature was used), sent from our servers, IP addresses anonymised — EU (Frankfurt)
Google (only if you connect Google Calendar or Gmail) (in use)access to your calendar data you choose to connect, and to your Gmail messages you ask about — EU and US

iMessage itself is Apple's service: messages between your device and our provider travel through Apple under Apple's own terms and privacy policy, as WhatsApp messages travel through Meta.

We do not sell your data and do not share it with advertisers. We disclose data to authorities only when the law requires it.

9. Transfers outside the EU

Our database is in the EU. Some providers above process data in the United States. Such transfers rely on the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses. You can ask us for a copy of the relevant safeguards.

10. How long we keep data

DataKept for at most
Early-access request (email, consent record, your optional answers, WhatsApp number once linked)if you are not admitted: 12 months; if you are admitted: kept with your account as the record of your consent
WhatsApp number or iMessage address of someone waiting for a trial place, with their language and when we added and told them (only to send that one message)until we tell you your place is open, then 24 hours while it is held for you; at most 7 days; deleted at once if you write STOP
Hashed WhatsApp number or iMessage address of someone who wrote to us without access, with reply/STOP times, code attempts, the time of our trial offer (and, to recognise a 👍 on it, the ID of that offer message, deleted with the offer, within 24 hours), the day we told you today's trial places were taken, and the log entries of our automatic replies (to limit our automatic replies and respect STOP)12 months after our last reply or your STOP, then deleted automatically
Trial account (WhatsApp number or iMessage address, messages, notes, reminders) if you do not request full accessdeleted automatically 30 days after the trial ends, with its trial consent record
Trial consent record (the sentence you agreed to, its version, time and how you agreed, and whether it came with an invite code)kept with your account as the record of your consent
Invite codes (the code, who shared it or a label we gave it, whether and when it was used (for a shared code: how many times), and which account used it)while the person who shared it has an account (our own codes: until we delete them); the link to the account that used it is removed when that account is deleted
A one-time trial code that was never used (only its hash and a salted hash of the IP address)7 days after the code expired (codes expire after 24 hours)
Messages with the assistant and the assistant's emails180 days, unless you delete them earlier
Voice messages you sendwe do not keep the recording: our server fetches it from WhatsApp or Blooio only to have it transcribed, holds it only in memory while that happens and never writes it to our database. Until then we keep only WhatsApp's or Blooio's reference to the recording, which is then replaced by the transcript or deleted. The transcript is kept as the text of that message, like every message (at most 180 days). OpenAI: section 8
Notes you ask it to remember, and remindersuntil you delete them or your account
Watches (what you watch, settings, check outcomes)while the watch is active; deleted 30 days after it ends, or with your account
Comparison pages of shopping research (what was found and recommended, your first name)30 days, then deleted; or with your account
Shared list records (who shares which list with whom, and its state)while the sharing is active; declined, expired or ended records are deleted after 30 days. If either account is deleted, the record is deleted with it. Items the other person added to your list stay on your list without a link to them
Record that a check-in message was sent or skipped (no content)12 months
Feedback you sent to our team in the chat12 months
Draft edit links (which draft, until when, whether used; no content)until used or expired (up to 24 hours), then deleted; or with your account
Codes to link an Apple ID email to your account (only a hash of the code, when it was made, expired and was used, and which address it linked)30 days after the code was made; the link itself stays until you remove it or delete your account
Approval records (what you approved, when) and security logs12 months; after that we keep only the short code of each approval, the kind of action, whether it was approved and its dates — no content and nothing derived from it — so that an old code can never approve anything new
Technical record that a message to you is being sent (only the time), to catch sends that may not have been recordeduntil the send is recorded; at most 7 days
The steps of a web-shop checkout the assistant filled in (which field got which of your delivery details, the shop's page addresses, including the full address of the first page with its parameters, so the order can be repeated exactly) and the delivery details you approved for ituntil the order is placed or cancelled, at most 24 hours
The steps of a web form the assistant filled in (which field got which value, page addresses, including the full address of the first page with its parameters, so the form can be repeated exactly) and the values you approveduntil the form is sent or cancelled, at most 24 hours
Records of browser sessions for web-shop orders, bookings and web forms (start and end time, the website's address, the text of the boxes the assistant ticked for you)12 months
A secure browser link: a hash of its token and of the cookie that ties it to the phone that opened it, the encrypted addresses of the live browser session and of the page to continue on, its status and timesthe live session's address is deleted when you finish or after 15 minutes, the page to continue on when the assistant continues there or the attempt ends; the rest for 12 months (security records)
A shop's or website's cookies (for example your cart) kept by our browser provider between the steps of an order, booking or web formuntil the order or form is sent or cancelled; we delete them within 24 hours, and if our browser provider cannot be reached at that time we keep trying and our operator is alerted
The cookies of a browser session you took over (including a login)until the attempt ends (at most 3 hours), then deleted; as with a shop's cookies, within 24 hours at the latest, and if our browser provider cannot be reached at that time we keep trying and our operator is alerted
The web address of a shop you ordered from or of a website you sent a booking or web form to, so that its emails to your assistant address are shown to you word for word and to tell you if its email has not arrived yet30 days after the order or the form
Your personal assistant email addresses (the current one and earlier ones)while your account exists. Earlier personal addresses keep receiving mail for you and are never given to anyone else. When your account is deleted we delete them; we keep only a one-way fingerprint (a hash) of each address, stored without your account or any other data about you, so that the address is never given to another person and mail meant for you never reaches someone else
Emails read from your Gmailwe keep no copy or cache in our database: they are used only while the assistant answers you. To answer, their content is sent to our AI model provider, which keeps it as described in section 8. Its answer (for example a summary or the list of what you need to do) stays in the conversation like every message (at most 180 days); a reminder is set only after your YES
Google access tokensdeleted immediately when you disconnect Google or delete your account
Data cached from Googledeleted within 30 days after you disconnect Google
Backups made by our database providerup to 30 days, then overwritten
Analytics events (no message content)24 months, then we delete them at the provider

During the beta we carry out the other deletions after these periods ourselves, until automatic deletion is in place for them too.

11. Security

Data is encrypted in transit; OAuth tokens are also encrypted at rest. Each user's data is separated from every other user's at the database level. Access by our staff is limited to what is needed to run and support the service.

12. Your rights

You have the right to access, correct, delete, restrict and export your data, to object to processing based on legitimate interest, and to withdraw consent at any time. Write to sandi@bistrisistemi.si. We answer within one month.

You can also delete your account yourself: write "delete my account" in the chat and confirm with the code we send you.

You can also complain to a supervisory authority: in Slovenia the Information Commissioner (Informacijski pooblaščenec, ip-rs.si), in Croatia AZOP (azop.hr), or the authority in the country where you live.

13. Deleting your account

When you delete your account, we delete your messages, notes, reminders, drafts and connections within 30 days, except records we must keep by law or for the periods in section 10 (for example approval and security logs). Your assistant email addresses stop working: mail sent to them afterwards is not delivered to anyone. A personal address you chose is never given to another person (we keep only its one-way fingerprint, see section 10). You can ask for an export of your data before deletion.

14. Cookies

The website does not use advertising or tracking cookies. Analytics run on our servers and do not set cookies in your browser.

15. Age

The beta is for people aged 18 or over.

16. Changes

We will tell you about material changes at least 30 days before they apply. We will never start using your data for a new purpose that requires your consent without asking you first.

17. Contact

DOERS, dejavnost oglaševalskih agencij, d.o.o., Vesca 16, 1217 Vodice, Slovenija, Matična št. 7284187, ID za DDV SI99045362.
Contact: sandi@bistrisistemi.si