Privacy Policy

Account data

Each person signs in with their own account. We store an email address, a display name, and either a securely hashed password (never plaintext) or a sign-in reference from our identity provider. Accounts belong to an organization; people in the same organization see that organization’s data and nothing else.

Uploaded data

Files you upload (sales exports, appointment lists, job sheets, and similar) are stored for your organization only and used solely to build the analysis you asked for. They are never sold or used for advertising, and are shared only as described under “Sharing and transfer” below.

Connected Google accounts

An organization member may connect a Google account so the service can read data about the organization’s own business. Each connection asks only for the scope it needs:

• Google Analytics (read-only, analytics.readonly): daily website traffic and engagement metrics, and sessions by channel, for the property you choose.
• Google Business Profile (business.manage): the list of locations you manage and their daily performance counts -- search and maps impressions, calls, direction requests, website clicks, and conversations. We read these figures; we do not edit your listing, post, or reply to reviews.
• Google Calendar (read-only, calendar.readonly): event titles, times, and locations from the calendars the connected account can see, within a rolling window around today, to show upcoming sessions and measure bookings.

How we use Google user data

Data received from Google APIs is used only to provide the features you see in Business Intelligence: showing your figures back to your organization, and computing the metrics, forecasts, alerts, and work items you set up on them. Specifically, we do not:

• sell it, or use it for advertising, retargeting, or interest-based ads;
• use it to train or improve artificial-intelligence or machine-learning models, ours or anyone else’s. No Google user data is sent to an AI model;
• use it to determine creditworthiness or for lending purposes;
• let any person read it, except with your organization’s explicit permission (for example, to answer a support request you send), where needed for security purposes such as investigating abuse, or to comply with applicable law.

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sharing and transfer

We do not share Google user data or uploaded data with third parties, except in these cases:

• When your organization tells us to. A member with permission to manage data can issue a read key that lets another application the organization uses pull the organization’s metrics and the underlying records, including data synced from Google (for example calendar event titles, times, and locations). Members can also set up automations that send an alert by email or to a web address they choose. The data goes only where your organization sends it, and you can revoke a read key or delete an automation at any time.
• Service providers that run the service for us: Railway (application hosting and database storage), Auth0 (sign-in; it receives your account details, not data from Google APIs), and Resend (delivers the automation emails your organization sets up). They process data only to provide their service to us.
• When the law requires it, such as a valid court order.
• If the service changes hands through a merger or acquisition. We would tell you before your data became subject to a different privacy policy.

How we protect your data

• Encryption in transit: all traffic to and from the service, and every call we make to Google APIs, uses HTTPS (TLS).
• Encryption at rest for Google credentials: access and refresh tokens are encrypted with AES-256-GCM before they are written to the database. The key is kept separately in the server environment, not in the database. Tokens stay on the server and are never sent to a browser.
• Hashed secrets: passwords, and the API keys your organization uses to push or read data, are stored only as one-way hashes.
• Organization isolation: every request is checked on the server against the signed-in person’s organization membership, so one organization can never see another’s data. Platform administrators manage accounts but do not get access to an organization’s data through that role.
• Stallion support view: so Stallion can tell you when a connection breaks, Stallion support staff can see, for each organization, its name and, for each data source, what kind it is, which provider it connects to, whether it is connected, when it last synced, and a short failure message only when it is one of the fixed messages this service writes itself. Staff cannot see your data: no source names, rows, metrics, datasets, uploaded files, dashboards, reports, tokens or credentials, and no error message that could repeat your data. Staff sign in with a separate Stallion administrator account that requires a second factor, not a normal account, and every time they open the view it is recorded in your organization’s activity log as “Stallion support”.
• Least privilege: each Google connection asks only for the scopes listed above, and Analytics and Calendar access is read-only. Production systems can be reached only by the service’s operator.
• Incident response: if a security incident affects your data, we will tell the affected organizations without undue delay.

Data retention and deletion

Synced data is kept while the connection is active, to support historical reporting. Deleting a data source in the app deletes its stored Google credentials right away and stops further syncing. You can also revoke access at any time from your Google Account permissions page. Records already synced stay in their dataset until you delete that dataset, which removes its records permanently. To have every record for your organization deleted, including your accounts, email the address below and we will complete the deletion within 30 days.

Children

Business Intelligence is a tool for businesses. It is not directed to children under 13, and we do not knowingly collect their personal information.

Changes to this policy

If we change how Google user data is used or shared, we will update this page and change the date at the top. We will ask for your consent again before using data in a new way.

Contact

Questions about this policy or your data can be sent to dj@buildstallion.com. See also our Terms of Service.