Inzenda Privacy Policy

Last updated: October 20, 2026

The Swedish version prevails if the two differ.

This policy describes how Inzenda AB processes personal data when you visit inzenda.se, create an account, pay, contact us or receive email from us. We have tried to write it so it can be read in a few minutes.

Inzenda AB, company registration number 559480-1580, is the controller for the processing described in this policy.

  • Postal address: Sysslomansgatan 20, 112 42 Stockholm
  • Privacy email: privacy@inzenda.se
  • Support: support@inzenda.se

We have not appointed a data protection officer.

Inzenda has two roles, and it matters to keep them apart:

  • We are the controller for data about you as an account holder and visitor: your account, your sign-in, payment, support requests, email from us, statistics on how the service is used, and protection against misuse. That processing is what this policy covers.
  • We are a processor for the data your company enters into the service about other people: board members, employees and payees in payroll and the employer declaration (AGI), counterparties in transactions, the person who signs the annual report, and similar. For that data your company is the controller, and we process it under our data processing agreement (DPA). Anyone with questions about such data, an employee for example, should contact the company first.

For demo companies we are the controller of all data in them, including the address of anyone you invite. We send the invitation on your behalf and delete the data when the demo company is deleted.

Account data. Name and email address. If you have a password, it is stored only as a hash. If you sign in with Google, Google gives us your name, email address, profile picture (as a link) and an id for your Google account. We also store which version of the terms of service you accepted, and when.

Sign-in and security. While you are signed in we keep a session with your IP address and browser and device information (user agent) and how you signed in (password, Google or passkey). A session lasts 7 days from its last use, or until you sign out. If you turn on two-step verification we store an encrypted setup key for your authenticator app and encrypted backup codes. We log when it is turned on or off, when new backup codes are created, when a backup code is used, when you confirm an action with the code, when the account is locked after too many errors and when support resets it. If you add a passkey you can sign in with it and confirm sensitive actions with it. We then store its public key, an id for it, what kind of passkey it is, a name and when it was added and last used. The private key and your screen lock never leave your device. We log when a passkey is added or removed.

Company data relating to you. Your company's registration number, name, address and financial year, and which company your account is linked to. If you are yourself the contact person for the employer declaration, we process your phone number on the company's behalf under the DPA.

Company lookup. When you enter a registration number we fetch the company's register data from Bolagsverket (the Swedish Companies Registration Office), including the board members' and auditors' names and personal identity numbers. For the lookup, before the company is added to an account, we are the controller on the basis of legitimate interest (showing the right company and the right people), and personal identity numbers are used only to identify the right person. The lookup itself stores no personal data with us. If you continue in the wizard, the data is kept in the draft in your browser, and with us only once the company is added to an account. A personal identity number from the register is never shown in full in your browser, only the year of birth. During the lookup we also collect technical browser signals to protect it against automated requests (Vercel BotID) and limit the number of lookups per IP address.

Payment. Card details are entered directly with Stripe and never reach Inzenda. We store Stripe's customer id, subscription id, subscription status (plan, billing period, renewal date) and the payments made (amount and date). In Stripe's checkout you can enter a billing address and registration number; those are stored by Stripe.

Communication. Email you send to support, which reminders we have sent, and whether (and when) you have unsubscribed from reminders.

Use of the service. Which steps you take in the service, for example completed wizard steps, a started checkout, a completed payment and a filing. It is linked to your account when you are signed in. We also store which campaign link (utm parameters), which website (domain name only) and which landing page a visit came from. These statistics store no IP address and use no cookies.

Technical data. Our hosting provider logs IP addresses in server logs. Vercel Web Analytics and Vercel Speed Insights give us visit statistics and load times without cookies. If something breaks, an error report is sent to Sentry; personal identity numbers are masked before the report leaves us, and we do not send IP addresses or sign-in data with error reports.

Filing data. Receipt numbers and status from Bolagsverket and Skatteverket (the Swedish Tax Agency) for what you file.

PDF bank statements. If you upload a bank statement as a PDF, it is read in memory and never stored, neither the file nor its text. The rows you confirm become transactions in the company's books; of the file only its checksum (sha256), the period and the account are kept, as a trail for the books.

Trials. If we give a company a trial, we keep the e-mail address the invitation is sent to, the day you asked for it, the end date and the purpose (test, prospect or partner), and then which account and company it covers. The data is kept before you have an account.

PurposeDataLegal basis (GDPR Article 6(1))
PurposeCreate and run your account, let you sign inDataAccount, sign-in, two-step verification (setup key and backup codes), passkeysLegal basis (GDPR Article 6(1))Contract (b)
PurposeDeliver the service: prepare the books, annual report and returns and send them to Bolagsverket and Skatteverket for the company's signatureDataAccount, company data, filingsLegal basis (GDPR Article 6(1))Contract (b)
PurposeTake payment and manage subscriptionsDataPayment, accountLegal basis (GDPR Article 6(1))Contract (b)
PurposeKeep our own accountsDataPaymentLegal basis (GDPR Article 6(1))Legal obligation (c), Swedish Bookkeeping Act
PurposeSend service records: receipts, the welcome email, filing confirmationsDataAccount, filingsLegal basis (GDPR Article 6(1))Contract (b)
PurposeSend reminders about deadlines, status at Skatteverket and drafts you did not finishDataAccount, company data, reminder logLegal basis (GDPR Article 6(1))Legitimate interest (f): that you as account holder do not miss a deadline
PurposeAnswer support requestsDataCommunication, accountLegal basis (GDPR Article 6(1))Contract (b) or legitimate interest (f)
PurposeProtect the service against misuse, troubleshoot and keep it secureDataSign-in, technical data, two-step verification log and passkey logLegal basis (GDPR Article 6(1))Legitimate interest (f)
PurposeUnderstand how the service is used and improve it, measure which campaigns workDataUse, technical dataLegal basis (GDPR Article 6(1))Legitimate interest (f)
PurposeEstablish, exercise or defend legal claimsDataThe data needed in the individual caseLegal basis (GDPR Article 6(1))Legitimate interest (f)
PurposeGive trials and send the invitation to the person who asked for oneDataE-mail address, end date, purposeLegal basis (GDPR Article 6(1))Legitimate interest (f): that the person who asked for a trial gets it

Where we rely on legitimate interest we have weighed our interest against yours, and you always have the right to object (see section 8).

We send no newsletters and no marketing by email. If we start, we update this policy before the first mailing, and you can always opt out.

We make no decisions about you based solely on automated processing that have legal effects for you.

You need to provide your name and email address to create an account, and the data a filing requires for us to prepare it and send it to the authority for the company's signature. Without them we cannot deliver the service. You are not obliged to provide any other data.

We never sell personal data.

Providers that process data on our behalf (processors):

ProviderWhat they do for usWhere the data is stored
ProviderVercel Inc.What they do for usRunning the website and servers, file storage for receipts and signatures, visit statistics, load times, protection against automated requestsWhere the data is storedServers in Frankfurt (fra1). File storage: Stockholm (arn1)
ProviderNeon (Databricks)What they do for usDatabaseWhere the data is storedFrankfurt (aws-eu-central-1)
ProviderResendWhat they do for usSending our emailWhere the data is storedSending via Ireland (eu-west-1); logs stored in the US
ProviderFunctional Software Inc. (Sentry)What they do for usError reportsWhere the data is storedEU (Germany, de.sentry.io)
ProviderGoogle (Google Workspace)What they do for usOur email, including support@inzenda.seWhere the data is storedEU and US (Google's data centres)

Recipients that are controllers in their own right:

  • Bolagsverket receives annual reports and, when the company has an auditor, your and the auditor's email address for the receipt and the notice about the audit report, and gives us register data. It is a public authority and processes the data under its own rules.
  • Skatteverket receives income tax returns, employer declarations and VAT returns. It gives us the employees' tax table ('Fråga om skatteavdrag') and, where your company has authorised us as a read-only agent (läsombud), data on the company's tax account and returns. It is a public authority and processes the data under its own rules.
  • Stripe (Stripe Payments Europe Ltd) handles payments for us and is a controller in its own right for part of that processing, for example fraud prevention and financial regulation.
  • Google is a controller for your Google sign-in, if you choose to sign in with Google.
  • The provider of an AI assistant you connect, for example Anthropic or OpenAI, receives your name and the companies' data under your or your company's agreement with that provider (see Connected AI assistants).

When you sign at Bolagsverket and Skatteverket, it happens in their own services.

We may also have to disclose data to authorities where the law requires it.

The database and file storage are in the EU (Frankfurt and Stockholm). Logs of sent emails are stored by Resend in the US, and support email at Google may be stored in the US. Several of our providers (Vercel, Neon, Resend, Sentry, Google and Stripe) are also US companies or part of US groups, so data may in some cases be accessed from or transferred to the US, for example for support or operations.

The provider of an AI assistant you connect may process the data outside the EU/EEA under its own terms (see Connected AI assistants).

When that happens the transfer is protected by one of the following:

  • The EU-US Data Privacy Framework, where the provider is certified under it. This applies to Vercel, Neon (Databricks), Resend, Sentry and Stripe.
  • The European Commission's standard contractual clauses in the provider's data processing agreement, where the provider is not certified. All our US providers also include standard contractual clauses in their agreements, and they apply to Google.

You can get a copy of the safeguards by contacting us.

DataHow long
DataAccountHow longAs long as you have an account. When you ask us to delete the account we delete the account data within 30 days, except what must be kept as below.
DataSign-in sessionsHow longExpire 7 days after last use or when you sign out, and are then deleted.
DataBooks, receipts, payroll, annual reports and tax returnsHow longAs long as the company is in Inzenda. Once the company is closed: until 31 December of the seventh year after the end of the calendar year in which the last financial year ended (Bookkeeping Act chapter 7 section 2). See below.
DataOur own accounting records about your paymentsHow longUntil the end of the seventh year after the end of the calendar year in which our financial year ended (Bookkeeping Act chapter 7 section 2).
DataReminder logHow longUntil the company is closed in Inzenda.
DataUsage statisticsHow long25 months, then deleted automatically.
DataServer logs at VercelHow longUp to 30 days.
DataError reports in SentryHow longUp to 90 days.
DataSupport emailHow long24 months after the case is closed.
DataThe setup key and backup codes for two-step verificationHow longUntil you turn the feature off.
DataThe security log for two-step verification and passkeysHow longAt most 24 months.
DataPasskeysHow longUntil you remove them or the account is deleted.
DataTrialsHow longA trial that is not used or that is ended: the e-mail address and the link are deleted 30 days after it ended. A used trial is kept as long as the company is in Inzenda.
DataDemo companiesHow long90 days after last use, when you delete it or when the account is deleted. Start over deletes the books at once.
DataDemo company abuse protection (a keyed hash of the IP address)How long2 days.
DataInvitations sent from demo companies (who invited, when, and a keyed hash of the recipient's address)How long12 months. An invitation that is not used is deleted, with the address, 30 days after it expired or was revoked.

The books are not deleted on request. Vouchers, their history, transactions, receipts, annual reports, tax returns, payroll runs and the system documentation in force for each year are accounting records that the company must keep under the Bookkeeping Act. The right to erasure does not apply where processing is required to comply with a legal obligation (GDPR Article 17(3)(b)). A deleted transaction therefore stays in the books as a reversal.

When you close a company in Inzenda, your account loses access at once and you are offered a download of the books first. Data about you that is not part of the books, such as the phone number and the log of reminders, is deleted then. The books are kept until 31 December of the seventh year after the last financial year ends and are then deleted automatically, receipts in file storage included.

Database backups are deleted as they rotate out, within 6 hours.

You have the right to:

  • access the data we hold about you and get a copy;
  • rectify inaccurate data;
  • have data erased, except what we must keep by law (see section 7);
  • restrict processing, for example while we look into an objection;
  • object to processing based on legitimate interest. You can stop reminders at any time through the link in every reminder;
  • receive your data in a machine-readable format (data portability) for what you have given us under the contract.

If you are the only one with full access to a company (demo companies excepted), you cannot delete your account until you have given someone else full access or closed the company. The company's books stay when your account is deleted, since the company must keep them.

Write to privacy@inzenda.se. We answer within one month. We may need to ask you to confirm who you are before we disclose data.

If your question is about data a company has entered into Inzenda about you, as an employee or board member for example, that company is responsible. Contact the company; we help it answer.

You also have the right to lodge a complaint with the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), www.imy.se, Box 8114, 104 20 Stockholm, Sweden. We would appreciate hearing from you first.

  • All traffic to and from the service is encrypted (HTTPS).
  • Personal identity numbers and salary bank account numbers are encrypted in the database with AES-256-GCM, with a key the database itself does not hold. They are shown masked in the browser.
  • Passwords are stored only as hashes.
  • Whoever adds a company gets full access to it. Others get access only through an invitation from someone with full access, with full access, edit access or view only. With view-only access you can ask for edit access; everyone with full access is then e-mailed your name and your message, and the message is deleted 30 days after the request is decided or expires. If someone with full access has connected an AI assistant, the assistant can read the request. Data fetched from Skatteverket under the company's authorisation is shown only to those with full access to the company. Those with access to a company linked in a group see the group's figures.
  • The books cannot be overwritten afterwards; changes are kept as corrections with history.
  • Error reports mask personal identity numbers before they leave us.

We use only the cookies the service needs to work, mainly for sign-in. We use no cookies for advertising or tracking and have no advertising pixels on the website. In your browser's local storage we keep, among other things, your choice of light or dark mode and drafts in the wizard. Read more in our cookie policy.

Stripe sets its own cookies on its payment pages. Those are covered by Stripe's cookie policy.

We update this policy when the service or the law changes. The date at the top shows when it last changed. For significant changes we notify you by email or in the service before they take effect.

Inzenda AB
Company registration number 559480-1580
Sysslomansgatan 20, 112 42 Stockholm
privacy@inzenda.se

If you are an auditor

If you are the auditor of a company that uses Inzenda: The company is the controller of the data about you, and we process it on the company's behalf. We fetch your name, your audit firm and your role from Bolagsverket's register; your title and email address come from the company or from you. The data is used for the auditor's note in the company's annual report, for Bolagsverket's notice and receipt to you and, if the company asks us to, for emails to you. We do not store your personal identity number, only a keyed hash to recognise you in the register. The auditor's note is part of the annual report and is kept with the company's accounting records (Bookkeeping Act, chapter 7, section 2). When the company is closed in Inzenda, your email address, your title and the hash of your personal identity number are deleted; your name, your role and your dates are then kept like the company's other data under the DPA (section 11.3). If we send you a link and you open it, we keep the IP address in security logs; for that we are the controller, on the basis of legitimate interest (see section 7 on retention). Please ask the company first, or privacy@inzenda.se.

You can ask which data we hold about you, have it corrected or erased, and object to the processing, through the company or privacy@inzenda.se. You can also complain to the Swedish Authority for Privacy Protection (IMY).

AI suggestions on import

AI suggestions on import are on from the start for companies added to Inzenda and can be turned off. Whoever adds a company sees that the function is on and can turn it off at once or later in the company's settings. When you connect an AI assistant, you also choose whether it is on for companies the assistant adds. For a company added earlier, the account that owns the company in Inzenda can turn it on. Separate terms govern the function (an addendum to the data processing agreement). Companies where the function is off are not affected.

When it is on, for the rows of a bank file we do not recognise, we send the bank's counterparty text, whether money came in or went out, an amount band, the month and facts about the company's size to Anthropic, PBC (USA), the maker of the AI model Claude. We remove personal identity numbers, organisation numbers, account numbers, card numbers, phone numbers, email addresses, amounts, the company's name and the names of the company's employees, board members and users, and rows that appear to concern a private person are not sent. The text may still contain a name, for example in a sole trader's business name. Processing takes place in the USA under the European Commission's standard contractual clauses (module 3); contact us for a copy.

A suggestion is never a decision: nothing is booked until a user has approved it. Anthropic does not use the data to train models and deletes it within 30 days; if a request is flagged for review under Anthropic's usage policy it may be kept for at most two years. We keep suggestions for seven days and then delete them. That a category was suggested by AI and approved by a user is recorded in the transaction's history and kept with the books.

To attribute costs and detect abuse, we keep usage metadata per company and user: the number of calls, tokens and the cost, never the content. The link to the user is removed after 12 months and the records are deleted after 24 months.

Connected AI assistants

You can connect an AI assistant, for example Claude or ChatGPT, to one or more companies in Inzenda. You start the connection in the assistant and approve it on inzenda.se, and you can disconnect it at any time under Connected apps in your account or under the company's Access tab. Someone with full access to the company can also disconnect your assistant from the company, and you are e-mailed when they do. The assistant reaches only the companies you chose and never more than you can access yourself. It can read and, if you allow it, book and prepare (an assistant can prepare the annual report and INK2), but it never sends anything to Bolagsverket or Skatteverket; you do that in Inzenda. Everyone with full access to the company is e-mailed your name and the assistant's name when you connect it.

You confirm and are responsible for what is sent to Bolagsverket or Skatteverket in the company's name; an assistant can only prepare. When something an assistant prepared has been sent, everyone with full access to the company is e-mailed about it. A prepared filing that is not confirmed is kept for 30 days after it expired; a confirmed one is kept for 24 months after the confirmation, with who confirmed it. An assistant can also prepare turning on payroll or VAT and a payroll run already paid, and reversing a booked item, inviting someone, revoking an invitation or approving edit access. That happens only when an authorised user confirms on inzenda.se; the provider then receives the names and amounts you give the assistant. In a prepared payroll run the amounts are deleted when it is confirmed, cancelled or expires.

When the assistant asks, we disclose the data about the companies that it asks for and that you can see in Inzenda, for example transactions, the books and returns, and with payroll the employees' names and amounts. This also applies if you have view-only access. The assistant also receives your name and which companies it is connected to. Personal identity numbers are never disclosed to an assistant: they are masked before anything leaves us, and the masked form shows only the date of birth. Names and dates of birth can therefore reach the assistant. The assistant can also hand over details of a new employee (name, tax table and column, start date, jämkning, salary account). We keep them at most 24 hours on a link only you open, and you type the personal identity number yourself on inzenda.se. The assistant's provider sees which product and price a payment link is for, but never card details. Stripe handles those.

The assistant can also hand a file to us, for example a bank statement or a receipt. We fetch it from the assistant provider's file service, or you upload it yourself through a link on inzenda.se. The file is kept in Inzenda as if you had uploaded it in the app, and a receipt is read with AI only if the company has turned that on. Files and images are never disclosed to the assistant; it receives only what we read from them, such as dates, amounts, VAT and the seller.

For the data about the company and its employees your company is the controller (section 2), and connecting an assistant is the company's instruction to us to disclose it. The provider of the assistant, for example Anthropic for Claude or OpenAI for ChatGPT, receives it under your or your company's own agreement with that provider and is not our sub-processor. This is separate from AI suggestions on import, where we use Anthropic as a sub-processor. The provider may process the data outside the EU/EEA under its own terms. In the assistant's settings you choose whether your conversations may be used to train the provider's models and how long they are kept.

For the connection itself we are the controller. We keep which assistant it is, which companies and which access you chose, when it was connected and last used, and a log of when it was connected and removed, on which days it read data about a company and, when it books or prepares, what it did (tool, time and result, never what it sent or received). The data about the connection and your account's rows in the log are kept as long as the account exists. In the company's log, what the assistant booked, undid or prepared, and what was confirmed, is kept as long as the company's accounting records; other rows (connections to the company, reads and preparations that were cancelled or expired) are kept for 24 months. If someone with full access disconnects another user's assistant, that is kept in the company's access history for as long as the company is in Inzenda. The basis is contract (b) for the connection and legitimate interest (f) for the log: to protect the company and be able to show what was done.