Trust Center · Wesentlich AS, Norway

Your strategy is the most sensitive thing you own. Here is exactly how we protect it.

Everything a CTO needs to validate One Page, and everything a data protection officer or authority needs to check how we handle personal data. Written plainly, kept current, and backed by documents you can ask for.

Last updated
18 November 2026
Next review
December 2026

For your CTO or IT security team

Architecture, tenant isolation, authentication, AI handling and how we test it

For DPOs, legal and supervisory authorities

Roles under GDPR, sub-processors, transfers, retention, rights and breach handling

  • EUCustomer data stored in the EU
  • AES-256 · TLS 1.2+Encrypted at rest and in transit
  • NeverYour content used to train AI models
  • AkaidoAI penetration testing of the live service
  • MonthlyHuman-led AI security review by our CTO

01 · Testing and reviews

Tested by machines, reviewed by a person, every month

AI systems open new kinds of attack, such as prompt injection and data leaking between clients. We test for them continuously with AI, and a named person checks the results and our suppliers by hand.

Active

AI penetration testing with Akaido

Akaido runs AI-driven attacks against the live service the way a real attacker would: broken access control, cross-client data access, authentication bypass, injection and prompt injection against our AI features.

Scope
Web app, APIs, server functions and AI features
Findings
Fixed by severity; summary report under NDA
Every month

Monthly human-led AI security review

Every month our CTO personally reviews the service and every third party it relies on. Automated tools find patterns; a person judges what matters and signs it off.

Our service
Akaido and security-scan findings, access rules, AI prompts and guardrails, audit logs
Third parties
Every sub-processor: terms, data use, incidents, certifications
Output
Signed review log, actions tracked to closure

And automated checks before and between releases

  • A security scan of database rules and exposed data before every publish
  • Regular deep security scans of the code: sign-in, access, secrets and data exposure
  • Dependency scanning on every build
  • Manual review of any change to sign-in, access rules or payments
  • Audit logging with alerts on unusual activity
  • Secrets in an encrypted vault, never in code

02 · Architecture

Where your data goes, layer by layer

A short path with few hands on it. Every request goes through the same checks, whether it comes from our app or straight at our API.

Layer
Provider · location
How it is protected
App and edgeReact app, server functions
Provider · location: Cloudflare Workers · global edge, no data stored
How it is protected: TLS 1.2+ only. Every private action runs in a server function that checks who is calling before doing anything. The service key never leaves the server.
DatabasePostgreSQL
Provider · location: Lovable Cloud (Supabase on AWS) · EU (Stockholm, Sweden)
How it is protected: AES-256 at rest. Row-level security on every table, so a direct request gets the same answer as the app. Daily encrypted backups and point-in-time recovery.
File storageBrain uploads
Provider · location: Lovable Cloud · EU, private buckets
How it is protected: AES-256 at rest. No public links; files are only served to people with access to that One Page.
Live updatesPresence, fresh data
Provider · location: Lovable Cloud · EU
How it is protected: One room per page. Live updates only reach people allowed to read that data.
AI modelsVia our AI gateway
Provider · location: Google Gemini, OpenAI
How it is protected: Calls go through a gateway that checks the user's role first. No training on your content. Prompts and answers are not kept after the request.
Web researchRadar, Diagnosis
Provider · location: Firecrawl
How it is protected: Reads public websites only. It receives the web addresses to check, never the content of your One Page.
EmailReminders, alerts
Provider · location: Lovable Cloud (email) · Sent from theonepage.ai
How it is protected: Sent only by the server. Each person can turn their own emails off.

03 · Access and isolation

One client can never see another

Access is decided inside the database, not just hidden on screen. Advisors work with many clients, so separating them is the first thing we test.

  • Row-level security on every table

    Each query is filtered to the One Pages the signed-in person has been given. Rules for page, tab and workspace access are shared database functions, checked automatically on every build.

  • Roles stored apart from users

    Page Owner, Leader, Team member and Viewer live in their own table and are enforced by a locked-down database function, so nobody can raise their own role.

  • Hidden means not sent

    When a tab or AI is off for a role, its data is never sent to that person's browser and AI requests are refused on the server.

  • Advisor workspaces are separate

    Each advisor sees only their own clients, hours and invoices. Removing an advisor removes that access at once.

  • Share links you can take back

    Links use long, unguessable tokens and can be revoked at any time. Every access change is written to the page history.

04 · Sign-in and accounts

Short-lived sessions, strong passwords

  • Two ways in

    Email and password (hashed with bcrypt) or Google single sign-on (OAuth 2.0).

  • Leaked-password check

    Passwords found in known breaches (Have I Been Pwned) are refused.

  • Short sessions

    Short-lived tokens with refresh-token rotation, so a stolen token expires fast.

  • Two-step sign-in

    Not available yet. It is on our roadmap.

05 · AI and your data

Your strategy is never training data

Neither by us nor by the AI providers we use. The monthly review checks that the providers' terms still say so.

  • Used only to answer your request

    Prompts and answers are not kept by the providers after the request.

  • One client's context at a time

    The AI only reads the One Page you are working in. Context from one client is never mixed into another.

  • Nothing changes without a yes

    Rewrites and suggestions are proposals until a person accepts them.

  • You decide who can use it

    The Page Owner can limit AI to certain roles or switch it off. Strategy chats are private to each person.

06 · Backups and resilience

Nothing is lost when something breaks

  • Saves never vanish

    Edits queue in order and retry until the server confirms, even after a dropped connection.

  • Your own copy

    Export your data at any time. Page Owners can also download a backup of a whole One Page.

  • SOC 2 Type II hosting

    Cloudflare and Supabase/AWS hold SOC 2 Type II reports.

Part two · Data protectionFor DPOs, legal teams and supervisory authorities

07 · Roles under GDPR

Who is responsible for what

One Page is provided by Wesentlich AS, registered in Norway (EEA), and operated in line with the GDPR as it applies in Norway through the Personal Data Act.

We are processor · Art. 28

The content your organisation adds

Strategy, goals, people named as owners, comments, uploaded files and chats. The organisation using One Page is the controller. We only process this on its instructions, under a data processing agreement (DPA).

We are controller · Art. 24

Accounts, billing and security logs

Name, email, sign-in records and invoices. Lawful basis: contract (Art. 6(1)(b)) to run your account, legal obligation (6(1)(c)) for bookkeeping, and legitimate interest (6(1)(f)) for security logging.

Legal entity
Wesentlich AS
Supervisory authority
Datatilsynet, Norway
Data location
EU / EEA

08 · Sub-processors

Every company that touches your data

Each one is reviewed by our CTO every month.

Company
Purpose and data
Location
Transfer safeguard
Lovable Cloud (Supabase, AWS)
Purpose and data: Database, files, live updates. All customer content and account data.
Location: EU
Transfer safeguard: Stays in the EEA
Cloudflare
Purpose and data: Runs the app close to users. Data passes through; nothing is stored.
Location: Global
Transfer safeguard: —
Google (Gemini)
Purpose and data: AI features. Only the text sent with each AI request.
Location: —
Transfer safeguard: No training, no retention
OpenAI
Purpose and data: AI features. Only the text sent with each AI request.
Location: —
Transfer safeguard: No training, no retention
Firecrawl
Purpose and data: Reads public websites for Radar and Diagnosis. Web addresses only.
Location: —
Transfer safeguard: No personal data sent
Lovable Cloud (email)
Purpose and data: Sends reminders and alerts. Name, email address and email content.
Location: —
Transfer safeguard: —

09 · Retention and deletion

Kept only as long as it is needed

  • One Page content and files

    Until the One Page is deleted or the contract ends.

  • AI prompts and answers

    Not kept by the AI providers after the request. Strategy chats are stored with the One Page and deleted with it.

  • Our invoices to you

    5 years, as the Norwegian Bookkeeping Act requires.

10 · Your rights

Ask, and we answer within a month

If your data is on a One Page that belongs to another organisation, we pass your request to them as controller and help them answer.

See

A copy of what we hold about you

Correct

Fix anything that is wrong

Export

Take your data with you

Delete

Have it erased

Object or restrict

Limit how it is used

Complain

To Datatilsynet or your local authority

See

A copy of what we hold about you

Correct

Fix anything that is wrong

Export

Take your data with you

Delete

Have it erased

Object or restrict

Limit how it is used

Complain

To Datatilsynet or your local authority

11 · Incidents and breaches

If something goes wrong, you hear it from us first

  1. Hour 0

    Detect and contain

    Audit-log alerts reach the CTO. Access is cut and evidence kept.

  2. Tell affected customers

    Without undue delay: what happened, what data, what we are doing.

  3. Within 72 h

    Notify Datatilsynet

    For data we control (Art. 33). For your data, we give you what you need to notify.

  4. Afterwards

    Fix and report

    People at high risk are told directly (Art. 34). A written review follows.

13 · Report a vulnerability

security@theonepage.ai

  • Acknowledged within 2 business days
  • Confirmed issues targeted for a fix within 30 days
  • Safe harbour for good-faith research

Privacy questions and requests

  • DPAs, documents and data subject requests
  • Wesentlich AS
  • Answered within one month, usually much sooner