Privacy Policy

About this policy

Who is responsible. rodnet.ai ApS (CVR 46686446, Horsens, Denmark) is the data controller for the personal data described here. Write to support@rodnet.ai with any question about it, or choose “Privacy or data request” on our support form. We have not appointed a data protection officer.

What it covers. This policy covers rodnet.ai and these apps:

• Roster (checkroster.com)
• Bavn (bavnscan.com)
• signplume (signplume.com)
• Docplume (docplume.com)
• riffquiz (riffquiz.app)

It describes what we collect about you when you visit these sites, hold an account, play a quiz or contact us.

What it does not cover.

• bizdex has its own privacy policy at bizdex.dk/privatliv, because it also publishes data from public registers.
• What your organisation puts into an app, such as checklists, scan targets and results, staff directories, documents and the email that passes through signplume’s relay. For that content your organisation is the controller and we are its processor, under our Data Processing Agreement. Questions about it go to the organisation that uses the app. If a request reaches us, we pass it on to them.

What we collect and why

Your account

When you create an account in Roster, Bavn, signplume or Docplume, we store:

• your email address, and in Roster, Bavn and Docplume also your name
• your password, only as a one-way hash that we cannot read back
• your organisation’s name, in the apps that have organisations (Bavn, signplume and Docplume)
• when you accepted our Terms of Service and Data Processing Agreement, and which versions

The section for each app below lists what else it keeps. We use account data to give you the account and the features you ask for, to sign you in and to send you the emails the account needs.

Legal basis: our contract with you (GDPR Article 6(1)(b)).

Emails we send you

The apps send the emails an account needs, such as:

• confirming your email address
• password resets, sign-in links and sign-in codes
• invitations from colleagues
• notices about the service you use

Docplume also sends owners and admins a short series of getting-started emails and a weekly summary; see Docplume.

All our email goes through our own mail server, mail.rodnet.ai. We send no newsletters, and our emails contain no tracking pixels.

Signing in and keeping accounts secure

• Sessions. A cookie keeps you signed in (see Cookies). In Roster, Bavn and Docplume, the session record on our server also holds your IP address and browser name. It expires 2 hours after your last activity and is then deleted automatically.
• Protection against abuse. We count sign-in, signup and form attempts per connection to stop password guessing and spam. These counters use your IP address, or a hash of it, and expire within minutes to a day.
• Server logs. Some of our web servers write a technical log line for each request: IP address, the page requested, the time and the browser name. We use these logs to keep the services running and secure. They are rotated automatically and replaced each time an app is updated, so we do not keep them long-term. Application error logs are kept for up to 30 days.

Legal basis: our legitimate interest in keeping the services and your account secure (Article 6(1)(f)).

Paying for a plan

Paid plans in signplume and Docplume are paid through Stripe.

• You enter your card details on Stripe’s own payment page, and they never reach us.
• We give Stripe an email address for billing and our internal number for your organisation. In signplume that is the email address of the admin who subscribes. In Docplume it is the billing email you enter, and we also give Stripe the billing name, address and VAT number you enter.
• We keep the customer number Stripe gives us, the status of your subscription and, in Docplume, the billing details you entered and the card type and last four digits.
• Stripe processes payment data as an independent controller under its own privacy policy.

We keep invoices and payment records for five years after the end of the financial year they belong to, as the Danish Bookkeeping Act requires.

Legal basis: our contract with you (Article 6(1)(b)), and our legal obligation to keep accounts (Article 6(1)(c)).

A short question about what you are trying to do

In Roster, Bavn and signplume, we sometimes ask signed-in users one question: what they are trying to get done with the app. The question comes from our own service at intent.rodnet.ai.

• To know whom we asked and when, the service receives your account number and email address. In signplume it also receives your organisation’s name.
• It remembers whether you answered, postponed or declined.
• If you answer, we store your answer together with the page you were on (without its query string) and your browser’s language.
• It stores no IP address and no browser details.

We use the answers to improve the apps.

Legal basis: our legitimate interest in understanding what our users need (Article 6(1)(f)). You can decline the question for good, and we delete your answers if you ask us.

Website statistics

We measure use of our websites with Umami, which we run ourselves at pulse.rodnet.ai. It sets no cookies and stores nothing in your browser.

What it records for each page view:

• the page address and title
• the site you came from
• browser, operating system, device type, screen size and language
• the country, region and city, looked up from your IP address

The IP address itself is not stored, and the statistics never leave our servers. We also count named events, such as a click on “Create an account”, without your name or email address.

Where it runs:

• every page on rodnet.ai and riffquiz
• the front page of signplume.com and the pages its ads lead to, with the campaign details in the address (source, campaign, ad version and keyword) but never an ad’s click identifier
• the public pages, sign-in pages and signed-in app of Roster, Bavn and Docplume

Legal basis: our legitimate interest in knowing how our websites and apps are used, so we can improve them (Article 6(1)(f)). The statistics contain nothing that identifies you, so we keep them without a fixed end date.

When you arrive from one of signplume’s ads

signplume advertises on Google Search. When you click one of its ads, Google adds a click identifier to the address, and the page you land on records:

• the click identifier and its type
• the campaign details in the address: source, campaign, ad version and keyword
• the area Google reports the click came from, such as a city or region
• which page, and which version of it, you saw
• whether the page’s script ran, whether you moved the pointer, scrolled or typed on it, whether your browser said it was automated, and whether it loaded the page ahead of your click (a prefetch), so we can tell people from bots
• whether you used a phone, tablet or computer, but not your browser’s details

We set no cookie for this and do not store your IP address. If you go on to create an account, we link the visit to your organisation and note when its first signature is in use and when it pays.

Each day, Google Ads fetches a list of which clicks led to a signup, a first signature in use or a payment. The list holds only the click identifier, the time, a random order number and, for a payment, its amount excluding VAT. No name, email address or company goes to Google. We do this to learn which ads are worth paying for.

Legal basis: our legitimate interest in knowing which of our ads work (Article 6(1)(f)). You can object at any time by writing to us. Google uses the list as an independent controller under Google’s privacy policy. A visit that does not lead to an account is deleted after 90 days.

When you contact support

The support form asks for your email address, a subject, a message and, if you like, your name.

• We store these with the app and category you chose, and use them only to answer you.
• We use your IP address briefly to limit how many tickets one connection can send. We do not store it with the ticket.
• We delete the ticket, and our email correspondence about it, at the latest 24 months after its last activity.

In Docplume, “Contact support” inside the app sends us your message by email, together with your organisation, the page you were on and your browser name.

Legal basis: answering your request (Article 6(1)(b) or (f)). Where the request is about your rights under the GDPR, keeping a record of it is also our legal obligation (Article 6(1)(c)).

AI assistants you connect

Bavn, signplume and Docplume let you connect an AI assistant, such as Claude, ChatGPT or Microsoft Copilot, to your account.

• When you do, the assistant’s provider receives the data you ask it to fetch, which can include your name and email address. That happens under your own agreement with that provider.
• We keep a log of which assistant used which tool, and when, for 90 days, so you can see it in the app.
• You can disconnect an assistant at any time.

Legal basis: our contract with you (Article 6(1)(b)).

What each app adds

Roster

• Your account holds your name, email address and password hash. Each account has its own private workspace, and there are no teams.
• Emails: email address confirmation and password reset only.
• No payments.
• Deleting your account: there is no delete button yet. Write to us, and we delete it within 30 days.

Bavn

• Your account holds your name, email address, password hash and the name you give your organisation.
• Emails: email address confirmation only.
• On-premises agents. If you install a Bavn agent in your network, it reports its version, the private network ranges it can see and the public IP address it connects from. This is treated as your organisation’s content under the Data Processing Agreement.
• No payments.
• Deleting your account: there is no delete button yet. Write to us, and we delete it within 30 days.

signplume

• Your account holds your company’s name, your work email address and your password hash.
• How you found us. When you sign up, we keep where you came from: the campaign details in the address, the referring site, the first page you saw and the type of any ad click identifier. If you came from one of our ads, the visit described above is linked to your organisation.
• Signing in. You can sign in with a password or with a link we email you. Where it is offered, you can also sign in with Google or Microsoft. In that case we receive only your verified email address from them and store nothing else.
• Two-step sign-in. If you turn on two-step sign-in, we store the secret for your authenticator app and your recovery codes.
• Session. The session cookie lasts 30 days. signplume does not store your IP address.
• Email log. For each email signplume sends you, we record the address, the kind of email and whether it was delivered. We use this to stop sending to addresses that bounce, and keep it for as long as the account exists.
• Outlook add-in. It runs inside your Outlook and loads Microsoft’s Office library from Microsoft.
• Deleting your account: there is no delete button yet. Write to us, and we delete it within 30 days.

Docplume

• Your account holds your name, company, email address and password hash. If you turn on two-step sign-in, it also holds the secret for your authenticator app and your recovery codes, both encrypted.
• Signed-in devices. Under your account settings you can see your sessions, with their IP address and browser. If you pair the Docplume desktop app, we store the device’s name (by default the computer’s name), its platform, the app version and when it was last seen.
• Getting-started emails. Owners and admins of a new organisation receive a short series of emails about getting started, and owners receive a weekly summary for the first eight weeks. Each email has a link to unsubscribe from that kind of email with one click. Legal basis: our legitimate interest in helping you get started with a service you signed up for (Article 6(1)(f)).
• Product feedback. We record which features each user has started using, so the app can suggest the next step, and any score or comment you give when we ask how likely you are to recommend Docplume. Feedback comments reach us with your name and your organisation’s name. Legal basis: our legitimate interest in improving Docplume (Article 6(1)(f)).
• Shared links. If you open a document someone has shared with you, our server keeps a session record with your IP address and browser name. It expires 2 hours after your last activity and is then deleted automatically. We store nothing else about you.
• Deleting your account: you can delete your own account under account settings, and download your account data as a file there first. If you are the last owner of an organisation, you need to delete the organisation or hand it over first. A deleted organisation is purged after 30 days.

riffquiz

• No accounts. riffquiz has no accounts and no sign-in.
• Your player name. If you enter one, we store it with your score and answers. It is shown on the quiz’s leaderboard to everyone who has the quiz link. Leave the field empty to play as “Anonymous”.
• Retention. Names, scores and answers are kept for as long as the quiz exists. Write to us if you want yours removed.
• Third parties your browser contacts. These companies receive your IP address as part of the request, like any website you visit:
  • Apple: when you play a question, the song preview streams directly from Apple’s servers.
  • Google: riffquiz loads its fonts from Google Fonts.
• Legal basis: running the quiz you take part in (Article 6(1)(b)).

Who receives your data

• Hetzner Online GmbH, Germany, hosts all our servers, databases and backups as our processor.
• Stripe, when you pay for a plan, as described above.
• Google, which fetches signplume’s list of ad clicks that led to a signup, a first signature or a payment, as described above.
• Google or Microsoft, if you choose to sign in to signplume with them.
• The provider of an AI assistant you connect yourself.
• Apple and Google, when you play riffquiz, as described above.
• Public authorities, where the law requires us to share data.

We never sell personal data and never use it to target advertising. None of our apps contains advertising or tracking code from other companies. signplume tells Google Ads which of its ad clicks led to a signup from our own server, as described above.

Transfers outside the EU

All our servers and backups are in Germany. Personal data leaves the EU only in these cases:

• when you pay through Stripe, which may transfer data to the USA under its own safeguards
• when you choose to sign in with Google or Microsoft, or to connect an AI assistant hosted outside the EU
• when your browser fetches song previews from Apple or fonts from Google in riffquiz
• when Google Ads fetches signplume’s list of ad clicks that led to a signup, a first signature or a payment

How long we keep it

Cookies

We set no tracking, advertising or third-party cookies, and our website statistics use no cookies. That is why we show no cookie banner.

The cookies we do set are needed to sign you in and to protect forms:

rodnet.ai and riffquiz set no cookies.

Browser storage. Roster, Bavn and Docplume store your display preferences, such as light or dark theme and whether the sidebar is open, in your browser’s local storage. signplume uses session storage briefly during two-step sign-in.

Your rights

You have the right to:

• see the personal data we hold about you
• have it corrected
• have it deleted
• restrict how we use it
• receive it in a portable format
• object to processing based on our legitimate interest (Article 6(1)(f))

To use any of these rights, write to support@rodnet.ai or choose “Privacy or data request” on our support form. We answer within one month.

If you think we handle your data wrongly, you can complain to the Danish Data Protection Agency (Datatilsynet), Carl Jacobsens Vej 35, 2500 Valby, Denmark, dt@datatilsynet.dk, datatilsynet.dk.

We make no decisions about you based solely on automated processing, and we do not profile you.

Changes to this policy

We publish every change on this page with a new version number and date. This policy is published in English and Danish. If the two versions differ, the English version prevails.

Version. Version 1.0, effective 22 October 2026, first published.