Privacy Policy
Last updated: November 19, 2026
1. Who we are
2. Data we collect
- Account: name, email and unique identifier (via Clerk authentication).
- Integration credentials: tokens, API keys and webhook secrets for the platforms you connect, used only to issue tax documents on your behalf.
- Sales data: identifier, customer, tax number, amounts, products and statuses, processed to create the invoice or credit note.
- EuPago payment requests: when you create a payment request in Rioko, the customer details you enter (name, tax number, email and address) and, for MB WAY, the mobile number, to create the payment in EuPago and issue the invoice in that customer's name.
- Support requests: what you write in requests and in the Rioko Assistant chat, and the answers, kept in your account.
- Rioko app (iPhone and Android): when you sign in to the app, we keep the session (a code we store only as a hash, from which it cannot be rebuilt, the device name if the app provides it, and the dates it started, was last used and ends). If you turn on notifications, we also keep the phone's notification identifier, its system (iOS or Android), and when we last sent it a notification and with what result. We also keep when you opened each support answer and saw each alert, to show the number on the app's icon.
- Technical logs: timestamps, request identifiers and external API responses, for auditing and diagnostics.
3. What we use it for
- Create Invoices, Invoice-Receipts and Credit Notes in your invoicing software automatically.
- Ensure tax compliance (AT rules, VAT exemptions M01–M99, tax number).
- Show history and reconciliation in the dashboard.
- Send failure alerts and issuance reports.
- Send notifications to the Rioko app (alerts and support answers), if you turned them on.
- Provide technical support when you request it, including through the Rioko Assistant (Roko), an artificial intelligence assistant that answers in the dashboard chat when you use it.
We do not sell or share your data with third parties for marketing purposes.
4. Subprocessors
- Cloudflare (hosting, DNS, D1, KV, Workers) — EU/global.
- Clerk (authentication; if you choose to sign in with your Google or Apple account, that account confirms your identity and shares basic profile data such as your name and email) — EU/US.
- Apple (Apple Push Notification service, notifications on iPhone) and Google (Firebase Cloud Messaging, notifications on Android) — US. Only if you use the Rioko app and turn on notifications: they receive the phone's notification identifier and the notification's text, which is generic and never carries sales data, your customers' data or the content of messages.
- Shopify, Stripe, Lodgify, EuPago (sales source platforms) — according to the connection you configure. For an EuPago payment request created in Rioko, EuPago receives the amount and the request's code; for MB WAY, also the customer's mobile number; for a payment link, also the customer's name and, if you enter it, their email, to send them the link. For Multibanco it receives no customer data.
- InvoiceXpress, Moloni, Moloni ON, Vendus, TOConline (tax document issuers) — Portugal.
- Stripe (processing payments for your Rioko subscription) — EU/US.
- Resend, with MailChannels as fallback (delivery of alert and report emails) — EU/US.
- Fly.io (fixed-IP egress relay required by Lodgify) — EU.
- Anthropic (artificial intelligence) — US. Used in two cases:
- Automatic diagnosis attached to critical alerts: only a restricted, predefined set of fields (total and tax calculations, product and SKU names, the error text returned by the platform, and connection metadata). Customer name, email, tax number, order reference and user identifier are never sent in this case.
- Rioko Assistant (Roko), in the dashboard chat once you accept it, and when the Rioko team asks it to look into one of your support requests: the request's messages, your connections' configuration (never credentials) and the data of the sales and documents it consults to answer, which may include your customers' name, email, tax number and order reference. The Assistant changes nothing in your account without your express approval.
- Google (Google Analytics 4 and Google Ads, measurement of traffic and of the ads that bring sign-ups) — EU/US, under the EU Standard Contractual Clauses. Loads only with your consent.
We use only the subprocessors required by the connection you configure. A platform you do not connect neither receives nor processes your data.
5. Retention
The customer details kept in an EuPago payment request (name, tax number, email and address) are deleted 30 days after the payment once the invoice is final, or 30 days after the request can no longer be paid if it never was. The MB WAY mobile is deleted as soon as the payment is created in EuPago. This deletion does not cover the invoices issued nor our record of them (number, amount and customer name).
In the Rioko app, the session ends when you sign out, after 90 days without use, or 180 days after you signed in. The phone's notification identifier is deleted when you sign out, when you turn off notifications in the app, when Apple or Google report that it is no longer valid, or when the account is deleted.
Tax documents already issued reside in your invoicing account and are not deleted by us: their retention follows the applicable legal archiving periods and is your responsibility.
6. Your rights (GDPR)
- Access your personal data.
- Correct inaccurate data.
- Request deletion ("right to be forgotten").
- Data portability.
- Withdraw consent at any time.
- File a complaint with CNPD (Portuguese Data Protection Authority).
To exercise any right, email rioko@kapta.pt.
7. Security
8. Cookies
Strictly necessary (always active, no consent needed): Clerk session — authentication; rioko_impersonate_id — entering another account: Rioko administrators, authorised partners and people granted read access (8 hours); rioko_member_account — the account someone who is a user of several is working in (1 year); rioko_attr — records signup origin (referrer/campaign) for abuse prevention (90 days).
Analytics and ad measurement (only with your consent): Google Analytics 4 — cookies _ga and _ga_* (~2 years) measure traffic; Google Ads — cookies _gcl_* (~90 days) record the click on a Rioko ad, so we know whether it led to a sign-up or subscription. Data may be processed by Google in the United States under the EU Standard Contractual Clauses. Loaded via Google Consent Mode v2 with everything denied by default — these cookies are set only after you accept.
You can change or withdraw your choice at any time via Cookie settings in the page footer. Your choice is stored locally on your device for 6 months, after which we ask again. We use no personalised advertising or remarketing cookies.
9. Changes
10. Consumer information
CIMAAL, Centro de Informação, Mediação e Arbitragem de Conflitos de Consumo do Algarve. Covers municipalities in the district of Faro.
Address: Ninho de Empresas, Edifício ANJE, Estrada da Penha, 3.º andar, sala 26, 8000 Faro
Phone: 289 823 135
Email: cimaal@mail.telepac.pt
Site: www.consumidoronline.pt
The electronic Complaints Book is also available at www.livroreclamacoes.pt/inicio.
11. Contact
NIPC 516277421
Urbanização O Monte Lt1, Loja 11, 8200-428 Galé, Albufeira, Portugal
Email: rioko@kapta.pt
Site: kapta.pt
Annex. Partner accounts
- when you sign up through the partner's page, that partner receives the account's company name, VAT number and email, only to confirm you are its client;
- only with your express permission does the partner access your account's data, including settings, documents and logs, and it handles them on your behalf;
- every permission, confirmation and withdrawal is recorded with the date, who made it and the version of the text accepted;
- you can withdraw access or leave the partner in My account, at any time.

