Legal

Data Handling & Security

Effective date: October 9, 2026

To organize and automate your business, we sometimes need access to the tools you run it on. That's a real ask, so here's exactly how we handle it.

The short version: we ask for the least access the work needs, your data stays in your accounts, and when the project ends, our access ends too.

1. We only ask for what the project needs

Before we start, your Scope of Work lists the tools we'll touch and why. We ask for the narrowest access that gets the job done — and nothing beyond it.

Wherever a tool allows it, we ask you to add us as a user with our own login and limited permissions, instead of sharing your password. That way you can see what we can access, and you can remove us with one click at any time.

2. Your data stays in your tools

We build inside your accounts — your Google Workspace, your CRM, your spreadsheets — so your business data lives where it already lives, and you own everything we build.

We don't keep copies of your business data beyond what a project needs to work, and we never sell it, share it, or use it for anything other than your project.

3. How we protect access

• Passwords and keys are never sent or stored in plain text. Not in email, text messages, chat, documents, or spreadsheets.
• Credentials an automation needs are stored in the automation platform's encrypted credential storage, or in your own password manager.
• Two-factor authentication is turned on for every account we use to do your work.
• Read-only access is used whenever a task only needs to read information — for example, financial dashboards use read-only connections that cannot move money.

4. Who can see your information

Only the people working on your project. We don't share access with anyone else unless you approve it in writing.

5. The tools we build with

Most of our builds use a small set of trusted platforms — such as n8n for automations and Google Workspace — plus the tools you already use. The specific tools for your project are listed in your Scope of Work before any work begins.

If a build uses AI — for example, to sort transactions or summarize information — we use the provider's business offering, which does not use your data to train their models by default. We'll tell you up front if your project includes AI.

6. When the project ends

At the end of a project, or whenever you ask:

1. Everything we built is handed over to you, in your accounts.
2. Our access is removed, or we confirm you've removed it.
3. Any copies of your data on our side are deleted within 30 days.
4. We confirm all of this in writing.

7. If something goes wrong

If we confirm that your information or accounts were accessed or exposed without permission, we'll tell you promptly — and always within the time the law requires — and work with you to fix it.

8. Questions

Want to talk through any of this before you start? Email privacy@cejasolution.com — we're happy to walk you through it on a call. For how we handle information collected through this website, see our Privacy Policy.