Legal · Version 2026-09-23

Privacy Policy

Effective September 23, 2026

Infinitum Imagery LLC (“Infinitum,” “we,” “us,” or “our”) operates Ackvio. This Privacy Policy explains how Ackvio collects, uses, discloses, and protects information about account holders, connected mailboxes, message recipients, integration contacts, and website visitors.

Scope and roles

This policy covers Ackvio websites, applications, APIs, tracking endpoints, and support. For account, billing, security, and product-usage information, Infinitum generally determines the purposes of processing. When a customer uses Ackvio to send or analyze email, the customer determines the recipients and purpose; the customer is responsible for its notices and lawful basis, and Ackvio processes recipient data to provide the requested service.

Account, preferences, and consent information

Firebase Authentication processes your account identifier, email address, verification status, display name, authentication provider, sign-in events, and security information. Ackvio stores account preferences such as reporting timezone, notification choices, theme and display settings, and Guide Center completion so those preferences can follow your account across supported browsers and devices. During account creation, you may optionally tell us how you heard about Ackvio; if you choose Other, we also store the short description you provide. We use this attribution information to understand which outreach helps people discover Ackvio, not for cross-context behavioral advertising. Ackvio also stores the current Terms and Privacy versions you accepted, acceptance time, consent source, and optional marketing choice. Marketing consent is separate, optional, and may be withdrawn.

Connected provider information

When you connect an email provider, Ackvio receives the provider account identifier, mailbox address, approved OAuth permissions, authorization tokens, connection timestamps, and provider responses needed to operate the integration. For Gmail, Ackvio requests standard identity information and permission to send email; it does not request permission to read Gmail message metadata, bodies, attachments, labels, or mailbox contents. Refresh tokens are encrypted at rest. Permissions depend on the provider and feature. Disconnecting or revoking provider access stops future provider operations but does not automatically delete existing Ackvio records.

Google API data

Ackvio’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide or improve the prominent user-facing Ackvio features you request, secure those features, comply with applicable law, or complete a transfer permitted by that policy. We do not use Google user data for advertising, sell it, or allow personnel to read it except with your affirmative agreement for specific data, when necessary for security, when required by law, or in aggregated form for lawful internal operations.

Message and engagement information

For messages sent through Ackvio, we process the sending and recipient addresses, subject, sending status, provider message identifier, timestamps, tracked links, reminder settings, and open or click events. Ackvio does not retain the message body after the provider accepts the send. Open tracking uses a small image; link tracking uses an Ackvio redirect. Provider caching, privacy systems, scanners, and bots may generate or hide events, so activity is a signal rather than proof of human reading.

Contacts, templates, signatures, campaigns, and imports

When you save an email template, Ackvio encrypts and stores its name, subject, and message body in your private account until you edit or delete it. When you save an email signature, Ackvio similarly encrypts and stores its name, format, content, and default selection until you edit or delete it. When you create a campaign or contact list, Ackvio stores the contact email address, names, company, customer-provided personalization fields, campaign name and subject, recipient count, delivery status, and engagement metadata. For scheduled campaigns, message content and personalization fields are encrypted while queued and each queue item is deleted after delivery, permanent failure, cancellation processing, or expiration. Recipient suppression records are retained to honor campaign opt-outs. CSV files are parsed on your device and valid contact records are sent to your private Ackvio account; the original file is not uploaded. For a Google Sheets import, you provide a sharing URL and Ackvio retrieves the selected sheet as CSV from Google. The sheet must be available to anyone with the link as a viewer; do not use this method for information that should not be link-accessible. Ackvio does not request Google Sheets account access for this feature.

Inbox Cleanup

Ackvio Sweep can analyze a sender list or CSV locally in your browser. The private browser-integration beta can group sender names and addresses from message rows currently visible in supported webmail pages after you grant site access. This local analysis is not uploaded to Ackvio and does not traverse an entire mailbox, read message bodies, or directly delete, archive, report, block, or unsubscribe. You review cleanup candidates and perform mailbox actions in your provider. If you save a dismissal, Ackvio stores the sender identity and timestamps in your private account until you restore it. Historical Sweep action records created before connected scanning was retired may remain available to their account owner under the retention rules below.

Browser extension and local tools

The Ackvio browser extension can read the recipient, subject, and HTTPS links in a supported webmail composer when you enable tracking, then send that limited information to your private Ackvio account to prepare Engagement Signals. It can display Ackvio status information alongside matching sent-message rows and stores a random, revocable pairing token plus your tracking preference in browser extension storage. The extension never receives provider OAuth tokens. When you invoke Screen Shot, Chrome grants temporary access to the visible tab so the extension can create a local PNG preview and download. When you invoke Record Screen, the browser's own sharing chooser controls the selected tab, window, or screen; the resulting WebM recording stays in the extension page until you download or close it and is not uploaded to Ackvio. PDF Signatures reads the PDF and signature image you choose, creates a visually signed PDF locally, and does not upload either input or output. The visual signature is not a certificate-backed digital signature. PDF Tracking in Version 1.0.0 tracks qualified activity on a user-provided HTTPS document link; Ackvio does not host the PDF or claim page-level reading analytics.

Integrations, APIs, and administration

We process API-key hashes and prefixes, webhook destinations, encrypted webhook secrets, request counts, contact engagement summaries, and delivery results. Data sent to a webhook or customer-selected integration is disclosed at the account holder’s direction and is then governed by that destination’s practices. The restricted owner administrator can view account identity, plan and subscription state, account and sending timestamps, connected-mailbox count, and aggregate send, engagement, contact, template, and campaign counts for service operations, abuse prevention, support, and capacity planning. This owner view does not disclose recipient addresses, subject lines, message bodies, template or signature contents, contact records, OAuth tokens, API keys, webhook URLs, or CRM records. Owner administrators may grant complimentary plans; Ackvio records the affected account, prior and new plan, administrator, and timestamp.

Referral program

If you participate in the referral program, Ackvio processes your referral code and link, attribution between the referring and referred account identifiers, qualifying Stripe invoice and subscription identifiers, commission amounts, hold and payout status, payout contact email, legal recipient name, and acceptance of referral terms. Referral dashboards do not reveal the referred customer’s email address or mailbox data. We use these records to calculate commissions, prevent fraud, handle refunds and disputes, review payout requests, meet tax and accounting obligations, and resolve questions. Referral, payout, tax, and anti-fraud records may be retained as legally or operationally required even after account deletion.

Device, network, and log information

Ackvio receives ordinary technical data such as browser type, request time, referring page, error details, and connection address through hosting and security systems. To limit repeated Free workspaces, Ackvio uses a random identifier in local browser storage and stores secret-keyed, one-way hashes derived from that identifier and a network address. The anti-abuse record is not a hardware fingerprint and is not used for advertising. Shared-device or shared-network users may request review.

How we use information

We use information to authenticate users; create and administer accounts; connect providers; send requested messages; provide tracking, reports, reminders, cleanup, APIs, and webhooks; process subscriptions; deliver support; secure and debug the Service; prevent abuse; enforce limits; comply with law; and improve reliability. Where applicable, processing may be based on contract, consent, legitimate interests in operating and protecting the Service, and legal obligations.

How we disclose information

We disclose information to infrastructure and authentication providers such as Firebase and Google Cloud; connected email providers as directed by users; Stripe for checkout, subscription, tax-ID, invoice, and payment processing; customer-configured CRM, webhook, and automation destinations; professional advisers under confidentiality; transaction counterparties subject to appropriate safeguards; and authorities or affected parties when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or secure the Service. Ackvio does not receive or store complete payment-card numbers. We do not sell personal information or share it for cross-context behavioral advertising.

International processing

Ackvio and its service providers may process information in the United States and other countries where privacy laws differ. Where required, we use recognized transfer mechanisms or contractual safeguards. Customers are responsible for any additional transfer requirements arising from their recipient data and chosen integrations.

Retention

We retain account and service records while the account is active and as reasonably necessary for security, support, disputes, legal compliance, and enforcement. Provider tokens are retained until disconnected, revoked, deleted, or no longer needed. Message metadata and engagement history follow applicable plan and operational retention limits. Consent, billing, security, and audit records may be retained longer where necessary to demonstrate compliance or prevent fraud. Backups and logs may persist for a limited period after deletion.

Your rights and choices

Depending on location, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal information; withdraw consent; opt out of marketing; and appeal or complain to a regulator. These rights may be limited by law and the rights of others. Account holders can archive a tracking record without interrupting its links, permanently delete a tracking record and its event history, disconnect a mailbox to revoke its provider authorization, or permanently delete their Ackvio account from Settings & account. Deleting an Ackvio tracking record does not recall the delivered provider email and may stop its Ackvio tracking links from resolving. Recipients can use the unsubscribe link in an Ackvio campaign to join that sender’s private suppression list.

Children

Ackvio is not directed to children and is intended for users age 18 or older. We do not knowingly create accounts for children. Contact us if you believe a child provided personal information.

Security

We use encrypted transport, restricted server access, encrypted provider tokens and webhook secrets, hashed API keys, signed sessions, email verification, and auditing appropriate to the Service. No online system is completely secure, and users must protect their credentials and provider accounts.

Cookies, local storage, and device caching

Ackvio uses strictly necessary cookies or browser storage for authentication, security, preferences, notification state, and Free-plan abuse prevention. Public interface files such as scripts, styles, and icons may be cached on your device to reduce repeat downloads; authenticated API responses and mailbox data are not placed in that static cache. Ackvio does not use these technologies to sell data or serve third-party behavioral advertising.

Changes

We may update this policy for legal, provider, security, or product changes. The version and effective date identify the current policy. When required, we will provide notice or request renewed acknowledgement.

Contact

Submit privacy requests, deletion requests, marketing opt-outs, or shared-network appeals to support@infinitumlive.com. We may need to verify identity before fulfilling a request. This policy should be reviewed periodically by qualified privacy counsel for every jurisdiction where Ackvio is offered.