When you connect Google or Microsoft, we request a send only permission and nothing else. Shaku AI cannot read, browse, search, open, or delete a single message in your mailbox, and we do not request any scope that would allow it. The one thing we can do is send the outreach messages you have written and approved, from your own address, so replies return to you and the message appears in your Sent folder.

For Google this is the gmail.send scope; for Microsoft it is Mail.Send. We additionally read only the address of the account you are connecting, so the app can show you which mailbox is linked.

When a prospect replies, that reply goes to your inbox, not ours. Shaku AI records the fact that a reply happened, who it was from and when, so the product can stop a sequence and show you the activity. We never store the contents of a reply. The substance of the conversation stays between you and the person you are talking to.

• In transit. Every request to Shaku AI runs over TLS. Plain HTTP is not served.
• At rest. All data is encrypted at rest by our managed database provider.
• Tokens. The OAuth access and refresh tokens that let scheduled sequences keep sending are held in an access controlled store. They are never exposed to the browser and never written to client side storage.

Shaku AI is multi tenant, and separation between customers is enforced in the data layer, not left to the application to remember. Every record is scoped to your workspace, and every query is filtered by tenant, so one customer’s account can never reach another customer’s leads, campaigns, drafts or connected accounts.

We ask for the narrowest set of permissions that makes a feature work, and no more. That is why the mail scope is send only, why the LinkedIn connection reads only your basic profile and cannot post or read messages, and why we do not request calendar, contacts or file access we have no use for. You can review exactly what each integration granted, and revoke any of them in one click from the integrations page, which invalidates the stored tokens immediately.

• Administrative access to production is restricted to the personnel who need it to operate the service.
• We do not use the data in your connected mail accounts to train machine learning models.
• A small number of vetted subprocessors (cloud hosting and managed database, authentication, model providers, contact data verification, and transactional email for system notices) each handle data only on our instructions and under contract. We never sell personal information or share it with advertisers or data brokers.

• Export. Download everything in your workspace at any time from Settings, as a machine readable JSON file. No request and no waiting period.
• Delete. Delete your workspace in one click. Sending stops at once, scheduled steps stop, and sourcing stops. The data is permanently erased seven days later, a short window that exists only so an accidental deletion can be undone. After that it cannot be reversed.
• Revoke. Disconnect any integration whenever you like, which removes our access to it immediately.

Shaku AI is built to the practices a SOC 2 program expects, and we are working toward formal attestation. We are not certified yet, and we will say so plainly here until we are, rather than imply a status we have not earned. If your procurement process needs specific documents or answers in the meantime, write to us and we will help.

If you believe you have found a security issue, please tell us at connect@shakuai.io before disclosing it publicly. We will acknowledge your report, keep you updated while we investigate, and we will not pursue action against good faith research that respects our customers’ data and the law.

Questions about security or a specific requirement from your security team can be sent to connect@shakuai.io.