Security and data ownership
Your data. Your rules.
AI data security comes down to three questions: where your data lives, who can reach it, and what an agent may do with it. Here are Ocally's answers, in plain words.
Data ownership
Your data stays yours.
You keep ownership of the content you upload, create or share through Ocally. That is written into our Terms, not only on this page.
Originals kept
Uploaded files keep their original bytes and their source. Every fact Ocally holds shows where it came from.
History is never rewritten
Corrections add a new version. The old one stays on record, so you can always see what changed.
Disconnect any time
Revoke any connection and all future access stops. The record of past work stays intact.
Tenant isolation
A private platform for every client.
Your business never shares a database with anyone else's. Every client runs on its own isolated platform.
- Its own database, workspace, Knowledge Store and Cred Store.
- A request from one client cannot read, infer or change another client's records.
- Files stored under a path of their own. Database credentials held in a secrets manager.
- Inside your company, a store's data and accounts stay with that store's people.
Every other client: a separate platform. No path between.
Credentials and connections
Access, not keys.
Agents act through narrow, temporary, logged permissions. They never see a password.
- 01
Never in a prompt
Passwords and tokens never appear in AI prompts, task files, logs or answers.
- 02
Just enough, just in time
Each action gets only the access it needs, for that task, for a short time.
- 03
Revoke any time
Revoke a connection and all future access stops at once. The record of past work stays.
- 04
Health, not secrets
Ocally staff can see whether a connection works. They never see its secret.
- 05
People handle sign-in codes
Sign-in codes and CAPTCHAs always go to a person, never to an agent.
- 06
Connect only what a goal needs
Ocally starts from your public presence. Kai offers to connect an account when a capability needs it.
Approvals
Human in the loop, by design.
Anything that matters waits for a yes from someone with the authority to give it. A chat message is not an approval. You approve the exact action.
- Owners set budgets and how much Ocally may do on its own, for the business or for one store.
- Edit the action and it needs approval again.
- Approved actions run once. A double tap never runs it twice.
- If a result turns harmful, the work pauses until the owner approves a safe change.
- Action
- Update holiday hours on two listings
- Store
- Downtown
- Reason
- Both still show last year's hours
- Expected effect
- Correct hours on search and maps
- Evidence
- Each profile, read the same day
- Approved by the ownerOnly the right person can approve.
- Runs onceExactly the action that was approved.
- Receipt keptWhich account, what was sent, what came back, and when.
On the record
- Every decision records who made it, when, and what happened next.
- Every setting change keeps who, when, the old value and the new one.
- From any result, follow the trail back to the goal, the plan, the task, the evidence and the proof.
Roles and permissions
Role-based access, store by store.
Everyone sees what is theirs to see and do. Nothing more.
| Role | Sees | Can do |
|---|---|---|
| Owner | Every store | Sets goals, budgets, how much Ocally may do on its own, users and connections. Resolves approvals. |
| Store manager | Assigned stores only | Runs daily work with Kai, reviews drafts, answers questions, resolves permitted approvals and invites staff to their stores. |
| Store employee | Assigned store work only | Completes tasks and shares facts and photos. Decisions go to a manager or owner. |
| Ocally staff | Only through a logged support path | Sets up and supports your platform. Access is explicit, scoped, time-limited and logged. Cannot sign in as you. |
Permissions are checked when an action is shown and again when it runs. Nobody sees a button for something they cannot do.
AI and your data
AI data security, answered plainly.
Ocally's agents work for your business, from your business knowledge, inside the limits you set.
Every agent reads the same truth
Kai, your briefings and every capability work from your own Knowledge Store, at the right scope. No copies. No drift.
Only what the task needs
Each task gets the slice of your knowledge for that store and that job, and only the access that job requires.
No guesses
Ocally never fills a gap with a guess, and never reports a gain it can't measure.
Safe when things fail
A provider outage never corrupts what Ocally already knows. A failed site update leaves the live site as it was, and you can roll back.
Rights checked first
Media with unresolved rights cannot be published. Ocally works from your brand kit, learned during setup.
Never used to train AI
Ocally does not train or fine-tune AI models on your data. Your content is used only to run the service for your business.
Read the Terms
Security questions, answered.
Who owns the data we put into Ocally?
You do. Our Terms say you keep ownership of the content you upload, create or share through Ocally. Your data lives in your own private platform, with a separate database and workspace no other client can reach. Disconnect any tool at any time, and the record of past work stays.
Does Ocally train AI models on our data?
No. Ocally does not train or fine-tune AI models on your data. Your content is used only to run the service for your business, on your own isolated platform, and nothing is shared with other customers.
How does Ocally protect business data in AI systems?
Every client runs on its own isolated platform. Agents get only the slice of knowledge a task needs, act through narrow, temporary, logged permissions, and never see a password. Passwords and tokens never appear in AI prompts, task files, logs or answers.
Can we control which actions go live?
Yes. Owners set budgets and how much Ocally may do on its own, for the business or for one store. Consequential actions wait for an approval from someone with the authority, and each request names the exact action, the store, the reason, the expected effect and the evidence.
Can Ocally staff see our data?
Only through a support path that is explicit, scoped, time-limited and logged. Ocally staff can see whether a connection works, never its secret, and they cannot sign in as you.
What happens when Ocally gets something wrong?
You correct it, and the same task picks up the change. The old version stays on record. A failed update leaves the live version in place, and you can roll back. If a result turns harmful, the work pauses until the owner approves a safe change.
Do you offer security and data protection terms?
Yes. Every contract can include Ocally’s standard security and data protection terms. Ask for them on your free consultation.
How do I report a security issue?
Email [email protected] with the details and the steps to reproduce it.