Supported Salesforce Sandbox access
A Sandbox administrator with the required Salesforce permissions can connect a supported Salesforce Sandbox directly. OrgMate is authorized during the connection flow; no prior app installation is required.
Technical detail
Security, data handling, and access controls
This page explains the access OrgMate requests, how connection material is protected, which providers handle service data, and which controls remain in your hands.
Information current as of .
Access
Salesforce access and product behavior
Salesforce defines what an OAuth scope can permit. OrgMate uses that access more narrowly for metadata analysis.
Exactly two requested scopes
OrgMate explicitly requests api to retrieve and analyze supported
Salesforce metadata, and refresh_token to keep the connection usable
across sessions.
Implicit identity access
Salesforce also supplies identity information with this OAuth flow.
identity is not a third explicit requested scope.
Why Salesforce shows a broad API permission
The Salesforce api scope is technically broad enough to permit record
access. OrgMate uses predefined retrieval paths for Salesforce identity,
organization information, and supported configuration metadata. It does not
query or retrieve Salesforce customer record data or expose a feature for doing
so. Automated tests cover these supported retrieval paths and verify their
expected metadata-only behavior.
Connect and reconnect
When OrgMate finds a usable Salesforce connection for your account, it returns you to the application without another Salesforce redirect. An explicit reconnect asks Salesforce for approval again.
Protection
Connection and account protections
Data in transit
Public OrgMate entry points use HTTPS to protect data in transit.
Stored Salesforce tokens
OrgMate encrypts Salesforce access and refresh tokens with a dedicated key before saving them to its database. Salesforce token values remain internal to OrgMate. They are never returned in product responses or included in records about revocation attempts.
Account isolation
Each Salesforce connection belongs to one authenticated OrgMate account. Server-side ownership checks prevent one account from using another account's connection. Automated tests use two separate accounts to verify this boundary when connecting a Salesforce Sandbox, retrieving account and connection information, using tokens, disconnecting, and revoking access. This is logical separation inside OrgMate, not a claim of separate physical infrastructure or independent certification.
Short-lived OAuth state
OAuth callback state expires after 10 minutes and can be used only once. OrgMate consumes it before exchanging the authorization code.
Email login codes
Email login codes expire after 10 minutes and are stored as hashes.
Authentication telemetry
Current authentication flows write a limited set of operational event fields. At the database boundary, known credential- or sensitive-data top-level field names—including secrets, tokens, codes, cookies, passwords, IP addresses, and email addresses—are rejected. This targeted safeguard applies to authentication event context, not every logging or telemetry surface.
Data
Stored data and current service providers
OrgMate stores the account and connection state needed to provide the service, including encrypted token material, retrieved metadata, Assessment information and progress, user questions and conversation state, and limited service telemetry.
What is sent for LLM processing
OrgMate sends OpenAI the relevant user question, OrgMate instructions, and selected context needed for the task. OrgMate does not retrieve, store, or send Salesforce customer record data.
| Provider | Purpose | Data category | Processing location | Data use or training |
|---|---|---|---|---|
| Hetzner Online GmbH | Hosts OrgMate's application, database, cache, public website, and network edge. | Service data stored or transmitted through the current core host. | Nuremberg, Germany. | Hetzner is an infrastructure provider, not an AI training service. Its data-processing terms govern this processing. |
| OpenAI | Processes supported OrgMate questions and analysis through its API. | The relevant user question, OrgMate instructions, selected context for the task, and the generated answer. | OrgMate uses OpenAI's global API endpoint and does not claim an OrgMate-specific processing region. | OrgMate has not opted in to share API inputs or outputs for model training. Under OpenAI's business and API terms, those inputs and outputs are therefore not used to train OpenAI models. OpenAI documents up to 30 days of default abuse-monitoring retention for API data. OrgMate does not claim modified or zero-retention settings. |
| Google mail infrastructure | Google mail infrastructure is configured to send invited-account login codes, send website-form submissions to contact@orgmate.io, and receive mail for the orgmate.io domain. |
Account and form contact details, one-time login messages, submitted org context and message content, delivery metadata, and inbound message content. | The Google Workspace setting for data at rest is set to Europe. This does not mean every processing or transmission step occurs only in Europe. | Google mail is not an LLM API. Google's Workspace processing terms govern this handling. |
Control
Retention, disconnect, and deletion
OrgMate keeps data only as long as needed to provide the service and meet related obligations. Retention may differ for legal, accounting, security, support, and provider-related reasons.
Disconnect
On disconnect, OrgMate removes the stored Salesforce access and refresh tokens from its database. This deactivates Salesforce access in OrgMate but does not delete previously stored metadata, Assessments, or other account data. OrgMate also attempts to revoke the Salesforce refresh token and, where possible, the access token.
Reconnect replacement
Reconnect establishes the replacement before attempting to revoke the old grant. A failed remote revoke does not discard a successfully established replacement.
Security contact
Report a security concern
To report a security concern confidentially, email security@orgmate.io. Tell us which OrgMate page or feature is affected and briefly describe what you observed. Please do not include passwords, OAuth codes, OAuth state values, Salesforce tokens, or customer record data.