Data and privacy
Orloi turns new activity from the Airtable data you select into a history you can review.
What Orloi reads and writes
Orloi reads the Airtable base, tables, and fields in your saved scope after activation. It does not read unrelated Airtable data, import activity from before activation, or write changes back to Airtable.
Orloi writes the captured history and the reports, metrics, and findings built from it to the Postgres database you connect. It does not modify your existing application data in that database.
Where durable history lives
Your Postgres database remains the durable record of Orloi output. The Orloi dashboard reads the stored history there so you can review activity and derived results later; pausing or reconnecting capture does not erase what is already stored.
For storage categories and implementation detail, see Architecture and stored data in Advanced.
Optional AI features
The core changelog, Activity, and metrics calculated without AI remain available without AI-backed features. Reports and suggestions are optional settings, not a requirement for capture or review. Reports are off until enabled; if you skip report setup, captured activity is not sent to an AI provider.
When you enable an AI feature, Orloi sends the context needed for that feature to the provider configured for it. That context can include readable activity history, metrics, report instructions, and other feature context. Review the provider's terms and data-handling settings before enabling AI for sensitive work, and never put secrets in prompts or custom instructions.
Why scope matters
Scope is the boundary for future capture. Include only the tables and fields that should become operational history, especially when a base contains customer, health, workforce, or other sensitive information. A later scope reduction stops matching future activity but does not remove history already stored; use Pause, reconnect, or remove a base for normal lifecycle changes and the Advanced storage reference for customer-controlled cleanup decisions.
Contractual security and privacy
This is a practical product guide, not a legal privacy policy or data-processing agreement. Contractual commitments, subprocessors, retention, residency, deletion requests, and formal security information live in the Orloi privacy policy and Orloi Trust Center. Use those documents and your agreement with Orloi for contractual decisions.
Orloi is for operational visibility, change history, audit trails, investigation, and process understanding. It is not designed or authorized for employee scoring, workforce surveillance, disciplinary decisions, or automated HR decisions.
For database roles, direct queries, provider networking, retention procedures, and BI or agent isolation, use the clearly labelled Advanced technical reference and AI agent database access pages.