GATE Security Overview

In short

• Your content stays yours. GATE does not use your content to train AI models. On Stable and on a dedicated server, nothing GATE sees is used to improve GATE.
• Choose how isolated you are. Business customers can run on Stable, our controlled release track, or by agreement on a dedicated server of their own. On both, GATE staff hold no account in your organization and open your content only when you ask.
• Hosted in the EU. Servers, database and files run in Germany and Finland. AI model calls go to the providers listed on our Subprocessors page, which also says how each transfer is protected.
• In writing. Our Data Processing Agreement under GDPR Article 28: breach notice to you within 48 hours, 30 days notice of new subprocessors on Stable, audit rights, and your data returned to you or deleted when the agreement ends, as you choose.

Where your organization runs

GATE runs on three kinds of infrastructure. The difference matters most for who can see your content.

An organization runs on Edge until it moves, and can ask to move to Stable or a dedicated server at any time at legal@gate.software. Section 11a of our Privacy Policy and section 7 and Annex 4 of the DPA set this out in full.

Who can access your content

• Your own people. Owners manage members, bots and settings. Members reach the bots they are given, all of the organization’s bots unless an owner limits it, and those bots’ ordinary chats. Private chats stay with their participants.
• Your bots. Each of your bots belongs to your organization and works with the integrations and data your people connect to it.
• Other customers. No feature lets another customer’s organization or its bots reach your content, and every signed-in request is checked against the organization it touches.
• GATE staff on Stable and dedicated servers. No standing access. GATE staff hold no account in your organization. The tools GATE uses to run these servers reach their health, logs and services, and have no command for reading your chats, files or memory. When you ask us to look at something, we do it case by case. Every person added to your organization, GATE staff included, is recorded and shown to your owners in the organization’s access log.
• Authorities. We disclose your data to an authority only where Union or Member State law requires it, and we tell you first unless that law prohibits it.

Isolation between customers

Each chat and memory is stored under exactly one organization, and each bot is assigned to one. People can belong to several organizations, and each membership is separate. Every signed-in request is checked against the organization it touches, and where relevant the role, bot and chat, before data is returned. Private chats additionally check that the person is a participant.

Each bot runs as its own operating-system user with its own home directory and its own credentials. Each customer’s agent processes run in their own resource-limited group, which limits how much of a server one customer’s agents can use. On a dedicated server, no other customer’s organization runs on the machine.

Identity and sign-in

• No passwords. People sign in with a passkey, a one-time emailed link valid for 10 minutes, or their Google or Microsoft account. Requests for sign-in links, and attempts to use them, are rate limited.
• Sessions. Session cookies are HttpOnly, Secure and SameSite, and session tokens are stored only as hashes. A session lapses after at most 30 days without use and ends after 180 days at the latest.
• Removing access. Removing a member ends their access to your organization immediately.
• Bots authenticate with their own tokens, never a person’s session.

Encryption

• In transit. Connections to GATE over the internet use TLS, and the GATE application sends HSTS.
• Secrets at rest. API keys, integration tokens and vault secrets are encrypted with AES-256-GCM under a keyring we can rotate. The one exception is the sign-in files for the AI accounts bots run on, which are stored as files readable only by the bot’s own system account and our server administrators.
• Google and Microsoft. Access tokens for Google and Microsoft mail, calendar and files are held by our integration provider, not on our servers.

AI models and your data

• No training. GATE does not use your content to train AI models. Providers whose terms allow training on data, and providers in China, are off by default and used only after your organization turns them on. Our DPA names the one always-on service whose terms allow it to use message content to improve its service: our transactional email provider.
• What a model receives. A bot sends a model the conversation, the memory notes relevant to the message, and the results of the tools it uses, not your whole account.
• Memory search is computed on GATE-operated servers in Germany, without an outside AI vendor.
• Your own AI account. Where your plan includes it, your organization can connect its own account or API keys with an AI provider, and its bots then run under your own agreement with that provider.
• Your connected systems. Bots read mail and files when a task needs them. Calendars, WhatsApp and Slack, once connected, are synced or stored so your bots can work with them. Disconnecting an integration ends your bots’ access at once and asks the provider to revoke the token.
• Keeping everything in the EU. By default, model calls go to the providers on our Subprocessors page. If all processing must stay in the EU, we scope an EU-only setup with you.

Logging and transparency

• Tool calls a bot makes are recorded in the chat they ran in, and shown to the people with access to that chat.
• Sign-ins, session and token revocations, role and membership changes, invitations, organization settings changes and renames, bot changes, secret reads and writes, and certain access denials are written to an audit log. Your owners see the organization-level part of it in the organization’s access log.
• When GATE staff or an operational bot opens a chat in your organization through GATE, an audit record is written and shown to your owners in the access log.
• Audit records are integrity-signed when written and kept for 90 days. On a dedicated server, GATE can also forward every audit record, signed, to a log collector you operate.

Secure development

• Changes reach production through pull requests. A change is merged only when GATE’s required automated checks, including security checks, pass, and any override of a failing check is made by a named GATE operator and logged.
• Stable servers receive only releases that have been promoted after running on Edge.
• Third-party dependencies are locked to exact versions, and a vulnerability audit runs every week and whenever dependencies change.

Backups and availability

• Each production server’s disk is backed up daily by our hosting provider, outside the server, and the last 7 backups are kept. Once data is deleted from the live system, it leaves the backups within 7 days.
• The platform and every server that serves organizations are monitored around the clock, from inside and from outside GATE.

Incidents and breach notification

• Under the DPA we notify you within 48 hours of becoming aware of a personal-data breach affecting your data, with what is known and more as it is learned.
• Where GATE is controller, we notify IMY, the Swedish data protection authority, within 72 hours.
• We cooperate with your own notifications to authorities and to the people affected.

When the agreement ends

You choose within 30 days whether we return a copy of your data to you or delete it. Deletion is complete within 30 days of the request, and backup copies roll off within 7 days after that. A copy of your data is also available on request during the agreement. People can delete their own account in Settings, and owners can remove members and bots.

Shared responsibility

GATE operates the platform and its servers, runs its security controls, and chooses its subprocessors and binds them by contract, as our DPA sets out. Your organization decides who is a member, which bots each member reaches, which integrations and data its bots may use, and which optional AI providers are on. We recommend that a business customer keeps the number of owners small, connects only the systems its bots need, and leaves the optional providers off.

Questions and reporting a vulnerability

For a signed DPA or answers to a security questionnaire, email legal@gate.software. To report a security vulnerability, email legal@gate.software with “Security” in the subject, as our security.txt says.