Loading...
Last updated Mon, 31 Aug 2026 19:39:44 GMT
This is demonstration content for a test workspace. It is not legal advice and it does not describe a real service.
_Last updated: 30 August 2026_
This policy explains what personal data the service holds about you, why it holds it,
where it is kept, how long it is kept, and what you can ask us to do with it. It covers
the workspace application and the public pages around it. It does not cover other
services you may reach from a link here.
What you give us. Your name, your email address, and anything else you type into
your profile — a job title, a department, a phone number, a location, a short biography,
a website. You choose all of it, and you can change or clear it at any time from the
profile settings page.
What you create. Tasks, calendar events, mail, chat messages, documents, orders,
products and customers. This is your workspace's working content. We treat it as yours.
What the service records by itself. The time you last signed in, whether your
account is active, which plan you are on, and the notifications the service sent you.
The service also writes an entry when an administrator changes your role or status, so
that a change of access can be traced later.
What we do not collect. We do not use third-party advertising trackers. We do not
buy data about you from anyone. We do not ask for payment card numbers in this
demonstration workspace, and no card is ever stored.
We hold your account details so you can sign in and so other members can recognise you.
We hold your content so the service can show it back to you. We hold the plan and limit
records so the service can decide what your account may do. We hold the delivery log so
that we can answer "did that notification actually go anywhere?" honestly — in this
workspace the answer is usually no, because no email provider is configured, and the log
says so rather than pretending.
Inside your workspace, other members see your name, avatar, title, department and
presence. They do not see your mailbox, your private calendar, your settings, or your
API keys — those are visible only to you, and the database enforces that with row-level
rules rather than trusting the application to remember.
Outside your workspace, nobody sees your data. We do not share it with other customers.
We share it with a supplier only where the supplier runs part of the service for us — a
hosting provider, a database provider — and only under a contract that holds them to
this policy.
We disclose data to an authority only where the law requires it, and we tell you unless
we are forbidden to.
The database, the file storage and the application all run on managed infrastructure in
a single region. Backups are held in the same region. Nothing is copied to a region you
have not been told about.
Account and content data is kept while your account is open. When an account is removed
from a workspace, the content it created stays with the workspace, and the profile
record is kept for a short period so the change can be reversed, then deleted.
Deleted mail is purged thirty days after it goes to the trash. Delivery logs are kept
for twelve months. Backups roll off on their own schedule, which is shorter than twelve
months.
You can ask to see the data we hold about you, correct it, export it, or have it
deleted. Most of that you can do yourself from the settings pages; anything you cannot,
ask a workspace administrator and they will ask us. We answer within a month.
You can also object to a particular use of your data, or ask us to restrict it while a
dispute is resolved.
Access to the database is limited to the application and to named operators. Every table
enforces row-level rules, so a query that should not see a row does not see it even if
the application asks for it. Passwords are stored as hashes by the authentication
provider and are never visible to us. API keys are stored as hashes too — the full key
is shown once, at the moment it is created, and never again.
If this policy changes in a way that matters, we will tell you in the workspace. For
anything else, use the contact form on the landing page or speak to your workspace
administrator.