Privacy Policy

Who we are

Operate With Intelligence (“OWI”) is a product of With Intelligence Inc., a Florida corporation incorporated in July 2026. This policy covers www.operatewithintelligence.com and the Mission Control and client-room software reached through it.

For anything in this policy, write to admin@operatewithintelligence.com or access@operatewithintelligence.com.

Speed Up Your Retirement assessment

The assessment uses the answers you choose to provide to explain business value drivers. OWI does not save these answers, financial estimates, or prepared conversation briefs through the assessment. Your chat platform may retain a conversation under its own policies.

If you agree to help us improve the assessment, we count the topic you select, completed reads, and use of the partner button. This is optional and starts unchecked. Our counter stores only the date, a fixed topic, the type of action, and its total. It does not store your answers, figures, name, email, chat text, or an IP address. These counts measure actions, not unique people or qualified leads.

Our hosting and database providers may process technical request information under their own policies. Opening the partner calendar takes you to the separate booking service; the assessment does not attach your answers. You choose whether to copy or share a prepared brief.

Limited Use of Google user data

We use Google user data only to provide the Operate With Intelligence service the client asked for. We do not sell it. Operate With Intelligence's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use data from Google APIs to develop, improve, or train generalized or non-personalized AI or machine-learning models. A named person approves anything that goes out.

What we collect

We collect only what the service needs to do its job.

• Account details. The email address you sign in with, and whether that address is on our staff list or is a member of a client workspace.
• What you tell us about the business. What you enter in the intake at /start and in the onboard form: the business profile, the people who run it, your goals, and what is currently painful. This is information you type, and you can correct it at any time.
• Connection consent. When you connect a system, we record which system, who approved it, and when.
• Google, when you connect a data app. There are five separate Google clients. Each asks only for the scopes below, if any, plus openid, email and profile so we can name the account. Staff sign-in is a sixth client and asks for those three identity scopes only.
  • OWI Mail (/google) — https://www.googleapis.com/auth/gmail.metadata. Message headers only — sender, date and subject line — never the text of a message.
  • OWI Business (/google/business) — https://www.googleapis.com/auth/business.manage. Listings and reviews. We never write to Google Business Profile in this slice.
  • OWI Mail + Calendar (/google/calendar) — gmail.readonly, https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/gmail.compose (drafts in the Drafts folder, never sent by us) and https://www.googleapis.com/auth/calendar.events (holds with no attendees, never an invitation, never a deletion). No calendar.acls.readonly. OWI staff accounts only: its consent screen is Google's Internal user type, so only operatewithintelligence.com Workspace accounts can grant it, and a client's account is refused by Google.
  • OWI Files (/google/files) — no data scope. It asks only for openid, email and profile, and has no access to Drive, Docs or Sheets.
  • OWI Search Console (/google/search-console) — https://www.googleapis.com/auth/webmasters.readonly. What people searched to find you: queries, impressions, clicks, average position and which pages earn them. Read only — we cannot change the site, submit a sitemap, or request indexing. Not webmasters, which would allow those writes.
• Meetings and transcripts. When a meeting between you and OWI is recorded through a tool you can see (Fireflies or Granola), the transcript and the attendee list are stored against your workspace. We send those tools nothing from your Google account. Where they hold calendar data of their own, it is through a Google connection you authorised inside Fireflies or Granola, separate from this product. Meetings booked with us — the title, the time and who attended — are stored the same way, taken from our own calendar and booking system rather than from yours.

We do not collect payment card details in this product, and we do not use tracking cookies for advertising.

What read-only means, exactly

On the Mail app, gmail.metadata permits reading message headers and labels — who wrote to whom, when, and the subject line — and never the text of a message. It does not permit sending, replying, deleting or modifying anything, and Google enforces all of that at the token: a request for a message body on this scope is refused by Google, not merely avoided by us.

On the Mail app, reading headers is the entire grant. That client asks for nothing from Google Calendar and nothing from Google Drive. The Mail + Calendar and Files clients are separate apps with their own Google clients, listed above; Mail + Calendar, on staff accounts only, holds gmail.readonly and reads message text.

Our code cannot send mail as you. On staff accounts the Mail + Calendar app holds gmail.compose, and that token could send; our code cannot. It has no send call, and two automated tests fail the build if one is ever added: one over the API service, and one over the mail and calendar tools, which asserts no send path, no calendar notification other than none, no delete, and no guest on a hold. Sending is the person's own press in their Gmail.

Headers are read so the software can see which threads are still waiting on a reply and how long work takes — who wrote, when, and about what. Nothing read from a mailbox is published anywhere without a person at OWI approving it first.

With the client's consent, given on our connect page before they grant access, named OWI staff may view the subject lines of recent messages, to confirm the connection works and to provide the service. We never send, change or delete email.

The systems you can connect

One rule holds across the connectors, and it is a property of what we ask for rather than a promise about how we behave: we request read access and not write access on every connector except Mail + Calendar on staff accounts. There we ask for two write scopes, gmail.compose and calendar.events, and use them for exactly two things: a draft in the Drafts folder, and a calendar hold with no guests. Where a provider offers only a combined permission, we say so on the screen where you grant it.

Google is five data apps, each a separate consent. Mail, Business, Mail + Calendar, Files, and Search Console — scopes listed above. Staff Google login is a sixth client and asks only for identity (openid, email, profile).

The rest are connected one business at a time. Each applies when and if you connect it — none of them reads anything of yours until you do, and describing them here is how the limits get agreed in advance rather than discovered afterwards.

• Jobber— in use, connected by OAuth, and read-only. When you connect it we read: requests, including the company name typed on a request; jobs, quotes and invoices, with their line items; visits and the team members assigned to them; job notes and who wrote them; custom field values on jobs and quotes; your team members’ names, including who the salesperson was; timesheet entries; and your custom field settings. We use it to see how work moves from request to quote to paid. We do not read your customers’ contact details: their names, email addresses, phone numbers or addresses. Notes and custom fields are free text your team wrote, so they can mention a customer; we keep them as Jobber returns them. We do not create, change or delete anything in Jobber.
• QuickBooks Online — in use, connected by OAuth, for the specific company you authorise (Intuit identifies it by a realmId), and read-only. When you connect it we read: the profit and loss, balance sheet and cash flow statements, month by month, with the reports behind them (profit and loss detail, general ledger, transaction list, sales by customer, expenses by vendor and trial balance); aged receivables and aged payables, with their detail; the transactions changed since the last read (invoices, payments, sales receipts, credit memos, refund receipts, estimates, bills, bill payments, vendor credits, expenses, deposits, journal entries, transfers and time activity); your lists of customers, vendors, products and services, accounts, employees, classes, departments, payment terms, payment methods and tax codes; your company information; and your accounting settings, including the date the books were closed. We use it to show what the numbers say. The customer, vendor and employee lists are read whole, as QuickBooks returns them, so they include the contact details kept on them: names, email addresses, phone numbers and addresses. We do not write invoices, bills or payments into QuickBooks. Refresh tokens rotate on Intuit’s schedule, and each company is a separate connection: authorising one does not give us any other.
• Quo (formerly OpenPhone) — in use, connected with an API key you issue, not OAuth, because that is what the provider offers, and read-only. When you connect it we read: your business phone lines (their name and number); the conversations on each line that changed since the last read, to find who each call was with; and the calls on each line, with their direction, status, start, answer and end times, and duration. We keep each call with those details, and monthly and daily counts of answered, missed and returned calls. We do not store your callers’ phone numbers: each caller is kept only as a code that cannot be turned back into a number. We do not request call recordings, transcripts, call summaries or the text of messages. We do not send calls or messages through Quo. Sending costs you money and would put us in a conversation with your customer under your name — neither is something this product does.

For every one of them the credential is encrypted before it is stored, is never committed to source control, and is readable only by the service that needs it. One client’s material is isolated from another’s.

How we use it

• To operate Mission Control and your client room.
• To prepare reviews and reports, which a person at OWI reads and approves before you ever see them.

Nothing is published, sent, or posted on your behalf without a human approving that exact action. There is no automatic publishing anywhere in this product.

We do not sell personal information. Data from Google APIs is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models.

Who else handles the data

These are the services we rely on. Each is listed because it is actually in use.

• Supabase — database, authentication and file storage.
• Vercel — hosting for the website and the application.
• Google — sign-in, and mail, calendar, business profile, files and search console data where you have granted it.
• Jobber — field service records, read-only, where you have connected it.
• Intuit / QuickBooks Online — accounting records, read-only, where you have connected it.
• Quo — business phone call records, read-only, where you have connected it.
• Fireflies / Granola — meeting transcription, where a meeting is recorded.
• Zoho Bookings — scheduling, if you book a call through the site.
• xAI (staff assistant only).OWI staff use an AI assistant, provided by xAI, to help with their own work email and calendar. It can only reach the mailboxes and calendars of OWI staff accounts, connected through our internal OWI Mail + Calendar application, which is restricted to our own Google Workspace and cannot be used by clients. No data from the OWI Mail application, and no data from any client's mailbox or calendar, is ever sent to xAI or to any other AI provider. OWI does not sell Google user data and does not use it to develop, improve or train AI models.

Your control

Withdrawing a connection is done from your side and takes effect immediately — you do not need our agreement or our help: Google in your Google Account’s security settings; Jobber by disconnecting the OWI app on its Apps page, which also deletes our stored copy, because Jobber tells us when you do it; QuickBooks Online by disconnecting the OWI app in its own connection settings; Quo by revoking the API key you issued. You can also press Revoke access on the connection in your own room, which deletes our stored copy — doing it at Google, QuickBooks Online or Quo ends our access there and leaves our copy to be deleted, so for a clean break with those do both. Parts of the product that depended on it stop working, which is the honest consequence rather than a penalty.

• Withdraw Google access at any time at myaccount.google.com/permissions. It takes effect immediately and needs nothing from us. Pressing Revoke access in your room does the rest: it deletes our stored copy of the credential and asks Google to end the grant as well. You can also ask us and we will press it for you.
• Correct what we hold about the business and its goals directly in your room.
• Ask for a copy, or ask us to delete it. Write to access@operatewithintelligence.com. We will confirm what we hold and what deleting it would remove before doing it.

How long we keep it

We keep working information for as long as we are engaged with you, and for a reasonable period afterwards so that a report can still be explained and its evidence produced. When you ask us to delete an engagement’s data we remove it from the live systems; ordinary backups age out on their own schedule.

When you press Revoke access on a connection in your room, we delete our stored copy of that connection’s credential. Where the provider publishes a revoke we can call — Google, QuickBooks Online and Jobber — we also tell them to end our access, and the room reports what they said. For a connection authorised by an API key you issued, and for a provider that publishes no revoke of its own, deleting our copy is the whole of our side: the key or the app itself is ended in your own account, and the room names where.

When you disconnect the OWI app on Jobber’s Apps page, Jobber tells us, and we delete our stored copy of that credential in the same way. Jobber has already ended our access by then.

Archiving a client when an engagement ends deletes the stored credentials for every connection that client made, in the same way.

What survives either action is the record and not the credential: which system, which account, the access that was granted, when we received it, when it stopped, and who ended it. Both are written to the account’s activity trail as they happen. We keep that because it is the only evidence of what we held and that we stopped holding it — the credential itself is gone and cannot be recovered.

Security

Access to client information is restricted at the database itself rather than only in the application, so a member of one client’s workspace cannot reach another’s. Credentials for connected systems are stored encrypted and are never written into our source code.

No system is perfectly secure, and we would rather say that than imply otherwise.

Where we operate

With Intelligence Inc. is a Florida corporation and the service is operated from the United States. If you use it from elsewhere, your information is processed in the United States.

The service is for businesses. It is not directed at children, and we do not knowingly collect information from them.

Changes

If we change what we collect or how we use it, we update this page and move the effective date. Material changes are told to the people using the service, not left to be discovered here.