Security

Brokers are already experimenting with AI on their own, pasting client emails into chatbots or building their own tools. Prismia gives them one standardized system your team can review instead.

• One approved tool instead of many unvetted ones. Scattered personal AI tools and scripts are replaced by a single vendor you can review.
• Scoped, revocable access. Prismia connects through standard Google and Microsoft sign-in with the specific permissions listed below. Access can be revoked at any time from your admin console.
• Your data stays out of public AI services. Email processing runs in an isolated environment, described below.

Think of a records clerk who reads a broker’s work mail, files the useful details in the right folder and ignores the junk. Mailbox access is read-only: Prismia cannot delete, move or edit messages.

1. A broker signs in with their Google or Microsoft work account and approves Prismia’s access.
2. When a new email arrives, Prismia reads it and decides whether it is work related. Spam, newsletters and personal mail are skipped.
3. From work emails, Prismia pulls out the details that matter: new or updated contact info, properties, deal terms and follow-ups.
4. Prismia adds those details to the broker’s database and keeps existing records up to date, and every entry is traceable to the email it came from.

The database and most features work without email access. Brokers or firms that prefer not to connect email can still use Prismia, but they give up the automatic updates that save the most time.

Automatic updates need two things: permission to read email and standard sign-in. Everything else is optional and can be left off. Every permission is read-only.

Required

• Reading emails and most small attachments. Google: gmail.readonly. Microsoft: Mail.Read.
• Standard sign-in. Google: openid, email, profile. Microsoft: offline_access, openid, email, profile, User.Read.

Optional, but recommended

• Syncing calendar events and contacts. Google: calendar.readonly, contacts.readonly. Microsoft: Calendars.Read, Contacts.Read.
• Reading large attachments stored in Google Drive or OneDrive. Google: drive.readonly. Microsoft: Files.Read.

Brokers can request approval individually, but IT admins usually approve Prismia once for everyone in the organization. Approve the required permissions to start; you can add the optional ones now or later. Each approval adds to what is already approved and never removes anything.

Microsoft 365 (Entra ID)

1. A Global Administrator or Privileged Role Administrator opens the admin consent link for each permission set being approved. Email hello@prismia.com for the links.
2. Sign in with the admin account, review the permissions Microsoft lists and select Accept. You land on Prismia’s sign-in page when it is done.

App name: Prismia (verified publisher: Prismia Enterprises). Application (client) ID: d87c1c9b-9184-415b-ab01-4a38db371dec. To review or revoke: Entra admin center, Enterprise applications, Prismia, then Permissions, or Properties and Delete.

Google Workspace

1. A super administrator opens Admin console, Security, API controls, Configured apps.
2. Select Configure new app and search for the client ID below.
3. Choose which organizational units it applies to.
4. Under access, choose Specific Google data and tick Gmail for the required permissions, plus Calendar, Contacts or Drive for the optional ones.
5. Save.

App name: Prismia. OAuth client ID: 140048196452-bvvt8ol55nvajf0q78vj3prlfo59ph36.apps.googleusercontent.com. To review or revoke: the same page, Prismia, then change access, or set it to Blocked.

Limiting what Prismia asks for

Tell us which permissions you approved. We restrict your workspace to match, and Prismia will never ask your brokers for a permission outside that list. If you approve more later, tell us and we will turn it on.

Removing Prismia

IT can revoke access at any time from the admin pages above, and Prismia stops reading immediately. Individual brokers can remove Prismia from their own account at myapplications.microsoft.com (Microsoft) or myaccount.google.com/permissions (Google).

Your emails never leave Prismia’s own AWS environment. AI processing runs on Amazon Bedrock, AWS’s managed AI service, which does not store or train on your data. Email is never sent to public AI services such as ChatGPT or the OpenAI and Anthropic APIs.

Every AI model call runs on Amazon Bedrock in Prismia’s own AWS account in US West. The inference path runs from a private network with no internet access to Bedrock through an AWS PrivateLink endpoint. Bedrock’s data retention mode for our account is set to none, so AWS stores no prompts or outputs and third-party model providers never receive them.

• Model makers cannot see your data. Bedrock runs models in AWS-owned accounts that providers like Anthropic cannot access, so they never see prompts, outputs or logs.
• The AI service keeps nothing. With retention set to none, Bedrock writes nothing to storage and blocks any model that would require retention.
• No internet path for AI processing. The step that runs the models has no route to the public internet. Prismia still uses the internet to connect to Google or Microsoft and receive your mail.
• No model training. Customer data is never used to train or fine-tune any AI model.

• Per-user access only. Prismia can read only the mailbox of the broker who connected it, never other mailboxes in your tenant.
• No passwords stored. Brokers sign in through Google or Microsoft, so Prismia never sees their passwords and your MFA and sign-in policies apply.
• Admin approval supported. IT can require approval before any broker connects Prismia, using Google Workspace or Microsoft Entra admin consent.
• Verified app.Prismia completes Google’s OAuth verification, including the security assessment required for Gmail and Drive access, and Microsoft publisher verification.

• Encryption in transit and at rest. Customer data is encrypted in transit using TLS and at rest using encryption provided by AWS and our database infrastructure.
• Isolated per customer.Each team’s data is kept separate from every other customer’s.
• Work email only. Emails classified as spam or personal are discarded, not stored.
• Clean logs. Application logs hold record IDs and errors only, never message content. Audit logs record who accessed what and when, and are kept for 12 months.

• Deletion on exit. When a firm leaves, it gets a 14-day export window, and its data is deleted within 30 days of termination.
• Nothing left behind. Extracted deal details, summaries and drafts are deleted along with the email they came from. Backups age out within 10 days.
• Departing brokers.When a broker leaves, their firm data is returned to the firm or deleted within 10 business days of the firm’s instruction. It is never released to the broker.

• Retention locked off.Bedrock’s retention mode is set to none and enforced by an AWS policy that blocks any other setting.
• Pinned region. AI processing stays in US West, with cross-region inference turned off.
• Approved models only. Prismia uses a fixed list of models and excludes any that require the provider to retain data.

• Paperwork on request. A data processing agreement (DPA) and our current subprocessor list.
• Subprocessors. AWS, Supabase, Railway and Vercel.
• Breach notice. Affected customers are notified within 72 hours of a confirmed breach.
• Independent testing. A third-party penetration test by December 2026, SOC 2 Type I by February 2027 and SOC 2 Type II by mid 2027.

Ask us for supporting documents on any item on this page. How we handle personal information is described in our Privacy Policy.

If you believe you have found a vulnerability, or have a question about how Prismia handles your data, email hello@prismia.com.