AN Software LLC

Privacy Policy

Applies to Verrandi. Effective 2 November 2026 (Google user data section added; earlier version 6 September 2026).

The short version: your business records are held in a database instance dedicated to you. We do not sell them, we do not share them with advertisers, and we do not use them to train machine-learning models. We do hold operational access to that database, and processes we run read your connected systems on a schedule, including when nobody is signed in. This page is specific about that rather than reassuring about it.

Who we are

Verrandi is built and operated by AN Software LLC ("we", "us"), a California limited liability company. Contact us at alex@verrandi.com.

This policy covers Verrandi, including its connections to Google (Gmail, Google Drive, Google Calendar, Google Contacts, Google Analytics and Google Search Console), to QuickBooks Online, and to any other system a customer chooses to connect.

Where your data lives, and who holds the keys

Each customer's data is held in a database instance dedicated to that customer. We do not maintain a combined store of customer content across customers.

There are two arrangements, and which one applies to you is agreed when you start:

• Managed — the default. The database instance is dedicated to you and the records in it are yours, but we create and administer it, and we hold the administrative credentials. In practice this means we can reach your content. We do so to operate and repair the service, not to read your business.
• Sovereign — the database belongs to your own cloud account and you hold the administrative credentials. We reach it only through the access you grant.

Some connected systems are read live rather than copied. QuickBooks Online is one of these: accounting records are read from Intuit at the moment a question is asked and are not written into our storage.

When we read, and on whose authority

Verrandi reads your connected systems in two ways, and one of them is unattended.

In the background. Scheduled processes we operate collect content from connected sources — email, documents, calendar — using the authorization granted by the person who connected each source. These run on a schedule whether or not anyone is signed in. This is how the system stays current, and it means that connecting a source is a standing grant rather than a per-session one.

When you ask. Answering a question reads from what has already been collected, and may read a live system such as QuickBooks Online at that moment.

Who can see what

When a person signs in, what they can retrieve is limited to the sources they have been granted and to content about them personally. That limit is applied when content is retrieved, before it reaches the reasoning step.

Two things about this you should know rather than discover. First, the limit is enforced at the level of the source — a person granted a source can retrieve what was collected from it. It is not a per-item re-check against the permissions of the original system, so it will not by itself reproduce fine-grained sharing rules inside a mailbox or a document store. Second, an administrative role exists that can retrieve everything in your instance. Your own administrator holds it, and so do we under the managed arrangement above.

If a category of material must never be reachable through Verrandi, do not connect the source that holds it. That is the only boundary we can promise today.

Credentials

Access credentials — including OAuth tokens for Google and for QuickBooks Online — are held encrypted in your own database instance. They are not held in a shared store.

They do, however, pass through services we operate. When you first authorize a system, the authorization code is exchanged for a token by a service of ours, which then writes the token to your instance; when a token is renewed, the renewal passes through that same service. Your business records do not pass through it. We state this plainly because it is a real qualifier on the sentence "your data stays in your own database," and we would rather you read it here than infer it later.

Intuit and QuickBooks Online data

Specific to the QuickBooks Online connection:

• We request only the accounting scope, and only for companies you explicitly connect.
• Accounting data is read on demand to answer a question or prepare a proposed change. It is not copied into our storage, not indexed, and not retained after the request completes.
• We do not write to your books without you approving the specific change first.
• We do not disclose QuickBooks data to any third party except the infrastructure providers named below, and we do not use it for advertising or profiling.
• Disconnecting removes our authorization. See how to disconnect.

Google user data

Specific to the Google connections. Each is made by one person signing in with their own Google account and agreeing on Google's own screen to what is listed there.

What we access, and what we do with it

• Gmail, read. The messages and attachments in the mailbox that was connected, so the person can ask questions answered from their own email and see what needs their attention.
• Gmail, send. Sending an email from that mailbox, only when a person presses send on a message they have seen. Verrandi never sends on its own.
• Google Drive, read. The files the connected account can open, so answers can come from the business's own documents.
• Google Calendar and Google Contacts, read. Events and contacts of the connected account, to show meetings and who a person is to the business.
• Google Analytics and Google Search Console, read. For the business owner only: website visits and search results, shown in the marketing view.
• Your name and email address, to confirm that the account that signed in is the account being connected. A sign-in by any other account is refused and its permission is given back to Google.

Storage. Unlike QuickBooks data, content read from Google is copied into the customer's dedicated database so it can be searched and answered from. Google tokens are held encrypted there. Both are covered by "Where your data lives" and "Retention and deletion" on this page.

Artificial intelligence. To answer a request, the parts of Google content needed for that request are sent to our language-model provider, under terms that bar training on it and limit how long it is kept. Google user data is not used to develop, improve or train generalized or non-personalized AI or machine-learning models, by us or by any provider on our behalf.

People. No person at Verrandi reads Google user data, except: with the customer's explicit agreement for specific items (for example to resolve a support request they raised); when needed for security, such as investigating abuse or a vulnerability; to comply with applicable law; or where the data has been aggregated and anonymized for running the service. We keep a written record of each such access, saying who, when and why.

Sharing. Google user data is not sold, not used for advertising (including retargeting or personalized or interest-based advertising), not used to decide creditworthiness or for lending, and not transferred to anyone except: the infrastructure providers named on this page, as needed to provide the features the person uses; as needed for security or to comply with the law; or as part of a merger or sale of the business, with notice to customers.

Removing access. Disconnecting stops collection; see how to disconnect. You can also remove Verrandi's access at any time at myaccount.google.com/permissions. To have collected content deleted, write to alex@verrandi.com.

Limited Use. Verrandi's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What we never do

• We do not sell customer data, and we do not share it with data brokers or advertisers.
• We do not use customer content to train machine-learning models, and we do not permit our providers to do so.
• We do not read customer content to build products or profiles.

Service providers

Verrandi runs on infrastructure operated by third parties, including database and cloud hosting providers and the provider of the language model that performs reasoning. Content is sent to the reasoning provider only as needed to answer a request. We select providers whose business terms bar training on the content sent to them and limit its retention, and we do not authorize any provider to use customer data for its own purposes. Their own terms govern what they do, and we cannot audit them beyond what those terms allow.

Retention and deletion

Collected content stays for as long as you keep the source connected. Disconnecting a source stops further collection but does not by itself delete what was already collected. Write to alex@verrandi.com to have it deleted and we will do so. Under the sovereign arrangement you may also delete the database directly. Operational logs that record that a request occurred, without its content, are kept for a limited period for security and reliability.

Security

Credentials are stored encrypted. Retrieval is denied by default and permitted only after the signed-in person's identity is resolved from their own session. We run automated checks that look for misconfiguration which could widen access, and we treat a finding as an incident. These checks run on a schedule, so they detect a problem rather than prevent one, and there is a window between a misconfiguration appearing and a check noticing it.

We have no third-party security certification — no SOC 2, no ISO 27001 — and we do not claim one.

Your rights

You may ask what is held about you, ask for a copy, ask for correction, or ask for deletion, by writing to alex@verrandi.com. We aim to respond within 30 days. Depending on where you live you may also have the right to complain to a data protection authority.

Children

Verrandi is a business product and is not directed to anyone under 18.

Changes

We may update this policy. The current version is always the one on this page, and the effective date above changes when it does. We do not operate a notification list, so check this page if it matters to you.