SimpleOS Delivery Trust: security and data handling
Last updated 13 November 2026
This page says where SimpleOS Delivery runs and how your data is protected. It then says, just as plainly, what we do not claim. Every statement describes how the product is built and run on the date above. SimpleOS Delivery is built and operated by Simple Intelligence Group, Inc.
1. Where the product runs
The product runs on Microsoft Azure platform services in the East US 2 region, in the United States. We do not run our own data center. There is no option today to host your data in another country.
Your data is stored in Azure Database for PostgreSQL. Files you upload are stored in Azure Blob Storage. Each product in the SimpleOS family keeps its own data in its own store. Signing in through SimpleOS does not merge them.
2. Who can sign in
People sign in with a Microsoft Entra ID work or school account. Personal Microsoft accounts are not accepted. Because sign-in happens at Microsoft, your own Microsoft Entra policies apply to it, including multi-factor authentication and conditional access, and we never see the password. The sign-in page also offers Google sign-in, a sign-in link sent by email, and sign-in with an email address and a password. Where a password is used, we store only a salted hash of it.
Signing in proves who a person is. It does not by itself give access to a workspace. A person reaches a workspace only as a member of it.
3. How customers are kept separate
The product serves many customers from shared infrastructure. Each customer has a workspace, and every record carries the identifier of the workspace that owns it. The server takes that identifier from the signed-in session and applies it to every request. It is not taken from anything the browser sends, and it does not depend on a screen hiding rows.
Inside a workspace there are administrators, members and viewers. An administrator sees everything in the workspace. Anyone else sees only the records assigned to them. The server enforces that rule as well.
4. How data is protected
Data is encrypted in transit with TLS and encrypted at rest by the Azure platform.
Application secrets and keys are held in Azure Key Vault. They are not stored in source code.
Actions that change your data are written to an audit log in your workspace.
Access to production systems is limited to the people who need it to run and support the product. Our staff do not read the content of a workspace unless you ask us to, for example in a support request, or unless we must do so to investigate a security incident or comply with the law.
5. How AI is used
AI models are reached through Azure AI Foundry, which is a Microsoft Azure service. Prompts are not sent to a model supplier's own public service.
A feature sends content to a model only when it is used. Records written by an AI feature are marked as AI-generated and carry a confidence level and a reason. A person reviews them before they take effect outside the workspace.
Where an AI agent reads or changes workspace data, it does so through the product's own controlled interface. That interface applies the workspace identifier itself and records every call.
We do not use your data to train, retrain or fine-tune any AI model.
The AI Use Statement lists what each feature sends.
6. How changes are made
Changes are built on separate branches, pass automated tests, and are reviewed before release. Each release is approved and recorded.
7. Who else handles your data
We use the companies below to run the product. Each receives only what it needs for the task shown.
| Subprocessor | What it does for the Service | Customer Data it handles |
|---|---|---|
| Microsoft Corporation, Microsoft Azure | Hosts the application, its database and its file storage in the East US 2 region. Delivers pages through Azure Front Door. | All Customer Data held by the Service |
| Microsoft Corporation, Azure Key Vault | Holds application secrets and encryption keys | Secrets and keys. No workspace content. |
| Microsoft Corporation, Microsoft Entra ID | Signs users in | Name, work email address, and the identifiers of the user and the user's organization |
| Microsoft Corporation, Microsoft 365 (Exchange Online) | Delivers product email. Account mail is sent through Microsoft Graph from the product mailbox. Client status reports go from the project owner's own Microsoft 365 mailbox. | Recipient address and message content |
| Microsoft Corporation, Azure AI Foundry, with Claude models supplied by Anthropic | Runs the AI model for the features described in the AI use statement | Project content the user asks the product to work on: a statement of work to be turned into a plan, meeting notes to be turned into proposed tasks, project and task records for a risk review, a completeness check or proposed plan changes, the names of team members with their open tasks for a workload suggestion, the text of a file a member attaches for a summary, the counts from a finished import for a draft cancellation message, and a question typed into the help assistant. The model's response. |
| Stripe, Inc. | Takes payment for subscriptions bought directly from us | Billing contact name and email address. Stripe collects the payment method on its own pages. We do not receive or store card numbers. |
We tell workspace administrators by email at least 30 days before a new company starts to handle customer data. A service that your administrator chooses to connect is not on this list: it receives data because you connected it, under your own terms with its provider.
8. Keeping and deleting data
We keep your data while your workspace is active. For 30 days after your agreement with us ends, an administrator can still export it. After that we delete it from the systems that run the product, and we complete the deletion within 90 days after the agreement ends. Backup copies are not restored for use and expire on the backup schedule of the database service.
9. If something goes wrong
If we confirm a security incident that affects your data, we tell your workspace administrators by email without undue delay. We say what we know and what we are doing about it, and we add to that as we learn more.
To report a suspected vulnerability, write to security@simpleintelligencegroup.com. Include the steps to reproduce it and the page address. If you act in good faith, look only at your own data, and give us a reasonable time to fix the problem before you publish it, we will not take legal action against you for the research.
10. What we do not claim
We would rather tell you now than have you find out in a review.
We hold no SOC 2 report. We hold no ISO/IEC 27001 or ISO/IEC 42001 certificate. We make no claim of compliance with HIPAA, FedRAMP, PCI DSS or any similar standard. No independent auditor has examined the controls on this page.
Microsoft publishes compliance documents for Azure. Those describe Microsoft's services. They are not certifications of our product.
We do not commit to a level of availability, and we do not state a recovery time or a recovery point. We do not claim a standby copy of the product in a second region.
We do not claim a scheduled penetration test by an independent firm, and we do not run a paid bug bounty.
We do not give each customer its own database server. Customers share infrastructure and are separated as section 3 describes.
We do not offer hosting outside the United States.
If your review needs something on this list, write to support@simpleintelligencegroup.com and tell us. We will answer truthfully about where we stand.
11. Questions
Security questions and reports: security@simpleintelligencegroup.com
Privacy questions: privacy@simpleintelligencegroup.com
Everything else: support@simpleintelligencegroup.com
See also: Terms of Service, Privacy Policy, Data Processing Addendum, AI Use Statement, Support.