Built for calendars
that matter.
AI agents have real write access to real calendars. We treat that access accordingly. Here is how Openavail protects your data and your organization's schedule.
No persistent calendar data
Openavail does not store your calendar events. Availability checks are streamed from the provider at arbitration time and discarded. Only arbitration outcomes (the audit log) are persisted.
Refresh tokens encrypted at rest
Google OAuth refresh tokens are encrypted with AES-256-GCM before storage. The encryption key is rotated quarterly. Governance plan customers can bring their own key (BYOK).
Short-lived session cookies
Dashboard sessions use HttpOnly, SameSite=Lax cookies with a 24-hour TTL. No JWTs stored in localStorage. Sign-out immediately invalidates the server-side session.
Agent API key hashing
API key material is shown exactly once at mint time. We store only an Argon2id-derived hash. Key compromise is limited to the specific agent and permission scope it was issued for.
Least-privilege access for every agent.
Each agent is registered with an explicit permission scope. API keys are issued per agent and can be revoked individually without touching other agents or sessions. Every key usage is recorded in the audit log with the key's reference ID.
Where we are and where we're going.
Audit period begins Q3 2026. Report expected Q1 2027.
Scoped alongside SOC 2. Targeting certification in 2027.
Data processing agreement available on request for Team and Governance plans.
Bring your own key for refresh-token and audit-log encryption.
If you discover a security vulnerability in Openavail, please email [email protected]. We will acknowledge within 48 hours and aim to resolve critical issues within 14 days. We request that you do not disclose publicly until we have had the opportunity to remediate.