Privacy at Ganivra

Accounts and authentication

When you create an account, Supabase processes your email address and authentication data so we can secure your workspace. Ganivra stores workspace membership and telemetry metadata needed to provide the product.

Optional profile details

You can provide your name, job title, company role, company name and website, industry, company size, and goals for using Ganivra. We store these details with your account to understand our users and improve the product. They are self-reported and do not change your workspace permissions. Profile fields are not included in our Google Analytics events. You can edit or clear these details in Profile & setup.

Website analytics and advertising

Our public website loads these services. Each may use cookies or similar technologies and processes data such as your IP address, browser and pages visited under its own privacy terms:

• Google Analytics, to understand aggregate website usage, such as visits and interactions.
• LinkedIn Insight Tag and the OpenAI advertising pixel, to measure our advertising and count conversions such as trial clicks, sign-ups and pricing review contact requests.
• Apollo.io website visitor tracking, which helps us see which companies, and in some cases which people, visit our website, using information Apollo holds.

The events we send to these services describe actions, such as starting or completing a pricing review, and broad categories. We do not send them the website you review, your name, your email address, or figures you enter. You can block these services with your browser’s privacy settings or a content blocker; the website still works without them.

AI economics calculator submissions

When you calculate results with your own entries, Ganivra stores the submitted use case, any industry and outcome descriptions, cost and revenue figures, workload counts, optional targets and previous costs, and the submission date. Calculations using an unchanged built-in example are excluded. Edited examples and restored entries are labelled separately. These figures are self-reported and are not independently verified.

We use submissions to understand AI economics, improve Ganivra, and prepare aggregated benchmarks and industry reports. We do not publish individual submissions or raw industry and outcome descriptions. Reports describe their source as user submissions and do not treat submission counts as counts of unique businesses.

Calculator submission records are not linked to your Ganivra account, email address, or IP address. We assign a random submission ID to prevent duplicate writes. Hosting and security services may separately process request information, including IP addresses. Do not enter names, contact details, customer information, or confidential information in the description fields.

We retain submissions for analysis and aggregate reporting, periodically reviewing whether they are still needed. Contact founder@ganivra.com with privacy or deletion questions. Because submissions are not linked to an account, we may need details about the submission to locate it.

The optional “Save analysis on this browser” control also keeps a separate local copy on your device. Clearing that browser copy does not delete a server submission. Google Analytics receives calculator interaction events and broad use-case categories, but our calculator events do not include your entered financial figures or free-text descriptions.

AI Invoice Reconciliation research and pilot requests

The checker processes CSV files in your browser. We store usage actions, input source (sample or file), comparison mode, and broad error stages with random session and comparison identifiers. The session identifier is kept in session storage; it does not identify a person or a unique business. No raw files, filenames, account labels, customer IDs, model names, or error text are included.

If you select the optional summary-sharing checkbox, your next real-file comparison also sends usage and invoice totals, differences, period length, coverage counts, cost basis, model/customer counts, and missing-data flags to Ganivra’s research database. Sample financial figures are excluded. Google Analytics receives categorical events only, not these summaries or contact details.

Submitting the pilot form saves your email, company, role, and selected bottleneck and links them to the activity and opted-in summaries from the same browser session. We use this information to assess demand, improve reconciliation, and contact you about the pilot. All submitted costs and identities are self-reported and unverified. We do not publish individual financial or contact records.

Research records are retained for ongoing product analysis and reviewed periodically for continued need. Reloading or clearing the checker does not delete server records. Contact founder@ganivra.com for deletion requests; pilot email or the session reference shown in the checker can help locate records. Hosting and security services may separately process request information.

Free pricing strategy reviews

When you request a pricing review, we read the public pages of the website you enter and send their text to Google Gemini to extract plans and prices. We store the website address, the extracted facts, the review, and a salted hash of your IP address that changes daily and is used only to limit how many reviews one visitor can run. Reviews are private to their link and are not published.

After a review, you can leave your name and email if you tick the consent box. We store them with your review and add them, with the website you reviewed, to our CRM provider Apollo.io, which processes them under its own privacy terms. We use them only to contact you about your review and pricing, and you can unsubscribe anytime. Contact founder@ganivra.com to have your details removed.

Product telemetry

Ganivra is designed around execution metadata. Model events may include provider, model, operation, tokens, latency, status, error category, and customer-supplied business identifiers. The telemetry model does not store prompt or response bodies; prompt-level economics use customer-supplied prompt IDs and version labels. The API rejects events whose attributes are named like content, such as prompt, response, messages or tool output. The metadata policy lists what each event may carry and how long we keep it.

The identifiers you send, such as customer, user and conversation IDs, are yours to choose. Use internal IDs rather than names or email addresses where you can.

Coding tool telemetry

If you send OpenTelemetry from Claude Code, GitHub Copilot or similar tools, Ganivra reads only usage metadata: model, tokens, cost, session and timing. Prompt, response and tool content in that telemetry is never copied. To show cost per person, we use the first identity the telemetry carries, which can be the developer's email address or account ID. It is stored as that call's user ID and is visible to members of your workspace. Set ganivra.user_id in your telemetry resource attributes to send a different label.

Your own GPUs

When you add a GPU pool, we store its name, GPU type and count, hourly rate, the models it serves, its dates and the price you compare it to. We calculate a daily cost from these figures and store each day's total, call count and rate. No personal data is involved. These costs are estimates; the terms explain their limits.

MCP telemetry

MCP events may include server name, tool name, transport, authentication category, latency, outcome, direct cost, bounded counts or flags, and links to other steps in the execution. Customers should not send tool arguments, tool results, OAuth scopes, credentials, workspace IDs, prompts, or responses.

Where data is processed

We use these providers to run Ganivra. Each processes data under its own terms:

• Supabase, for sign-in and the database that holds workspaces and telemetry.
• Google Cloud, to host the website and API.
• Google Gemini, to read public website text for free pricing reviews only. Workspace telemetry is not sent to it.
• Apollo.io, for contact details you choose to share after a pricing review, and for website visitor tracking.
• The analytics and advertising services listed above, on the public website.

How long we keep data

Workspace data, including telemetry, costs, revenue, budgets, GPU pools and the audit history, is kept while your workspace exists, so reports and past figures stay reproducible. Nothing expires automatically today. When a workspace is deleted at your request, we delete its data. The metadata policy lists each kind of record.

Your choices

You can stop sending telemetry at any time by removing the SDK initialization or the OpenTelemetry exporter. To delete an account, a workspace or specific events, or to ask what we hold about you, email founder@ganivra.com from the address on the account. We confirm by email when it is done.