Privacy Policy

ALVERA PRIVACY POLICY

Privacy and data-handling disclosures for the Service.

Provider: Sean Dotts d/b/a Alvera

Version: 2026.05.08-enterprise.vFinal

Effective Date: May 8, 2026

Contact: Sean.dotts@gmail.com

1. Overview

This Privacy Policy explains how Sean Dotts, an individual doing business as Alvera ("Alvera," "we," "us," or "our") collects, uses, discloses, and protects information in connection with the Service. Alvera is currently operated by Sean Dotts under the trade name Alvera and may later be assigned to Alvera LLC or another successor entity.

2. Scope

This Privacy Policy applies to the Service, including Alvera applications, websites, APIs, user accounts, workspaces, uploads, exports, support interactions, and related services. The Service is intended for business and professional use.

3. Information We Collect

Account and identity information, such as name, email address, authentication identifiers, workspace membership, roles, and invitation details.

Customer Data submitted to or processed through the Service, including CRM records, property information, lead information, notes, schedules, appointments, files, attachments, resources, and configurations.

Usage and security information, including IP address, user agent, device and browser details, login and MFA events, audit logs, export events, upload scanning status, legal acceptance evidence, access events, and operational metadata.

Billing and transaction information processed in connection with subscriptions and payments.

Integration information associated with enabled services such as Google OAuth, Google Calendar, maps, geocoding, billing, or email delivery.

4. How We Use Information

Provide, operate, maintain, support, and improve the Service.

Authenticate users and manage accounts, invitations, roles, workspaces, and access controls.

Process Customer Data and uploaded files as instructed by Customer and as necessary to provide the Service.

Perform security, integrity, anti-abuse, audit, upload scanning, export governance, and legal acceptance functions.

Preserve evidence, enforce agreements, investigate misuse, respond to security incidents, and comply with legal obligations.

Process billing, subscriptions, customer support, and operational communications.

5. Uploads and File Security

Supported upload workflows may use asynchronous upload security scanning. Uploaded files may be stored in a pending state and may remain unavailable in normal product workflows until scanning completes with a clean status. Files that are flagged, infected, fail scanning, or remain unverified may be blocked, restricted, or removed from storage.

Alvera supports integration with ClamAV-compatible scanning infrastructure when configured and may use baseline file safety validation when such infrastructure is not configured. These measures are designed to reduce risk, but no scanning system can guarantee detection of all malicious or unsafe content.

6. Restricted Evaluation and Security Monitoring

Certain users, invitations, workspaces, or access contexts may be designated as Restricted Evaluation Access. In those contexts, Alvera may use additional logging, watermarking, export restrictions, legal acceptance requirements, and access controls to protect confidential product information and the Service.

7. AI and Analytics

Alvera does not currently send Customer content to third-party generative AI model providers. Alvera does not currently use common third-party session replay analytics tools. Alvera may maintain internal application, security, and audit logs in its own systems.

8. Service Providers

Alvera uses service providers to operate the Service. Current providers may include Supabase for authentication, database, and storage; Vercel for hosting and deployment; Stripe for billing and payments; and Google services for OAuth, calendar integration, maps, places, and geocoding functionality. Alvera may update service providers as the Service evolves.

9. Disclosure of Information

We may disclose information to service providers, as directed by Customer, to comply with law, to respond to legal process, to prevent fraud or abuse, to protect rights and safety, to investigate security incidents, or in connection with a business transfer, restructuring, financing, acquisition, or formation of a successor entity.

10. Security

Alvera uses commercially reasonable administrative, technical, and operational safeguards designed to protect information processed by the Service. These may include role-based access controls, multi-factor authentication for certain contexts, private storage buckets, signed access workflows, upload scanning, export governance, evaluator restrictions, audit logging, and legal hold mechanisms.

No system can be guaranteed to be perfectly secure.

11. Retention

Alvera retains information for as long as reasonably necessary for business, operational, security, legal, evidentiary, backup, and compliance purposes. Certain records, including legal acceptance records, audit logs, export events, upload scanning records, and security events, may be preserved for evidentiary, security, or legal hold purposes.

12. Customer Responsibilities

Customer is responsible for obtaining required notices, consents, rights, and permissions for information submitted to the Service and for configuring workspace roles, access controls, exports, invitations, and integrations appropriately.

13. Business Transfers

Information may be transferred to Alvera LLC or another successor entity associated with the Service, or in connection with financing, restructuring, merger, acquisition, sale of assets, or similar transaction.

14. Changes to this Policy

Alvera may update this Privacy Policy from time to time. Updated versions will be identified by version and effective date.

15. Contact

Questions regarding this Privacy Policy may be directed to Sean.dotts@gmail.com.