Security and data

RippleSync is built so that, on most routes, your documents never reach it. Where they do, through the Microsoft 365 connection, they pass through in memory and are never stored. This page is written for the IT, security and privacy teams who review tools before people use them.

Where your data goes, by way of using it

Way of using it	What reaches RippleSync	Who processes your content	Stored by RippleSync
Copy the prompt into your assistant	Nothing	Your approved AI assistant	Nothing
"Run it" and "Test your assistant" on this site	Nothing: files and answers stay in your browser	No one else	Nothing
Microsoft 365 Copilot agent	Nothing: it runs inside your Microsoft 365 tenant	Microsoft	Nothing
RippleSync automation	Text of the day's project meetings, email, chats and documents, passed through the connection in memory	Your Copilot Studio agent and flows, in your tenant	Nothing. Decisions and findings are kept in SharePoint lists in your own tenant
Microsoft 365 connection	The text of documents, emails or transcripts your assistant asks for, passed through in memory	RippleSync's server (Vercel, United States), then your AI assistant	Nothing
Feedback form	What you type, and your email if you give it	Formspree	Kept by Formspree so we can read and answer it

Microsoft 365 permissions

All permissions are delegated: RippleSync acts as the signed-in person and can only see what that person can already see. None of them allows writing, sending or deleting.

Connection	Microsoft Graph permissions	Admin consent
/mcp (files)	User.Read, Files.Read.All, Sites.Read.All, offline_access	Only if your tenant blocks user consent
/mcp/mail	The above, plus Mail.Read	Only if your tenant blocks user consent
/mcp/meetings	The above, plus Calendars.Read, OnlineMeetings.Read, OnlineMeetingTranscript.Read.All, Chat.Read, ChannelMessage.Read.All	Always, for transcripts and channel messages

Controls

• No storage. There is no database or file storage, and nothing is cached between requests. The server doesn't log document text, email or transcripts.
• Encryption. All traffic uses HTTPS. Your Microsoft sign-in is wrapped in an AES-256-GCM encrypted token held by your assistant; RippleSync keeps no copy.
• Sign-in. Sign-in uses Microsoft Entra ID, so your company's sign-in rules apply, including multi-factor authentication and conditional access. RippleSync's own sign-in step follows OAuth 2.1 with PKCE, and only accepts approved return addresses.
• Sign-in lifetime. Access lasts about an hour, and a sign-in lasts at most 30 days without use. To cut access sooner, remove RippleSync in the Microsoft Entra admin center, or at myapps.microsoft.com. RippleSync then loses access within about an hour.
• Read-only by design. No tool can edit, send, delete or share. Owners apply every change themselves.
• Prompt injection. Document text is treated as material to check, never as instructions. A document that tries to instruct the AI is reported in the coverage note. This is tested with a planted hidden instruction.
• Verified quotes. The record_findings tool re-reads each source and flags any quote that isn't in the document.
• Website. No cookies and no third-party scripts or fonts. Visits are counted with Vercel Web Analytics, which is cookieless, served from this site and doesn't identify visitors. A strict content security policy is in place, and the site can't be framed by other sites.

Who else processes data

Company	What for	Where	What they receive
Vercel	Hosting the website and the Microsoft 365 connection, and counting visits without cookies	United States (Washington, D.C.)	Request details (IP address, time, address requested, status), kept briefly in Vercel's logs; connection content in memory only
Formspree	The feedback form	United States	What you type in the form
Microsoft	Sign-in, and reading Microsoft 365 content	Your tenant's region	Covered by your company's agreement with Microsoft
Your AI assistant's provider	Running the check	Under your company's agreement with that provider	The prompt, the documents and the findings

RippleSync doesn't use your content to train AI models. Whether your assistant's provider does depends on your agreement with them.

Known limits

• No certifications. RippleSync has no SOC 2 or ISO 27001 certification, and no independent penetration test yet.
• Data location. The Microsoft 365 connection runs in the United States. If content must stay in your region, use the Copilot agent or the paste route.
• No individual revocation. Individual sign-ins can't be cancelled from RippleSync's side. Revoke the app in Microsoft instead, as described under Controls.
• No rate limiting. RippleSync doesn't limit requests itself. Microsoft's own limits on reading Microsoft 365 still apply.
• AI accuracy. Results are AI drafts. Accuracy is measured on a sample project, not on your documents. Check each finding against its quote before you use it.

Answers for security reviews

Is RippleSync a data processor for our content? Only on the Microsoft 365 connection route, and only in memory while a request runs. On the other routes, your content never reaches RippleSync.

Can we limit it to our tenant or turn it off? Yes. Admins can require admin consent, assign RippleSync to specific users, or block it, in the Microsoft Entra admin center under Enterprise applications.

Does it need a data processing agreement? Ask through the feedback form, choosing Privacy request. For most teams, the Copilot agent or the paste route avoids the need, because RippleSync never receives content.

How do we report a vulnerability? Use the feedback form and choose Security report. Don't include company documents. See security.txt.

What changes when RippleSync changes? Changes to data handling are listed on the privacy page with a date.