Privacy policy
Effective from:
The binding version of this document is the Slovak one at /sk/ochrana-osobnych-udajov/. This English text is a courtesy translation; in case of any discrepancy the Slovak version prevails.
This document describes what personal data we process while running Faktura365, why, on what legal basis, and who we share it with. It covers the website and the Faktura365 mobile apps for Android and iOS alike — they are the same service and the same account. It is written to be read, not to put you off.
Who we are
The controller is Volodin s. r. o., Račianska 1579/88B, 831 02 Bratislava, Slovakia, company ID (IČO) 57105961, entered in the Commercial Register of the Municipal Court Bratislava III, section Sro, insert no. 190122/B.
For anything about personal data, write to info@faktura365.sk. We have not appointed a Data Protection Officer — the obligation does not apply to us.
Two different roles — and the difference matters
For your account data we are the controller: we decide why we need it.
For the data you type into invoices — your customers, their addresses and the amounts — YOU are the controller and we are the processor. We only store it and show it back to you; we do not use it for anything of our own, and we hand it over only where you yourself send it — to your customer by email or, if you use e-invoicing, through the certified delivery provider — and to that provider for the checks described under "E-invoicing". The terms of that processing are in article 9 of the Terms of Service.
Account data we process
Of the data we ask you for, only an email address and a password, or a Google sign-in, are required to create an account — without them no account comes into being. A sign-up by email also requires your first and last name. Your phone and company details are voluntary; without the company details, however, you cannot issue a document. The rest of this list arises automatically as you use the service.
- Email — signing in, verifying the address, resetting the password and service messages. Legal basis: performance of a contract, Art. 6(1)(b) GDPR.
- Password, only as an irreversible hash (PBKDF2) — signing in. Performance of a contract.
- First name, last name, phone, interface language — prefilling documents and setting up the interface. Performance of a contract.
- Profile picture — only if you sign in with Google, and it comes from Google. Performance of a contract.
- Number of visits, the date and time of the last visit, and the account creation date — security, support and abuse prevention. Legitimate interest, Art. 6(1)(f) GDPR.
- How many times your company opened some of the application’s documents and windows — the delivery note, the payment receipts, the cash document and the Links window — per day, and whether from the invoice page or from a list, and how many times it opened the e-invoicing connection page and pressed its connect button. The content of the documents is not recorded. Improving the service and support. Legitimate interest, Art. 6(1)(f) GDPR.
- The date you accepted the terms of service and this policy, together with the identifier of the wording you accepted — performance of a contract, and proof that we informed you.
- Your IP address when signing in, registering or resetting a password — limiting the number of attempts, that is, protection against password guessing and against mail being sent to addresses that are not yours. All we keep is a counter of attempts tied to the address; it is valid for at most an hour, and its row is deleted the next time the table is swept. The same kind of counter, this time without being written to the database, limits company lookups in the registers. Legitimate interest, Art. 6(1)(f) GDPR.
Data you enter yourself
Your companies, customers, price-list items, bank accounts, invoices and the payments against them. We keep them for as long as your account exists. We do not use them for advertising or profiling. We do not pass them to third parties — other than the processors listed under "Who we share data with", an e-invoice you send yourself, and the people you give access to your account yourself (see the next section).
People you give access to your account
You can add other people to your account — your accountant or a colleague, for example — and give them a role: editor (documents, companies, contacts and the price list) or view only. You can add only someone who already has a Faktura365 account of their own with a confirmed email address: you enter the email they sign in with. Only you add and manage the people of your account. The person added then sees the data of your account — your companies, contacts, price list, documents and payments — and, depending on the role, can change it. Who gets such access is your decision, and you can change or remove it at any time.
When you add someone, all we store is that the person is a member of your account, and their role. If the email you enter belongs to no account, or is not confirmed yet, we store nothing and only tell you so; the number of such checks is limited. We email the person added that they now have access to your account; Resend delivers it, it names you and the role, and a reply goes to your address. It counts towards the daily sending limit. Legal basis: towards you, performance of a contract, Art. 6(1)(b) GDPR; towards the person added, the legitimate interest in letting you work together in the service, Art. 6(1)(f) GDPR.
If somebody else gave you access to their account, you see their data to the extent they set, and you can end that access yourself at any time. They are responsible for the data in their account; this does not open your own data or your own account to them.
Email we send you
Service messages — a welcome message or address verification when you sign up, password reset, notices about your account — go to every user. They are part of the service; the legal basis is performance of a contract, Art. 6(1)(b) GDPR, and the only way out of them is to delete the account.
A one-off offer of help — if your email address is confirmed, we send you at most one such email: on a weekday morning, two to six days after you sign up if your account holds no document yet, not even a draft, or seven to twelve days after you sign up if it holds exactly one. In it we ask whether something is missing or not working. All we check is how many documents there are, never what they contain. The legal basis is our legitimate interest in the service being usable, Art. 6(1)(f) GDPR; if you would rather not receive it, write to info@faktura365.sk.
The newsletter — invoicing tips, changes to the rules and product news, roughly once a month — goes only to people who explicitly ask for it by turning the switch on during sign-up or in the account settings. The legal basis is your consent, Art. 6(1)(a) GDPR together with § 116 of Act No. 452/2021 Coll. on electronic communications. Consent is not a condition of using the service.
You can withdraw that consent at any time — with the switch in your account settings or the link at the bottom of every such email. Withdrawal works for the future and does not affect the lawfulness of what we sent before it.
We keep a record of your answer: what you answered, when, where from (sign-up, settings, the unsubscribe link), in which language, and which version of the wording you were shown. Without it we could not demonstrate that we had consent, which is what Art. 7(1) GDPR requires of us. We do not store your IP address or details of your browser alongside it. The record lives for as long as your account does and is deleted with it.
Documents you send to your own customers — if you choose to email a document, Cloudflare delivers it to the address you enter; if Cloudflare does not accept it at that moment, Resend delivers it instead. The email carries either the document as a PDF or a link to it, plus your short note if you add one. It is sent in your company's name, and the customer's reply goes to the email address on the document or, where there is none, to your account's email address — so the customer will see that address. We do not store the customer's address beyond what is already on the document itself; all we keep in your account is a count of the emails sent this way. In this relationship you are the controller and we are the processor — the same role the "Two different roles" section above describes.
A link to a document is signed and has no expiry: anyone holding it can open it without an account with us, so that the document is still there a year later when your customer's accountant needs it. That is why you can cancel it at any time with "Cancel the link" on the document; cancelling stops every link to that document you have handed out so far.
E-invoicing
An e-invoice — an invoice in a structured electronic format under Act No. 222/2004 Coll. on value added tax, as amended by Act No. 385/2025 Coll. — may be sent and received only through a certified delivery service provider. Ours is Efakturuj, s. r. o. (the Efakturuj service), established in Bratislava and entered in the register of providers kept by the Financial Administration of the Slovak Republic. Until you switch e-invoicing on yourself, it receives neither your company's details nor your documents from us; the one exception is the customer check described below.
Connecting a company — when you connect your company, we hand the provider its name, company ID (IČO), tax ID (DIČ), VAT ID (IČ DPH), address, e-mail and phone number from the company card; the provider compares the e-mail and phone with the ones you enter on the portal of the Financial Administration. You then choose the provider as your digital postman (digitálny poštár) on the portal of the Financial Administration of the Slovak Republic — a step the law puts on everyone who receives e-invoices. What you enter there, on the portal or on the provider's pages, does not reach us; the provider processes it as an independent controller under its own policy. We store only which step of the connection the company is at, the identifier the provider keeps it under, and the access credentials the provider issues for the company to send and receive e-invoices — those in encrypted form.
Sending an e-invoice — if you choose to send a document as an e-invoice, we hand the provider its whole content: the details of your company and of your customer, the items, amounts, dates and payment details. The provider delivers it to your customer over the Peppol network and reports the invoice data to the Financial Administration of the Slovak Republic, as the law requires. A sent e-invoice cannot be recalled. We keep a record of each sending: the document number, the customer's name, their network address, the time and the delivery status — and the customer's response (an acceptance, a rejection or a question, with their text), if they send one through the network. We also keep an exact copy of the XML file that was sent, that is, the whole content of the document as it left.
Checks at the provider — when you open the e-invoice sending window, and again when you send, we have the document checked by the provider's validator, when it is available, and check whether your customer is in the Peppol network. We show you the result and use it to find faults, and we may stop a document that fails. The validator only checks the document and does not store it. When a document passes, all we keep is that it passed, when, and a technical fingerprint of the file that tells us the document has not changed since; an edited document is checked again. Our administrator may run the same check for support and fault-finding, on documents of companies connected to e-invoicing, even if you did not mean to send the document; this delivers it to nobody. For a company connected to e-invoicing, the administrator may also re-check the state of its activation at the provider; the provider then receives only the identifier it keeps the company under, and this delivers nothing to anyone. The administrator may also move such a company’s activation forward; if the provider confirms it as verified at that moment, we register it in the Peppol network and e-mail the account owner that the company is connected — the same as when you finish connecting it yourself. The administrator may also check whether your customer is in the Peppol network: the provider then receives only the customer's DIČ or network address, even if you have not switched e-invoicing on. We run these checks as your processor, on your instruction under article 9 of the Terms of Service.
Received e-invoices — documents your suppliers send you are taken over from the provider when you open the list of received e-invoices; a customer's answer to an e-invoice you sent arrives the same way. We store the content of the document so that we can show and print it for you: the document number, the details of the supplier and of the customer including contact persons, the supplier's network address, the dates, the items, the amounts and the tax breakdown, the supplier's payment details (account number, payment reference), the order and contract numbers and the note — and the status you give the document yourself (to confirm, confirmed, rejected), and the payments you record against it (amount, date and payment method). We also keep the original XML file as it arrived — including any attachments the supplier embedded in it — so that it stays available to you even if we change the delivery service provider. A confirmation is your own note and we do not report it to the supplier. If you reject a document, we send the rejection, with the reason you write, to the supplier through the delivery provider — if their side accepts such responses; we store the reason and the time it was sent. Where our provider does not pass rejections on through the network, you may instead send the supplier an e-mail with the document's number, date and amount and your reason: Resend delivers it to the address you confirm in the rejection dialog (we prefill the supplier's e-mail from the document or from their contact), your company is the sender, and the supplier's reply goes to your company's e-mail, or to your account's e-mail if the company has none. We store the address the e-mail was sent to and the time. We also save the supplier among your contacts — the name, company ID, tax ID, VAT ID, address, phone, e-mail, account number and register entry from the document, and its network address — marked as having sent you an e-invoice. If you already have a contact with the same tax ID, we update these details on its card from the latest document; the contact person, the website and the note are left as they are, and the e-mail is filled in only if the card has none. Whether the supplier is a VAT payer we check automatically in the OpenData service of the Financial Administration by its VAT ID. You can edit or delete the contact at any time. Where we cannot print a document ourselves, we also store its PDF form as drawn by the provider.
For the content of sent and received e-invoices you are the controller, we are the processor and the provider is our sub-processor — the same role the section "Two different roles" above describes. The legal basis for processing your account and company data for this purpose is performance of a contract, Art. 6(1)(b) GDPR.
The invoice generator without an account
The finished invoice is produced inside your own browser. Neither the document nor its contents is sent to our server, and we do not store it.
The invoice you are still working on is kept in your browser's local storage, so that closing the page does not lose it. It stays on your device and is not sent anywhere. After 30 days we stop using it — the next time the generator is opened it is deleted; sooner than that, the button that clears the form removes it, as does clearing the site's data in your browser. Until you open the page again, it stays in your browser.
There is one exception: company lookup. If you have the details filled in from a register, the query (a name or an IČO) passes through our server — see the next section.
If you decide to create an account from the generator, we carry the draft into the sign-up form in the part of the address that is never sent to a server, and store it only once the account exists — at which point it becomes ordinary account data. Without that step of yours, no data of yours and nothing from the document reaches us.
When you download the finished invoice, we add one to a count of our own — all we follow is how many documents the generator has produced. We store no name, no cookie and nothing else that could tie that counter to you or to what the document says. Your IP address — as with any request to a website — is seen by our server and used only to limit abuse; it is not written to the database.
Company lookups in the registers
When you have a company or a customer filled in from a register, we send your query to public sources of Slovak company data: the Register of Legal Entities (RPO) of the Statistical Office, the Commercial Register, and the OpenData service of the Financial Administration for checking VAT-payer status. Only one query is sent without a step of yours: when we take over an e-invoice from a supplier, we check in the OpenData service of the Financial Administration whether the supplier is a VAT payer — sending only the supplier's VAT ID, nothing about you or the document.
Searching by name is served by ORSF (orsf.sk) — a private project, its server in Germany, which republishes those same state registers as a search index. It is not a state register and we would rather say so plainly; we use it because it answers a name in a fraction of a second instead of several. The address and the register entry that get printed on the invoice we ask RPO for directly in the first place; when RPO does not answer, we fill them in from ORSF — otherwise the document would go out missing a mandatory particular. So do check the prefilled details before you issue a document: they are your responsibility.
Only what you typed leaves (a name or an IČO), and it leaves from our server — those sources receive neither your IP address nor anything about your account. We use the answer to prefill the form and we do not store the queries against your account.
Suggestions for improvement
If you send us a suggestion from inside the application, it reaches us by email together with your email address and your account identifier — otherwise we could not reply to you. Resend delivers that email to our address, Cloudflare forwards it to our mailbox, which is operated by Google, and the message stays there for as long as the subject is open. Legitimate interest in improving the service and in answering you, Art. 6(1)(f) GDPR.
When something in the application breaks
So that we learn about a fault before you have to tell us, we send a report about it to Sentry. It carries a technical description of the error and the place in our code, the address of the page it happened on, the version of the application, the type of your browser and operating system, and the identifier of your account if you are signed in.
We do not put your name, your email address or the contents of your invoices into the report (the one exception for the email address is described below), and links that open something by themselves — address verification, password reset, signing in with Google, and a link to a document shared with a customer — are stripped out of the address before it is sent. Storing IP addresses is switched off in Sentry. Reports are kept for 30 days and then disappear.
The exception: if an e-invoice fails the delivery provider's check before it is sent, the report also carries the email address of the signed-in user, the identifiers of the rules it broke (for example BR-25), the identifiers of the document and the company, the document type, the currency and the number of lines, so that we can reach you and help put it right. Even then we put nothing else of the invoice into the report.
Legitimate interest in keeping the service working and in being able to fix a fault, Art. 6(1)(f) GDPR.
Export for couriers
From your issued documents you can put together a file for a carrier (Packeta, SPS, DPD, GLS, Slovenská pošta, DHL, UPS or a universal CSV/XLSX) — you download it and upload it to the carrier's portal yourself; on that route nothing leaves us for the carrier. On the document we store which carrier you exported it to and when, so that you do not send it twice by mistake, and on the company the last export settings (weight, pickup point, sender label and the Packeta API key), so that you do not have to type them again. We keep them for as long as the document, or the company, exists in your account. Legal basis: performance of a contract, Art. 6(1)(b) GDPR.
You can search a carrier's list for a parcel's pickup point. Only when you open the search does your browser load the list or map directly from the carrier — Packeta (widget.packeta.com, together with your company's API key), SPS (balikomat.sps-sro.sk), DPD (api.dpd.sk) and GLS (map.gls-slovakia.com); Slovenská pošta's list of post offices is passed on to you by our server. We send the carrier only the language, nothing from your documents and nothing about your customers; it does receive what a browser hands over whenever it loads something (e.g. the IP address), and Packeta may show its own cookie bar. For that each of them is an independent controller under its own privacy policy.
You can also send parcels straight to a carrier through its API (Packeta, Slovenská pošta, GLS, SPS, DPD, Zaslať.sk). First you enter the access details of your own account at the carrier; we check them with the carrier and store them encrypted, so they are not shown to you again — you see only a shortened form, and you can change them or disconnect at any time, which deletes them. Only when you press send do we pass the carrier, for the documents you picked, the data a delivery needs: the recipient's name and address, phone and email, the cash-on-delivery amount with its variable symbol and the account it is paid out to, the parcel's value and weight, the document number, and your company as the sender. The carrier gives us back the parcel number and the label; we store the number on the document and only hand the label to your browser. In this we act on your instruction as your processor; the carrier is in a contract with you and processes the data further as an independent controller under its own policy. We keep the access details until you disconnect or for as long as the company exists, and the parcel numbers for as long as the document exists. Legal basis: performance of a contract, Art. 6(1)(b) GDPR.
Who we share data with
Our processors, and nobody else. We do not sell data and we do not hand it to advertising networks.
Besides them, the carriers Packeta, SPS, DPD and GLS — only when you open the search of their pickup points yourself — and a carrier you have connected yourself (Packeta, Slovenská pošta, GLS, SPS, DPD or Zaslať.sk), only with the parcels you send it (see "Export for couriers").
- Cloudflare, Inc. — hosting of the site, the application, the database and the e-invoice file storage, delivering the documents you email to your own customers, and forwarding email sent to our addresses (your suggestions for improvement included) to our mailbox. EU/US, Standard Contractual Clauses.
- Resend (Plus Five Five, Inc.) — sending service email (the welcome message, address verification, password reset, the notice that your password was changed, the confirmation link to the new address when you change your email and the notice of that change to the old address, the confirmation code that proves it is you in the settings, the notice that a company was connected to e-invoicing, the one-off offer of help), sending the newsletter to those who asked for it, delivering your suggestion for improvement to us, delivering the documents you send to your own customers when Cloudflare does not accept them, the notices of a rejected e-invoice you send to a supplier, and the notices of access you send by adding someone to your account. US, Standard Contractual Clauses.
- Efakturuj, s. r. o. (the Efakturuj service) — the certified delivery service provider (digital postman) for e-invoices: connecting a company, delivering and receiving e-invoices, and reporting their data to the Financial Administration of the Slovak Republic. Only if you switch e-invoicing on — apart from checking a customer in the Peppol network (see "E-invoicing"). Slovak Republic; data is processed in the EU/EEA.
- Google Ireland Ltd. — signing in with Google, if you use it, the Google sign-in button shown on the pages of this site, audience measurement, measuring how well our advertising works, and the mailbox your suggestions for improvement arrive in. EU/US, EU-US Data Privacy Framework.
- Functional Software, Inc. (Sentry) — reports about errors in the application. Processed in the EU (Germany).
- PostHog Inc. — recordings of how the pages of this site (not the application) are used, only with your consent. Processed in the EU (Germany).
Cookies and local storage
Strictly necessary, without which the service does not work: f365_session (you are signed in), f365_google_state (CSRF protection for Google sign-in), f365_google_widget (the same for the Google sign-in card on this site; it is created only after you press its button and lasts 5 minutes), f365_active_company, f365_active_account (which account you are working in, if you were given access to another one too), f365_tab_account (carries, with a save, which account the page was showing, so the change cannot land in another account; it lasts a minute), f365_locale, f365_theme (your interface settings) and f365_consent (your answer to the cookie bar, kept for 6 months).
Besides cookies we use your browser's local storage (localStorage and sessionStorage) for small things that need not travel to a server: the language and theme you picked, the units of measure you used last (f365_units), the constant symbol you used last (f365_constant_symbol), whether the optional parts of a form are unfolded, the details prefilled into your next invoice (f365_invoice_issuer_details, f365_invoice_client_details), the countdown before a verification email can be sent again (f365_verify_resend_until), the fact that you dismissed the Google sign-in card (f365_google_widget_closed, until you close the browser tab), a one-off marker that stops a page reloading in a loop after an error (f365_skew_reload), and the draft invoice in the generator. All of it stays on your device, none of it is sent to us, and clearing the site's data in your browser removes it. In the mobile app, a document you view, print or share is written to the app's temporary folder; it is deleted the next time the app starts, or sooner — when the next document is opened, once it is a few minutes old. A document you share or open in another app is then kept by that app under its own rules. If you turn on the app lock (Face ID, a fingerprint or the device passcode), the app stores only the fact that it is on and the wording of its screen; the device's own system does the check, and no biometric data ever reaches us or the app.
Measurement of visits and of advertising: Google Analytics 4 and Google Ads in Consent Mode v2. Until you answer the bar, consent is not granted: in that state no cookie is stored, you are not identified, and Google receives only anonymous signals about the visit. If you do grant it, Google Analytics stores its own cookie and joins your visits into one session, and Google Ads stores the identifier of the ad click (the _gcl_* cookies) so that we can tell which campaign brought a new sign-up.
Recordings of how the site is used: if you accept on the bar, on the pages of faktura365.sk (not in the application) we use PostHog to record how the page is used — moving through it, scrolling, clicks and the part of the page where the visit ends — so that we can see where the site is unclear. Anything you type into a field, and the whole content of the invoice generator, is hidden in the recording while still in your browser and never reaches us or PostHog. PostHog stores no IP address and creates no personal profile. It stores a cookie and a local-storage entry of its own (ph_*) to join the pages of one visit. The legal basis is your consent, Art. 6(1)(a) GDPR; without it the recording is not even loaded. Recordings are kept for 30 days.
From advertising we measure a single event — that a new account was created. We do not send Google your email, your name or anything else that could identify you (enhanced conversions are switched off), and we do not track what you do inside the application. We do not use personalised advertising: the ad_personalization signal is always denied, so your data does not become advertising audiences or remarketing lists.
Signing in with Google on the page itself: we show a small card with a button for signing in with your Google account. For that button to be drawn, your browser requests a script from Google (accounts.google.com), and Google may store cookies of its own in the process. This is neither measurement nor advertising, it serves sign-in alone, and that is why we do not make it conditional on your answer to the cookie bar: § 109 of Act 452/2021 Coll. requires consent for storage that is not necessary for a service you asked for yourself. Data from your Google account (email, name and profile picture) reaches us only when you press the button — until then we receive nothing about you from Google. You can dismiss the card at any time with its ✕.
Your answer covers both this site and the application (the cookie is set on the .faktura365.sk domain). You can change it at any time by clearing cookies in your browser settings — the bar will then ask again.
Where you came from is worked out WITHOUT a cookie and without storing anything in your browser. If you arrive from a link carrying campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content, or a click identifier such as gclid, msclkid or fbclid) or from another site, we pass that along in the addresses of our own links (the src parameter) and store it only if you create an account — as a detail of that account. It describes the visit, not you: no name, no email, nothing that identifies you. If you do not create an account, nothing is stored at all. It answers one question for us — which of our pages and campaigns bring new users.
After a sign-in or a sign-up we set a technical cookie, f365_ga_event, for one minute. It carries a single fact to the browser — that the sign-in succeeded — because the sign-in itself is completed on the server and the page would otherwise never learn of it. It contains no personal data and is deleted once it has been read.
How long we keep it
Account data and everything you created in it, for as long as the account exists. When you delete the account, all of it goes at once — invoices, customers and numbering counters included; we keep no separate backups. The database only technically retains restore points for the last 30 days (the Time Travel feature of Cloudflare D1) — we would use them only to recover from a failure, and they expire after 30 days.
One-time tokens that verify the email at sign-up live for 30 days; tokens for an email change or a password reset live for hours. They are deleted once they expire. When you change your email, we also store the new address until it is confirmed; the sign-in address changes only once the link we email to it is pressed, and an unconfirmed new address is deleted with its token. The one-time code that carries a Google sign-in from the mobile app's browser back into the app lives two minutes and is deleted once used or expired. The confirmation code that proves it is you in the settings is stored only as a hash; it is valid for ten minutes and is deleted once used, once a new one is requested, or once it expires.
When you change your email, we keep the previous address with a one-time token for 30 days, so that you can undo a change you did not make. The legal basis is our legitimate interest in keeping accounts secure. They are then deleted, and also when the account is closed.
Counters of failed sign-in attempts — tied to an IP address and to a hash of the email that was typed — are valid for at most an hour and are swept away as later attempts come in. The counter of confirmation emails, tied to your account identifier, is valid for 24 hours and deleted with your account. The counters of attempts to confirm it is you in the settings and of confirmation codes sent, tied to your account identifier, live just as long and are deleted with your account.
The counter of documents you have emailed — tied to your account identifier — is valid for 24 hours and exists only so that the daily sending limit can be kept. It is deleted with your account.
The form submission marker — a random identifier tied to your account, written down when a record is created (a document, a payment, a customer and the like) or a document is emailed, together with the kind of action and a reference to the record created. It exists only so that the same form sent twice is not saved twice. It is valid for 24 hours and is then removed at the next save; it is deleted with your account.
A membership in someone else's account lasts until the account's owner removes it, until you end it, or until either account ceases to exist. Deleting your account removes the access of everyone you added to it; their own accounts stay.
The record of your newsletter answer, for as long as the account exists; it is deleted with it.
A link to a document shared with a customer, until you cancel it or delete the document or the account.
E-invoicing records — the state of a company's connection, the lists of sent and received e-invoices and their stored files — for as long as the account exists; they are deleted with it. What we have already handed to the delivery provider, and what it has reported to the Financial Administration of the Slovak Republic, does not cease when you delete your account with us: the provider and the Financial Administration keep it for as long as the law requires them to.
Recordings of how the site is used (PostHog), 30 days; then they are deleted.
Your rights
You have the right of access to your data, and rights to rectification, erasure, restriction of processing, portability, and to object to processing based on legitimate interest. Write to info@faktura365.sk — we answer within one month.
You can delete your account yourself under Settings with the "Delete account" button — on the website and in the mobile app alike. It is deleted at once, together with everything you created in it; from the database's restore points it disappears within 30 days (see "How long we keep it"). If you can no longer sign in, write to info@faktura365.sk from the address the account is registered with and we will delete it for you.
Where processing rests on consent (the newsletter, measurement of visits and advertising), you have the right to withdraw that consent at any time, without affecting the lawfulness of the processing that took place before you did.
If you believe we are processing your data unlawfully, you may lodge a complaint with the Slovak Data Protection Authority (dataprotection.gov.sk).
Automated decision-making
We make no automated decisions about you and we do not profile you.
Changes
The effective date of this version is shown above. We will tell you about material changes in the application.