AUDIGRAM / Privacy

Privacy policy

Effective October 3, 2026 · Version 2026-10-03.1

What Audigram collects, why it is needed, and how to make a privacy request.

01Scope

This policy covers audigram.net, Audigram accounts, direct purchases, licensing, updates, and support. Third-party services have their own policies. See the Security & AI Policy for product-data details.

02Information collected

  • Account and contact information, including name and email address.
  • Purchase details, including product, amount, date, billing contact, payment status, and order identifier. Stripe processes card data; Audigram does not receive your full card number.
  • Technical data needed for security and licensing, including IP address, browser or device type, OS and app version, request logs, and license or activation status.
  • Support messages, diagnostics you choose to send, and data you direct an optional integration to exchange.

03Sources and third-party collection

We receive information directly from you; automatically from your browser, device, and Audigram app; and from providers you use with Audigram, including payment, account, licensing, hosting, email, fraud-prevention, and optional integration providers.

Payment and optional integration providers may collect information across the sites and services where they operate under their own policies. Audigram does not add third-party advertising trackers or permit cross-site behavioral advertising through Audigram services.

04Local project data

Audigram does not upload project files, audio, scripts, source documents, prompts, or AI results for cloud AI processing. Local models and their processing stay on your Mac unless you deliberately send information for support or through an optional integration.

05Google user data (READS and LINES)

READS and LINES can connect to Google Sheets so you can work with your script and session sheets directly. This section explains what Google data these apps access and how it is handled.

What we access. When you choose to connect an app to Google Sheets, it asks Google for permission to see and edit your Google Sheets spreadsheets. It may also ask for your email address, only to show which Google account is connected.

How we use it. The apps open only the spreadsheets you choose. They read and edit those sheets to provide the app's features, for example reading a session script and writing back results such as line status, transcripts or volume labels. Google user data is used for nothing else.

Where it is processed. All processing happens on your Mac. The apps do not keep copies of your spreadsheets: sheet contents are read and edited directly in your Google account. Google user data is never sent to Audigram's servers or to any cloud AI service. Any AI features in these apps run entirely on your Mac using local models.

Your sign-in. The permission Google grants is stored only on your Mac (READS uses the macOS Keychain). Audigram never receives your Google password or sign-in.

Sharing. Audigram does not sell, rent, share or transfer Google user data to anyone. We do not use it for advertising, and we do not use it to develop, improve or train AI or machine-learning models. Audigram staff cannot access your Google data.

Your control. You can disconnect at any time: use Sign out in the app, or remove "Audigram Applications" in your Google Account under Security → Third-party apps & services. Disconnecting stops all access immediately.

Limited Use. Audigram'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.

Questions about this section: info@audigram.net

06Use and disclosure

We use information to operate accounts, purchases, licenses, downloads, updates, and support; prevent fraud; improve reliability; and meet legal, tax, and security obligations.

We share only what is needed with service providers for hosting, accounts, licensing, email, payments, and fraud prevention, or when required by law or a business transfer. Stripe processes payments under its own Privacy Policy. Audigram does not sell personal information or share it for cross-context behavioral advertising.

07Cookies and browser storage

Audigram does not use advertising cookies, analytics cookies, or browser storage for behavioral tracking. Public pages do not set Audigram account cookies. Our account service uses cookies only to sign you in, maintain your current session, and protect account actions.

Audigram does not offer a save-login or keep-me-signed-in option. New account-session cookies are browser-session cookies, with a server validity limit of 24 hours. Signing out invalidates the session. A browser that restores previous sessions may retain session cookies; you can also remove them in your browser settings. Browser password saving is controlled by your browser, separately from these cookies.

Our hosting provider uses Cloudflare for traffic protection. Cloudflare may set the security cookie __cf_bm on public pages, including before you sign in. It expires after 30 minutes of inactivity and is used for bot protection. See Cloudflare’s cookie information.

Auth0 operates our sign-in service and uses its own cookies for authentication and attack protection, including session and device-security cookies where applicable. Their lifetimes depend on Auth0’s session and security settings. See Auth0’s cookie information. These provider cookies are separate from Audigram’s account-session cookies.

Stripe’s hosted checkout is opened when you choose to acquire an app; Stripe scripts are not embedded on our public pages. Stripe controls cookies and storage on its checkout under its own Cookie Policy. Audigram does not use checkout cookies for advertising or visitor analytics.

Necessary authentication and security cookies are used for those purposes only. We do not sell personal information or share it for cross-context behavioral advertising, regardless of browser privacy signals. Other Do Not Track signals do not change these necessary functions.

  • __Host-authsystem_v2_session — account.audigram.net; signs you in for the browser session, subject to the 24-hour server limit. The cookie is inaccessible to page scripts.
  • __Host-authsystem_v2_csrf — account.audigram.net; protects account actions from forged requests. It lasts for the browser session, subject to the same server limit.
  • __Host-authsystem_v2_login_* — account.audigram.net; binds a sign-in attempt to your browser. It lasts up to 10 minutes and is removed when the sign-in callback completes.
  • __Host-authsystem_v2_verification and __Host-authsystem_v2_verification_csrf — account.audigram.net; protect email-verification actions for an unverified sign-in. They expire after 30 minutes.

08Retention and security

We keep information only as long as needed for service, support, fraud prevention, disputes, and legal or accounting obligations. We use reasonable safeguards, but no system is completely secure.

09Privacy requests

Depending on applicable law, you may ask to access, correct, delete, or receive a copy of information associated with you by emailing info@audigram.net. We may verify your identity and retain records required for licenses, transactions, security, or law.

We will not discriminate against you for exercising a privacy right. If applicable law gives you a right to appeal our response, reply to our decision and label the message “Privacy Appeal.”

10Updates and contact

Revised policies will be posted here with a new effective date. Material changes will also be identified by email, account, or in-app notice when appropriate or required.

Audigram LLC is based in Los Angeles, California. Questions may be sent to info@audigram.net.