Who we are
Rixa Handelsbolag (organisation number 969804-3131), Sweden, is the controller for the personal data described here. Contact: founders@rixa.se.
RIXA is in a pilot phase. This policy describes what the software actually does today. It has not yet been reviewed by a lawyer, and we will update it when it has.
What we collect and why
- Access requests: your name, work email, firm and optional message from the request-access form, so we can reply and arrange a demo. Legal basis: legitimate interest.
- Accounts: your email, name, role and firm membership when you are invited, so you can sign in and so access can be controlled. Legal basis: our agreement with your firm.
- Change history and access log: who changed or opened which record, and when, so your firm has an audit trail. Legal basis: our agreement with your firm.
- Pilot signals: which product screens a signed-in user opens (the screen name only, never a record or anything typed) and feedback notes you choose to send, so we can improve the product. Legal basis: legitimate interest.
Your firm's records
Records and documents a firm puts into RIXA belong to that firm. The firm is the controller and we process them on its behalf. We do not sell personal data, use it for advertising, or train AI models on it.
What stays on your own computer
If your firm has not been set up on RIXA's server, its portfolio records and documents are kept only in your browser and never sent to us. We cannot see, back up or restore that data. Clearing your browser's site data deletes it.
Who processes data for us
- Supabase: sign-in, database and file storage, in the EU (Sweden).
- Lovable: building and hosting the website.
- Resend: sending sign-in and invitation emails.
- Cloudflare: runs the website and the product's server code, so requests pass through its network.
- GitHub: runs RIXA's scheduled jobs, such as the daily deletion of expired pilot data and the nightly Fortnox fetch. A job only tells our server to run; your firm's records do not pass through GitHub.
AI document reading and transfers outside the EU
RIXA can read uploaded documents with Anthropic's API, which processes them in the United States. This is switched off for every firm, and stays off until the firm agrees to it in writing. Before it is switched on for anyone, we will name the legal safeguard for that transfer here.
Connecting your own Claude
A member of a firm can connect their own Claude (Anthropic) to RIXA, once the firm has agreed to it in writing and we have switched it on for that firm. It is off for every firm until then. Claude then reads the firm's portfolio records as that member, with that member's access, and may save drafts that a person in the firm accepts or dismisses. Since November 2026 it can also search and read the text of the firm's documents, which RIXA stores beside each uploaded file for that purpose. It never opens the stored files themselves.
What Claude reads is processed by Anthropic under your firm's own agreement with Anthropic for Claude, not under RIXA's. We switch it on for a firm only on a Claude plan under Anthropic's commercial terms (Team or Enterprise). On Anthropic's consumer plans (Free, Pro and Max), whether chats are used to train models depends on each user's own setting, so they are not for a firm's records. Every call Claude makes is recorded in your firm's audit trail with the member it acted for. A member can disconnect Claude at any time in RIXA or in Claude.
A portfolio company's Fortnox books
A firm can ask a portfolio company to connect the company's own Fortnox to RIXA. This is off for every firm until the firm has agreed to it and we have switched it on. A system administrator at the company approves the connection in Fortnox; nobody at the firm sees the company's Fortnox login.
RIXA then reads the company's account balances per month: account numbers, account names and amounts, every night and when the firm asks. It does not read invoices, vouchers, customers, suppliers, employees or salaries, discards the contact details in Fortnox's export file, and never writes to Fortnox. An account name can contain a person's name (a loan from an owner, for example); it is kept only as the name of that account. RIXA stores no Fortnox password or login, only the company's number in Fortnox, encrypted.
The balances are kept with the firm's records, under the same rules as the rest of them. The company can end the connection at any time in Fortnox, and the firm can disconnect it in RIXA; figures the firm has already approved stay with its records.
How long we keep data
- Access requests: 12 months from the request, unless it leads to an account.
- Pilot signals (screen names and feedback): until three months after the pilot your firm takes part in ends, or earlier, together with your firm's data.
- Accounts: until your firm stops using RIXA and asks us to remove them, or you ask us to.
- Your firm's records, documents, change history, access log and record of Claude's calls: until your firm asks us to delete them, and during a pilot at the latest seven days after the agreed end date, when they are deleted automatically unless the pilot is extended. Either way we give a signed certificate of what was deleted. Copies in our providers' backups expire on the providers' own schedule.
Your rights
You can ask for access to, correction of or deletion of your personal data, object to processing based on legitimate interest, and ask for a copy in a portable format. Write to founders@rixa.se. If your request concerns records your firm put into RIXA, we pass it to your firm.
You can also complain to the Swedish Authority for Privacy Protection (IMY), imy.se, or to the authority where you live.
Cookies and browser storage
We use only the browser storage the product needs to work: your sign-in session and, if your firm is not set up on RIXA's server, its portfolio records. There are no analytics or advertising cookies.
Changes
We will post changes on this page and update the date at the top.
CONTACT
Questions about this policy?
Write to Rixa Handelsbolag at founders@rixa.se.