Privacy notice

Publication pending: the formal legal entity, retention schedule and final policy review must be confirmed before public release. These pages describe the current local alpha preview.

Data used in this preview

Microsoft sign-in provides an account identity and profile. The application stores organization membership, connection and mailbox identifiers, consent state, encrypted Microsoft credentials, and saved sample-flow descriptions and versioned rules. Session cookies support sign-in; temporary unsaved draft handoff is held in server memory.

Email access and its limits

Microsoft Mail.Read allows broader mailbox reading than the metadata preview uses. Optional Mail.ReadWrite and Mail.Send permissions are requested separately for the actions you choose. On your request, the local preview lists up to 10 recent Inbox messages and reads selected metadata such as subject, sender, receipt time and importance. The metadata preview does not request message bodies or attachments or save a synchronized Inbox record. Reviewing or automatically executing an approved mail-changing action reads the message text and its change identifier in memory to verify the action. It stays in memory, is not sent to AI, and is not stored as mail content in the application database. Forwarding messages with attachments is unavailable. Approved replies, draft creation, forwarding and folder moves are performed through Microsoft Graph. Active flows store new-mail metadata, decisions and action outcomes for the log. Automatic actions need approval for the saved version and mailbox at activation.

Microsoft and AI

Microsoft receives sign-in, consent and Microsoft Graph requests. The public demo uses fictional data and rule-based simulation. OpenAI receives the setup goal, questions and current flow configuration when you use the AI assistant. An optional subject-analysis step sends the subject and your saved criterion or AI reply instructions to OpenAI after explicit consent, automatically for new arrivals in an active flow; no sender details, email body or attachments are sent by that feature. A future AI feature requires a separate description of its data use before it is enabled.

Storage and access

This alpha uses a retained database on its dedicated development host behind a Cloudflare HTTPS tunnel. It is not yet a Cloudflare Worker/D1 production deployment. Microsoft credentials are encrypted at rest; signed-in sessions use HttpOnly, SameSite cookies. Organization and connection-owner checks control access. Saved sample drafts remain after server restart. A production retention schedule, hosting locations and deletion process have not yet been finalized.

Your choices

Microsoft permission approval is separate from flow activation. You can review or revoke this application’s Microsoft permissions using Microsoft’s account controls. Revoking a permission does not itself delete previously stored organization records or drafts. Application record deletion and connection-disconnection controls are currently unavailable. The action audit records an approval identifier, organization, owner, flow version, a fingerprint and result status, without storing the selected message body. Final retention and request handling remain to be confirmed.

Privacy questions and release requirements

For privacy questions, contact hello@365with.ai. The formal legal entity, applicable processing arrangements and request-handling process must be confirmed before public release. No unverified retention period, legal basis or compliance guarantee is claimed here.