Your business knowledge deserves serious protection.
Clear access controls. Reviewable knowledge. An honest account of how your information is handled.
Security at a glance
Defined access. Human authority.
- Organization-scoped access
- Server-side credentials
- Review before approval
- Revocable connections
- Source-backed knowledge
- Source
- Opryn processing
- Human review
- Approved knowledge
- Authorized lookup
Your organization, your access rules
Opryn checks signed-in membership and scopes company requests to the active organization. Owner and administrator permissions are required for sensitive management actions. Knowledge retrieval applies the requesting person’s or AI connection’s permitted access.
Reviewed knowledge, not invented policy
Approved knowledge is distinct from Observed findings awaiting review. Opryn’s shared answer pipeline checks approval and blocking conflicts before using retrieved guidance. Source references help people inspect the basis of an answer where available.
AI can still make mistakes. Review important decisions and do not treat Opryn as a substitute for professional advice or required human authorization.
Connections have a defined purpose
Manual Drive imports read links or copies you provide. Where authorized Drive connections are enabled, Opryn can browse files covered by your Google consent, but imports only the files you choose. Connecting does not automatically import or approve your Drive content. ChatGPT and Claude can send context you explicitly ask them to share and retrieve permitted Opryn knowledge. Connecting them does not give Opryn unrestricted chat history.
Slack and Teams require their supported setup and authorized user interactions. Custom bots and agents remain external systems; Opryn provides approved knowledge and evaluates its responses under connection permissions. It does not build agents or fine-tune model weights.
Credentials and service providers
Server-side integration code handles OAuth tokens and provider credentials. External AI access uses authorized grants or connection keys; those can be revoked in Opryn. Customer-created API keys must also be kept secure by the system using them.
Hosting, authentication, storage, payment, email, and AI processing depend on service providers. Company content may be sent to the configured model provider to transcribe, organize, search, or answer questions. See the Privacy Policy for details.
Calls and media
Businesses choose the recordings they upload or authorize through configured call learning. Recordings, transcripts, selected video frames, and derived findings may be processed. Businesses are responsible for recording notices, permissions, and consent.
Twilio call-audio settings support removal after processing or a retention period of 7, 30, or 90 days. Cleanup depends on successful processing and maintenance runs; transcripts and derived knowledge are separate. This is not a universal deletion schedule for all uploads, nor does it delete the provider’s original recording.
Service providers
Opryn uses infrastructure providers for specific parts of the service. The Privacy Policy describes the information involved.
- Vercel
- Application hosting
- Supabase
- Authentication, database and storage
- OpenAI
- Configured AI processing
- Stripe
- Subscriptions and payments
- Resend
- Configured invitation email delivery
- Nango
- Managed integration authorization where used
Disconnecting and removing information
Disconnecting a service stops the associated access; it does not automatically erase knowledge already imported or copies already received by another system. Authorized users can remove supported items through the app. Full account, organization, or stored-media deletion requires a data removal request; we do not promise instant deletion from every backup or third-party system.
Questions before connecting?
Contact Opryn about your access, security, or data handling needs. No certification or independent security audit is claimed on this page.
