EAConnect Planning
EAConnectPlanning
Request Demo Access
← Back to Overview
Last Updated: October 2026

Privacy & Data Protection Policy

EAConnect provides enterprise planning and analytics infrastructure. We treat customer financial, operational, and headcount data with strict tenant isolation, cryptographic encryption, and zero third-party commercial monetization.

1. Information We Collect

When you request demo access, initiate a pilot, or use EAConnect Planning, we process:

  • Account & Contact Credentials: Name, corporate email address, business domain, title, and organization billing details.
  • Enterprise Model Metadata: Dimensional hierarchies, formula scripts, pipeline configurations, and audit timestamps created within the platform.
  • Customer Application Data: Financial actuals, budget lines, and headcount tables loaded via our iPaaS connectors or file imports. This data remains 100% customer property.
  • Technical Telemetry: Aggregate system uptime, calculation engine latency, error logs, and session authentication tokens.

EAConnect Excel Add-in

The EAConnect Excel Add-in (listed in Excel as EAConnect) connects your open workbook to your selected EAConnect Planning workspace to load reports and input forms, refresh data, save report layouts, and submit planning changes.

Data used: The add-in processes your account identity, selected workspace, report and form identifiers, filters, layouts, and the worksheet values needed for these operations. Opening or refreshing content retrieves data from your selected workspace. Saving planning changes sends edited values and their dimension context to that workspace. Saving a report to a folder sends its layout, filters, and sheet configuration.

Workbook access: The add-in requests permission to read and write the open Excel document. It writes report and form data, formatting, and binding metadata into the workbook, including a hidden EAConnect metadata sheet. Workbooks you save or share can therefore contain business data and EAConnect metadata.

Authentication and local storage: Depending on workspace configuration, authentication uses Google Firebase Authentication or an external sign-in service configured by your organization. Firebase processes sign-in credentials and token refresh requests when enabled. The add-in stores account/session information, authentication and refresh tokens, workspace address, and display preferences in browser or Office webview storage; the workspace address may also be stored in Office roaming settings. Signing out clears the add-in's stored session. Workspace and display preferences can remain until changed or the add-in's browser storage is cleared.

Recipients and retention: Data is exchanged with the workspace you select and the authentication services needed to sign in. Microsoft processes workbook storage and sharing under your Microsoft account or organization's settings. Server-side retention follows the applicable workspace policy and customer agreement. Signing out or uninstalling the add-in does not delete workbook contents or data already saved to EAConnect. Contact your workspace administrator or privacy@eaconnect.io for access, correction, or deletion requests.

For help using the add-in, email info@eaconnect.io with the subject “EAConnect Excel Add-in Support”.

2. Strict Tenant Isolation & Security Controls

EAConnect operates dedicated tenant schemas with PostgreSQL row-level security and cryptographically isolated data stores. Customer datasets are never blended, nor are customer financial transactions or proprietary drivers used to train public or multi-tenant machine learning models. All data in transit is protected using TLS 1.3, and all data at rest is encrypted using 256-bit AES keys managed via dedicated KMS.

3. Data Retention & Erasure

Customers retain full administrative control over data retention policies. Upon termination of an agreement or upon written request, all active customer instances, database partitions, and backups are purged within 30 calendar days in compliance with SOC2 and GDPR requirements.

4. Subprocessors & Hosting Architecture

EAConnect infrastructure is hosted within secure tier-4 data centers (AWS and Google Cloud Platform) situated in the United States and the European Union based on customer region preference. We maintain formal Data Processing Agreements (DPAs) with all underlying cloud hosting vendors.

5. Contact Our Data Protection Officer

For questions regarding compliance, Data Processing Addendums (DPA), or to execute an audit request, please contact our security team at privacy@eaconnect.io or mail to EAConnect Inc., 100 Montgomery St, Suite 1400, San Francisco, CA.

Request Demo Access & Security Review