Privacy Policy

1. Who is responsible

BusinessMode is operated by Frej Dahl Linneke in Denmark under the business name BusinessMode. The business is currently unregistered and is not a separate incorporated company. For privacy questions and requests, contact [email protected].

For the account, billing, support, website and security purposes described here, Frej Dahl Linneke, operating BusinessMode, is the data controller. When a business customer supplies personal data to manage access to its own application, that customer determines the purposes of the processing and BusinessMode acts on its behalf under the Data Processing Agreement. If your request concerns access provided by that customer, contact the customer first; we assist it with requests within our processor role.

2. Information we handle

• Accounts and administration: your name or profile information where supplied, email address, authentication identifiers, session information, Workspace and Project memberships, roles, selected settings and invitations.
• Customer access data: customer-supplied external user identifiers, Organization and administrator details, Licenses, features, seats, assignments, access-code redemptions and associated access or audit history.
• Billing and payments: subscription and plan details, invoice and payment references, billing contact information, payment status and relevant merchant connection details. Stripe-hosted interfaces handle payment-card entry; do not send raw card details to BusinessMode.
• Support and correspondence: information you send in a support request and records needed to investigate and answer it.
• Usage and technical information: event times, sanitized page paths, browser or device context, internal account identifiers where enabled, access decisions, operational records and error information. Hosting and other providers can receive network metadata such as IP addresses.
• Optional reviews: the review, selected display details and an avatar you expressly provide for that purpose, together with consent and moderation records.
• Privacy requests: the request, information needed to verify authority, processing status and a minimal record of the outcome.

We receive information directly from you, from authorized administrators and customers who invite or provision you, from use of the service, and from providers such as authentication and payment services. The service is intended for business customers. Customers should use internal identifiers and minimize the personal data they submit. Special-category data, criminal-offence data and raw payment-card data are not intended inputs.

3. Purposes and legal bases

We use account and service information to provide access, operate the service, communicate about an account and carry out a subscription. Where you personally contract with us, necessary processing is based on performance of that contract or steps you request before it. For contacts acting for a business customer, we rely on our legitimate interests in administering that relationship and providing the requested service, subject to your rights.

We use billing records to collect and reconcile payments and comply with applicable accounting and tax obligations. We process information needed for security, abuse prevention, fault diagnosis, support and establishing or defending legal claims on the basis of our legitimate interests, except where a specific legal obligation applies.

Optional persistent browser analytics, session replay and publication of a personal review depend on your consent. Where permissible, limited service measurement relies on our legitimate interests in understanding and improving the service; consent is required wherever applicable law requires it. The presence or absence of a cookie does not determine that legal question. You can withdraw consent without affecting processing already lawfully carried out.

Customer-controlled application data is processed under the customer's documented instructions and DPA. The customer is responsible for its own legal basis and notices. We do not claim that our service agreement supplies a legal basis for every use a customer makes of personal data.

4. Cookies and analytics choices

The Cookie Policy describes authentication and preference storage, basic cookieless measurement and optional persistent analytics and masked replay. Before opt-in and after choosing No, basic cookieless measurement can continue. Choosing No does not disable authentication, security processing or all server-side operational events.

Optional product analytics uses internal identifiers rather than intentionally sending your name or email address. Captured browser content is minimized and masked. Pseudonymous identifiers and masking reduce exposure but do not make all information anonymous. Change your choice through Analytics settings in the website footer or Privacy & Data in the product. Withdrawal does not automatically erase records already delivered to a provider.

5. Recipients and service providers

We use infrastructure and specialist providers for hosting, database storage, authentication, private exports, transactional email, payment processing, analytics, error monitoring and editorial content. Relevant services include Hetzner, Supabase, Resend, Stripe, PostHog, Sentry and Sanity, according to the function used. See Service providers and subprocessors for their roles. A payment provider may act as an independent controller for some of its own regulatory and payment purposes.

Authorized customer administrators can see information appropriate to their roles. Customer-configured webhooks and integrations send relevant events to destinations selected by that customer. We may disclose information when required by law, to professional advisers subject to confidentiality, or where necessary to establish, exercise or defend legal claims. If the business is transferred, any necessary transfer of personal data must remain subject to applicable safeguards and notice requirements.

6. Storage and international processing

Production database storage is hosted by Supabase in the EU Ireland region. Supabase also provides authentication and private storage for personal-data export files. BusinessMode application hosting is on Hetzner in EU-central. Email, payments, analytics, monitoring and editorial content involve separate provider systems.

BusinessMode's location in Denmark does not mean that every provider stores or accesses data only in Denmark or the EEA. Provider processing and support can involve other countries. Where a transfer is subject to GDPR restrictions, it must use an applicable adequacy decision or appropriate safeguards, such as the European Commission's standard contractual clauses with any necessary additional measures. This policy does not promise EU-only hosting. Contact [email protected] for information about a particular processing arrangement and the applicable safeguards.

7. Retention

We retain personal data for the purposes for which it is needed and applicable legal obligations, rather than applying one period to all records. Relevant criteria include whether an account or customer instruction remains active, whether a record is needed to support access or billing history, an unresolved support or security issue, a legal retention requirement, and the time reasonably necessary to handle a claim or demonstrate the handling of a privacy request.

• Account and customer access records: ordinarily remain while the account and processing relationship continue. Cancelling a paid subscription is not a deletion request. Customer-controlled data follows the customer's instructions and the DPA; deleting one administrator's profile does not delete an entire customer's dataset.
• Personal-data exports: generated export files expire after seven days and are removed by the cleanup process. A signed download link lasts at most one hour, or the remaining file lifetime if shorter. Copies you download remain under your control.
• API retry records: encrypted replay records used for safe retries have a 24-hour lifetime and are removed by scheduled cleanup after expiry.
• Unassociated payment work: pending work awaiting a merchant connection has a seven-day cleanup rule.
• Accounting records: where Danish bookkeeping law applies, required bookkeeping material is generally retained for five years from the end of the financial year concerned. This applies to the necessary financial records, not every item in an account.
• Audit, security, delivery and support records: retained according to their continuing operational, security, legal or accountability purpose. Not all of these records have automatic age-based deletion. Applicable erasure requests and account deletion may remove or de-identify records within their scope.
• Provider records and backups: follow separate provider processing and retention arrangements. Deleting active application data does not instantly rewrite every backup, erase sent email or erase payment records that must lawfully be retained. Data retained solely for recovery or legal purposes must remain restricted to that purpose.

We delete or de-identify personal data when it is no longer needed, subject to lawful retention. A truly anonymous aggregate can be retained without retaining a person's or customer's identifier. Contact us for the retention criteria and status relevant to a specific record or request.

8. Exports, deletion and security

The product provides separate requests to export your personal data, delete your user profile and, for an authorized owner, delete a BusinessMode account. Sensitive actions require identity and authority checks. A sole owner must arrange ownership transfer before deleting their profile if the account is to remain.

A personal export contains the requester's supported personal records, not a full dump of every customer, Workspace or downstream provider. Broader returns and provider-held records can require assistance. Account deletion affects that account's Projects and customer access records; it does not delete other people's independent accounts or automatically cancel subscriptions in a separate customer-owned merchant account.

Deletion includes provider follow-up where needed. A submitted provider request is not proof that erasure is complete. We distinguish completion from records lawfully retained and outstanding provider work. Access controls, scoped credentials, protected export downloads and minimized telemetry help protect data; no service can guarantee absolute security.

9. Your rights

Subject to applicable law, you can request access, correction, erasure, restriction and portability of personal data, and object to processing based on legitimate interests. You can withdraw consent at any time. We may need reasonable information to verify your identity or authority without collecting more than necessary.

Send requests to [email protected] or use the available product controls. We respond within the time required by law, ordinarily one month for a GDPR request, and explain any lawful extension or refusal. Where a business customer is the controller, we refer or assist the request through that customer.

You may complain to the Danish Data Protection Agency, Datatilsynet, or the supervisory authority competent for your residence, workplace or the alleged infringement. See datatilsynet.dk. You need not contact us before exercising that right.

BusinessMode makes access decisions from customer-configured features, assignments, capacity and validity rules. It is not intended to make decisions about employment, credit or similarly significant matters on its own behalf. Customers remain responsible for any legally significant use they make of access decisions.

10. Changes and contact

We update this policy when practices or applicable requirements change and provide additional notice where required. The effective date identifies this version. Privacy contact: [email protected].