SimpleOS Reach Privacy Policy

Last updated 13 November 2026

This text is in effect as published. Our attorney is completing a review of it. If the review changes anything, we will post the new text here and email workspace administrators before the change takes effect.

This policy explains what information Simple Intelligence Group, Inc. ("SIG", "we", "us") handles when an organization uses SimpleOS Reach (the "Service"), what we do with it, and what choices people have.

In short: we collect what we need to run the Service. We do not sell personal information. We do not use customer data to train AI models. We do not show advertising in the Service.

1. Who is responsible for what

1.1 The Service is sold to organizations. The organization that opens a Workspace is the "Customer". The Customer decides what data goes into its Workspace and who can see it.

1.2 For the data in a Workspace ("Customer Data"), the Customer is the controller and we are its processor. We handle that data on the Customer's instructions under our Terms of Service and Data Processing Addendum. If you are a person whose details are in a Customer's Workspace, the Customer is the right place to send a request about them. If you write to us, we will pass your request to that Customer.

1.3 For a small set of data, we are the controller: the account details of the people who sign in, billing contact details, messages sent to our support line, and the operational logs of the Service. Sections 2.1, 2.4 and 2.5 describe that data.

2. Information we handle

2.1 Account information. When a person signs in with a Microsoft Entra ID work or school account, Microsoft sends us that person's name, work email address, and the identifiers of the person and of their organization. We store those, together with the person's role in the Workspace. We never receive the person's Microsoft password. If the sign-in page offers another sign-in method, we receive the equivalent details from that method, and where a password is used we store only a salted hash of it.

2.2 Customer Data. Subscriber records (email address, name, company, job title, country, phone number where supplied, custom attributes). Consent records with their time and source. Campaign content. Engagement events (delivered, opened, clicked, bounced, unsubscribed). Attribution records. Audit log entries. Media the workspace uploads. Access tokens for connected accounts.

2.3 Data from services a Customer connects. When an Administrator connects another service to the Workspace, the Service stores the access token for that connection and the specific data the connection is built to use. An Administrator can disconnect a service at any time, and the stored token is deleted when that happens.

2.4 Operational information. Server logs record the time of a request, the address it came from, the browser type, the page or function requested, and any error. An audit log records significant actions in a Workspace, such as a sign-in, a change of role, or a connection being added. We design these logs so that they do not hold passwords, access tokens or the body of a message.

2.5 Support and billing information. If you write to our support line, we keep your message and our replies. If your organization buys a subscription directly from us, our payment provider, Stripe, collects the payment method on its own pages. We receive the billing contact's name and email address, a customer reference, and the status of the subscription. We do not receive or store card numbers.

2.6 Cookies. The Service uses the cookies it needs to keep a person signed in and to remember which Workspace they are in. It does not use advertising cookies or cross-site advertising trackers.

3. How we use information

3.1 We use the information in section 2 for these purposes:

(a) to provide the Service to the Customer and to keep it secure;

(b) to sign people in and apply the roles the Customer has set;

(c) to send messages about the Workspace, such as invitations, security notices and billing notices;

(d) to answer support requests;

(e) to find and fix faults, and to detect and stop misuse;

(f) to meet our legal obligations and to establish or defend legal claims.

3.2 We do not sell personal information, and we do not share it with anyone for advertising.

3.3 We do not use Customer Data to train, retrain or fine-tune any AI model.

3.4 Our staff do not read the content of a Workspace except where the Customer asks us to, for example in a support request, or where we must do so to investigate a security incident or to comply with the law.

4. AI features

4.1 The Service includes features that send content to an AI model and return a draft. A feature sends content only when it is used.

4.2 What is sent: Content the workspace asks the product to work on. Campaign copy, subject lines, briefs and audience descriptions, for drafts, versions for each channel, suggested segments and a proposed send time. The text of a file attached to a campaign, for a summary of that file. The public web pages and posts of a competitor the workspace names, for a competitive summary and a draft reply post. Where a workspace uses engagement matching, a subscriber's email address, company, job title, country and company attributes, for a match and a one-sentence reason. Where a workspace uses the advertising sales features, the details of a media property and of a request for proposals, for a fit score and a pitch draft. An industry name typed during setup, for a starter pack. The questions a workspace sets for its search visibility checks. A question typed into the help assistant. Subscriber email addresses are not part of a drafting prompt.

4.3 Where it goes: SimpleOS Reach reaches AI models through Azure AI Foundry, a Microsoft Azure service. The models are Claude models supplied by Anthropic and served by Microsoft. The model runs as a Microsoft Azure service. Prompts are not sent to a model supplier's own public service.

4.4 Records written by an AI feature are marked as AI-generated in the Service and carry a confidence level and a reason. A person reviews them before they take effect outside the Workspace.

4.5 The AI Use Statement gives the full description.

5. Who we share information with

5.1 Subprocessors. We use the companies below to run the Service. Each one receives only what it needs for the task shown.

CompanyWhat it does for the ServiceCustomer Data it handles
Microsoft Corporation, Microsoft AzureHosts 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 VaultHolds application secrets and encryption keysSecrets and keys. No workspace content.
Microsoft Corporation, Microsoft Entra IDSigns users inName, work email address, and the identifiers of the user and the user's organization
Microsoft Corporation, Azure Communication Services and Microsoft 365 (Exchange Online)Delivers account email through Azure Communication Services Email. Delivers campaign email through Azure Communication Services, or through the sender's own Microsoft 365 mailbox where a campaign is sent that way. Delivers text messages through Azure Communication Services where enabled.Recipient address, message content, and for text messages the phone number
Microsoft Corporation, Azure AI Foundry, with Claude models supplied by AnthropicRuns the AI model for the features described in the AI Use StatementThe prompt content listed in the AI Use Statement, and the model's response
Microsoft Corporation, LinkedIn (only for accounts a workspace member connects)Publishes posts and returns results for connected accountsPost content and the connected account's identity
Stripe, Inc.Takes payment for subscriptions bought directly from usBilling contact name and email address. Stripe collects the payment method on its own pages. We do not receive or store card numbers.
Twilio Inc., SendGridDelivers email where the workspace or the host is configured to use itRecipient address and message content

5.2 We tell Administrators by email at least 30 days before a new subprocessor starts to handle Customer Data.

5.3 Services a Customer connects. When an Administrator connects another service, data moves between the Service and that service as the connection describes. The provider of that service handles the data under its own terms with the Customer. It is not our subprocessor.

5.4 Legal requests. We disclose information to a court or a government body only where the law requires it. Where the law allows, we tell the affected Customer first.

5.5 Change of ownership. If our business or the Service is sold or merged, the information we hold passes to the new owner, who must continue to honor this policy for it.

5.6 Affiliates and contractors. People who work for our affiliates or as our contractors may help us run and support the Service. They act on our instructions and are bound to keep information confidential.

6. Where information is kept

6.1 The Service is hosted on Microsoft Azure in the East US 2 region, in the United States. There is no option today to keep data in another country.

6.2 If you use the Service from outside the United States, your information is transferred to the United States and processed there. Where data protection law requires a contract for that transfer, the Data Processing Addendum explains how a Customer puts one in place with us.

7. How long we keep information

7.1 We keep Customer Data for as long as the Customer's Workspace is active.

7.2 For 30 days after the Customer's agreement with us ends, an Administrator can still export Customer Data. After that we delete it from the systems that run the Service, and we complete the deletion within 90 days after the agreement ends. Copies in backups are not restored for use and expire on the backup schedule of the database service.

7.3 An access token for a connected service is deleted when an Administrator disconnects that service or when the Workspace is deleted.

7.4 We keep billing and tax records, and other records the law requires, for as long as the law requires. Where the Service must keep a specific record as evidence after other data is deleted, the Data Processing Addendum names it.

7.5 We keep support messages for as long as we need them to answer the request and to deal with any follow-up.

8. Security

8.1 Data is encrypted in transit and at rest. Each Workspace is kept separate by an identifier that the server applies to every request. Application secrets are held in Azure Key Vault. Access to production systems is limited to the people who need it to run and support the Service.

8.2 The Trust page describes these measures in more detail. It also states plainly what we do not claim, including that we hold no security certification today.

8.3 No service can promise that it will never be breached. If we confirm a security incident that affects a Customer's data, we tell that Customer's Administrators without undue delay and give them the information they need to meet their own obligations.

8.4 To report a suspected vulnerability, write to security@simpleintelligencegroup.com.

9. Your choices and rights

9.1 If you use the Service through your employer or another organization, that organization controls your account and the data in its Workspace. Ask its Administrator first if you want to see, correct, export or delete information about you. We help Customers respond to those requests.

9.2 Depending on where you live, the law may give you rights over personal information that we hold as a controller, including rights to see it, to have it corrected or deleted, to object to how it is used, and to receive a copy. To use one of those rights, write to privacy@simpleintelligencegroup.com. We answer within the time the law sets. We may need to confirm who you are before we act.

9.3 We do not sell personal information and we do not share it for cross-context behavioral advertising, as California law uses those terms. We do not treat anyone differently for using a privacy right.

9.4 If you are not satisfied with our answer, you may complain to the data protection or consumer protection authority where you live.

10. Children

The Service is a business product. It is not directed at anyone under 16, and we do not knowingly collect personal information from children. If you believe a child has given us personal information, write to privacy@simpleintelligencegroup.com and we will delete it.

11. Changes to this policy

We may change this policy. The current version and its date are always at the top of this page. If a change is material, we tell Administrators by email at least 30 days before it takes effect.

12. Contact

Simple Intelligence Group, Inc.

Privacy questions and requests: privacy@simpleintelligencegroup.com

Security reports: security@simpleintelligencegroup.com

Product support: support@simpleintelligencegroup.com

See also: Terms of Service, Data Processing Addendum, AI Use Statement, Trust, Support.

13. Mobile numbers and SMS consent

Where SMS is enabled we hold the mobile number, the record of how and when consent was given, and delivery and opt-out events for messages sent to it. We use that data only to send the messages you asked for and to prove we were entitled to send them. We do not sell mobile numbers, and we do not share mobile numbers or SMS consent with third parties or affiliates for their own marketing purposes. The only parties that receive them are the carriers and messaging providers needed to deliver the message.

14. LinkedIn data flow

When a workspace member connects a LinkedIn account, we receive an OAuth access token plus the connected identity (name, email, profile URL, and any Company Pages the user administers) from LinkedIn. We store that token per tenant and use it only to publish posts and retrieve engagement analytics on identities the user explicitly connected. We never post without an authenticated action from your workspace, and we never sell, share, or resell data retrieved from the LinkedIn APIs. Revoking the connection from within SimpleOS Reach immediately invalidates our stored token and stops all further LinkedIn API activity on that connection.

15. YouTube API Services

Our internal publishing tool uses YouTube API Services to upload our own training and demonstration videos to our own YouTube channel. By interacting with that YouTube content you are also subject to the YouTube Terms of Service and the Google Privacy Policy. Our tool accesses only our own channel through Google OAuth; it does not access, collect, or store any other user's Google data. The Google account authorization our tool holds can be revoked at any time at Google security settings. Stored authorization tokens are kept in our private configuration, encrypted at rest, and are deleted when no longer needed.