Gridfloo
FeaturesSolutionsPricingDownload
Sign inRequest access
Product
All featuresFlowsMy DayStudioCommunicationGridfloo AIGridfloo BrowserSolutionsPricingDownload
Resources
Getting startedWhat's newHelp centreSupportSecurity and privacy
Request accessSign in
HelpSupportTermsPrivacySecurity

Security

Last updated 3 November 2026

Gridfloo holds a company’s work: its projects, flows, documents, files, conversations and, when connected, its mail and calendars. This page explains how we protect it: how access is controlled, where data is kept, how backups are made and tested, and what is not there yet. We think you should know both what is in place and what is still being built. Questions go to security@gridfloo.com.

Your data stays yours and remains separate

  • Access is enforced in the database itself, not only in the app. Every request is answered with the rights of the person asking, so a mistake on one screen cannot show one company’s data to another.
  • Changes to these rules are proved, not assumed. Before a change to who-sees-what goes live, we record what every user can see and compare it after the change; it ships only with zero differences.
  • Files follow the same rules. A file is handed out through a short-lived signed link, issued after the same permission check as the item it belongs to — or through a share link that someone with access deliberately created.
  • Access tokens for connected mailboxes and calendars are kept on the server and never sent to the browser.

You can take everything with you

  • Workspace export: an owner or admin can download a full copy of the workspace at any time — every record, every file and earlier versions, chat files, receipts and the member list — in open formats (JSON, CSV and the original files) that need nothing from Gridfloo to read. Passwords and sign-in keys are never included.
  • Your own copy, in your own storage: Gridfloo can send that full copy every day or every week to a bucket your company owns (Amazon S3, Cloudflare R2 or any S3-compatible storage), so you always hold a current copy, whatever happens to Gridfloo. Gridfloo only needs permission to write there; your bucket’s own rules decide how long copies are kept, and a failed copy alerts your workspace admins.

Signing in

  • People can sign in with their Microsoft or Google work account. Your company’s own rules for those accounts then apply, as far as your IT has set them up: for example two-factor authentication, conditional access, approved devices, and switching an account off when someone leaves.
  • Sign-in by e-mail code is available for people without either, with optional two-step sign-in: after the e-mail code, a code from an authenticator app (with one-time recovery codes as a fallback). Each code works once, and five wrong ones lock it for 15 minutes. A workspace can require it.
  • Your rules for your workspace: its admins choose which ways of signing in it accepts, and can require your company’s own accounts (your Microsoft work tenant or Google Workspace domain). This is enforced by the database itself: work in a workspace stays closed to anyone who signed in another way.
  • Verified company domains: a workspace proves it owns its e-mail domain with a DNS record, which is checked again every day. A domain can be verified by one workspace only.
  • Joining with a company address, if the workspace allows it: people whose sign-in proves an address at a verified domain (a Microsoft work account, a Google Workspace account of that domain, or a code sent to the address) can join directly, or ask and wait for an admin to approve. Someone who left or was removed can only ask to join again; an admin decides.
  • Signed-in devices: everyone can see where their account is signed in (Profile › Account) and sign out any device, or all but the one in front of them. A signed-out device is refused at once, and anything it has open closes within 15 minutes.

Encryption

  • In transit: every connection between you, Gridfloo and the services it uses (mail, calendars, AI, storage) is encrypted with HTTPS/TLS.
  • At rest: the database and stored files are encrypted at rest by the providers that hold them (AES-256 at Supabase and Cloudflare R2). This covers documents, files, and mail and chat attachments.
  • Backups: encrypted before they leave, with a key only Gridfloo holds, offline. The provider that stores them cannot read them.
  • On your devices: what Gridfloo keeps for offline use (in the browser or the desktop app) is protected by your device’s own security: its sign-in and disk encryption.
  • Gridfloo is not end-to-end encrypted: our servers must read your data to search it, share it and run the features you use. Who may see it is controlled as described above.

Backups, and proof they work

  • Every night, the whole database and every file are copied off-site, to a different provider and region than the live system (Amazon Web Services, Singapore).
  • Copies are kept for 180 days. For the first 30 days they are locked: nobody can delete or change them, Gridfloo included.
  • A failed or late backup alerts us immediately, and our backup dashboard flags a copy that is much smaller than the night before.
  • Restores are tested every quarter. The last test, on 4 October 2026, restored the full database with no errors: every table, rule and row accounted for.
  • On top of this, the database provider keeps its own daily backups.
  • How much could be lost, and how fast we restore: the newest copy is at most one day old, so in a disaster up to a day’s changes could be lost. Continuous backup, which cuts that to minutes, is switched on when a customer needs it. We aim to have the service running again within one working day of a disaster.

Audit log and accountability

  • Audit log: workspace admins see who did what — sign-ins (including failed ones and ones refused by the workspace’s sign-in rule, with country), members and roles, invitations, sharing and public links, files deleted, exports and their downloads, backups to your own storage, settings and billing.
  • Filter it by kind, person and date, and download it as a spreadsheet (CSV).
  • Entries cannot be changed or deleted by anyone, Gridfloo included; the database refuses it. The log is part of the workspace export, and it outlives a deleted workspace.
  • It is kept for as long as the workspace exists, and after it is deleted, so what happened can still be shown.

How we protect and operate Gridfloo

  • Our administrator accounts for code, hosting, database, file storage, backups, payments and company e-mail all use two-factor authentication.
  • Every change to the code is scanned for accidentally included passwords or keys.
  • Backup credentials can only write new copies; they cannot read or delete existing ones.
  • No one at Gridfloo reads your content unless you ask us to (for support), it is needed for security, or the law requires it.
  • Support access needs your yes: Gridfloo staff can open a workspace they are not a member of only when one of its admins allows it (or lets support in), with a reason and for at most 8 hours. Only for a security problem or a legal order may they open it without asking; it is then marked as an emergency in your audit log and your admins are told at once. Every step is written in the workspace’s audit log.

Where data is kept

  • Database: Japan (Tokyo). Files: Cloudflare, Asia-Pacific. Encrypted backups: Singapore.
  • The full list of providers, and what each one does, is in the privacy statement (section 6).

AI and your data

  • Your workspace content is never used to train AI models by Anthropic or OpenAI. Moonshot AI’s terms do not clearly rule this out, so Moonshot is off unless a workspace admin chooses to allow it, and its retention is not stated.
  • You decide which AI providers may be used: workspace admins choose them. Gridfloo never quietly switches to a provider your workspace has not allowed; if none is allowed where someone is, AI is simply off for them.
  • Only what the task needs is sent: the text, document or picture the person asked about, nothing more.
  • AI acts as the person, never with more rights: it can only see and change what that person may see and change. Changes to people and access (invitations, roles, groups) and meetings with other people wait for the person to confirm them.
  • The providers today: Anthropic and OpenAI (United States) and, only where a workspace allows it, Moonshot AI (outside the EU; its China service in mainland China). What each one does is in the privacy statement (section 6).
  • How long providers keep it: Anthropic and OpenAI process requests under their business (API) terms, which exclude training, and may keep them for up to 30 days to detect abuse, then delete them.

Privacy and GDPR

  • Gridfloo is provided by Leworks International AB, Stockholm, Sweden, and works under the GDPR.
  • For a company’s workspace, the company decides about the data and we process it on its behalf. A data processing agreement is available on request.
  • See the privacy statement for what is stored, why, and your rights.

On request and planned

These are not available yet. If your organisation needs one of them, tell us: it decides what we build next.

WhatStatus
Files in your own storage: your workspace’s files kept in your own S3-compatible bucketOn request
EU data centre: database and files kept in the EUPlanned
Single sign-on (SAML) and user provisioning (SCIM)On request. Domain verification, which it builds on, is in place.
Independent penetration testPlanned
Continuous backup: minutes instead of a dayOn request
ISO 27001 certificationNot yet. We will say so here when it is under way.

If something goes wrong

  • A failed or late backup alerts us at once, and the audit log records every sign-in, including refused ones.
  • If a security incident affects your data, we investigate at once, stop it, and tell the affected workspace admins without undue delay, and at the latest within 72 hours, with what happened, what data was affected and what we are doing. As your processor, we help you meet your own GDPR duties, including the 72-hour notice to the authority.
  • Afterwards we say what we changed so it does not happen again.

Reporting a vulnerability

If you believe you have found a security problem, write to security@gridfloo.com. We answer quickly, keep you informed while we fix it, and will not take action against good-faith research that avoids other people’s data.

Gridfloo

One connected workspace for your work, your team and the people you work with.

Product

All featuresFlowsMy DayStudioCommunicationGridfloo AIGridfloo Browser

Gridfloo

SolutionsPricingDownloadRequest access

Resources

Getting startedWhat's newHelp centreSupportSecurity and privacy

Legal

PrivacyTermsSecurity