Security

How We ProtectYour Data

This page describes the security controls RoryPlans uses today. For what we collect, where it is stored and how long we keep it, see our Privacy Policy.

At a Glance

Controls in place today

TLS encryption for all connections
AES-256-GCM for stored integration credentials
Sign-in with Google, Microsoft, GitHub or Slack
Access checked against team roles and plan sharing
Least-privilege Microsoft 365 access (Sites.Selected)

Security Controls

The controls below are built into the RoryPlans application and the infrastructure it runs on.

Encryption in Transit and at Rest

Connections to RoryPlans and between RoryPlans, its database and its service providers use TLS (HTTPS). Our database (Neon) and file storage (Google Cloud Storage) encrypt stored data at rest. Our key-value store (Upstash), which holds plans and agent run records, is not encrypted at rest; data in it is protected in transit and by access controls.

Protected Credentials

WinTeam API keys and organization email (SMTP) passwords are encrypted with AES-256-GCM before they are stored. RoryPlans API tokens and OAuth client secrets are stored only as hashes. Other connected service tokens rely on the storage encryption above.

Sign-In and Access Control

You sign in with your Google, Microsoft, GitHub or Slack account, so multi-factor authentication follows that provider’s settings; RoryPlans has no separate MFA step. Every request is checked against the user’s account, team role and plan sharing settings.

Least-Privilege Integrations

Microsoft 365 access uses Sites.Selected, so RoryPlans can reach only the SharePoint sites an administrator grants. Sign-in and connection flows use signed, single-use state, and sensitive operations are rate limited.

Activity Records

Each agent run keeps a record of its status, results and where they were delivered, and agents can be set to wait for your approval before they send results. Changes to plans are recorded in an internal audit log with who made the change and when.

Data Location and Deletion

The application runs in Vercel's US East region and our main database in US East (N. Virginia). You can delete plans, chats, files, agents or your whole account; the Privacy Policy explains what each removes. Database backups are kept for 30 days.

Infrastructure Providers

RoryPlans runs on these providers. The certifications shown are held by each provider, not by RoryPlans. Our full list of service providers is in the Privacy Policy.

Vercel

Hosts the RoryPlans application in its US East region (Washington, D.C.) and provides the AI Gateway, Vercel Connect, code sandboxes for agents and web analytics.

SOC 2 Type 2
ISO 27001
PCI DSS
GDPR
EU-U.S. Data Privacy Framework

Neon

Hosts our main database on Amazon Web Services in US East (N. Virginia), encrypted at rest.

SOC 2 Type 2
ISO 27001
ISO 27701

Google Cloud Platform

Stores uploaded files in a private Cloud Storage bucket, shared only through links that expire, and runs AI models (Vertex AI and Gemini API).

SOC 2
ISO 27001
PCI DSS
HIPAA

Upstash

Key-value storage for plans, agent runs and short-lived security records, in AWS US East (us-east-1).

GDPR

Microsoft Azure

Runs Azure OpenAI models and the Azure Bot Service that connects the RoryPlans app to Microsoft Teams.

SOC 2
ISO 27001
FedRAMP

Security Practices

How we protect data, control access, run our infrastructure and respond to incidents.

Data Protection

TLS (HTTPS) for connections to RoryPlans and to our database and service providers
Encryption at rest for our database (Neon) and file storage (Google Cloud Storage)
AES-256-GCM encryption for WinTeam API keys and organization SMTP passwords
RoryPlans API tokens and OAuth client secrets stored only as hashes
Files kept in a private bucket and shared only through links that expire

Access Control

Sign-in with Google, Microsoft, GitHub or Slack accounts
Multi-factor authentication through your sign-in provider’s settings
Team roles and plan sharing settings checked on every request
Microsoft 365 limited to the SharePoint sites an administrator grants (Sites.Selected)
Signed, single-use state on sign-in and connection flows

Infrastructure Security

Production keys and credentials kept in our hosting provider’s environment configuration, with access limited to authorized personnel
Rate limits on sensitive operations
Agent code runs in separate Vercel Sandbox environments
Application logs and errors monitored through our hosting and observability providers

Incident Response

Vulnerability reports accepted at support@roryplans.ai
Affected customers notified of a security incident without undue delay and no later than 72 hours after confirming it, in addition to any notice the law requires
RoryPlans is working towards SOC 2; our infrastructure providers already hold the certifications listed above

Questions AboutOur Security?

Email us with security questions, documentation requests or vulnerability reports.

Security Support

Security Inquiries

General security questions and documentation requests

Vulnerability Reports

Responsible disclosure of security vulnerabilities

Security Reviews

Security questionnaires and vendor reviews