Enterprisely← Back to Home

Privacy Policy

Last updated: March 13, 2026

1. Scope

Enterprisely is a software platform for collecting business documents, extracting structured ESG data, reviewing evidence, automating selected import workflows, and generating framework-aligned reports. This Privacy Policy explains how we collect, use, store, and disclose information when you use Enterprisely at enterprisely.biz.

2. Information We Collect

2.1 Account and workspace information

When you create or use an account, we collect information such as your name, email address, encrypted password hash, account creation date, and organization identifier used to scope your workspace.

2.2 Company profile and reporting data

You may enter company and ESG reporting information such as company name, legal form, headquarters, industry, contact details, reporting period, workforce metrics, governance disclosures, environmental data, and target-setting information. This information is used to populate dashboards, readiness checks, action plans, and generated reports.

2.3 Uploaded and imported documents

You may upload or import business records such as bills, invoices, receipts, spreadsheets, presentations, and policy files. The current product supports direct uploads for PDF, CSV, XLS/XLSX, DOCX, PNG, JPG/JPEG, and PPTX files. These files are stored in cloud storage and linked to your organization workspace.

2.4 Extracted fields, evidence, and review data

We generate and store structured fields derived from your documents, including values such as vendor names, dates, billing periods, energy usage, costs, currencies, notes, confidence scores, evidence snippets, processing mode labels, and human review or confirmation status.

2.5 Automation and integration data

If you use automation features, we may collect and store portal URLs, optional portal login details, run history, run logs, scheduling settings, and related import metadata. If you connect Google Drive, we may store your connected folder details plus OAuth access and refresh tokens needed to support sync features you enable.

2.6 Technical and service data

We also process technical information needed to operate and secure the service, such as authentication data, request metadata, service logs, rate-limit events, and error diagnostics.

3. How We Use Information

  • To authenticate users, maintain organization-scoped workspaces, and secure access to the platform.
  • To upload, store, index, and retrieve documents and related metadata.
  • To extract structured ESG data from uploaded or imported files and present those results in review workflows.
  • To generate KPI summaries, data-quality indicators, missing-information views, action plans, and report content.
  • To run optional automation features such as portal imports, scheduled imports, and Google Drive sync.
  • To operate exports and reporting features, including PDF and CSV outputs.
  • To debug issues, monitor reliability, prevent abuse, and improve the service.

4. AI Processing

Enterprisely uses AI and document-processing tools to analyze uploaded or imported content and to generate structured outputs. Our current processing stack includes Amazon Bedrock with Nova 2 Lite, plus fallback parsing or OCR paths such as PDF parsing, AWS Textract, Tesseract, and rule-based extraction. We use these tools to extract data, generate evidence-backed outputs, draft reporting text, and support action-plan generation.

We do not use your content to train public-facing models. As with any AI-assisted workflow, outputs may be incomplete or inaccurate and should be reviewed by you before being relied on.

5. Sharing and Service Providers

We do not sell your personal information or your business reporting data. We disclose information only as needed to operate the service or as required by law.

  • AWS for hosting, storage, authentication-related infrastructure, AI processing, OCR, and data persistence.
  • Google if you choose to connect Google Drive for folder-based imports.
  • Other subprocessors or authorities where reasonably necessary for security, legal compliance, or platform operations.

6. Security

  • Passwords for Enterprisely accounts are stored as hashes, not in plain text.
  • Data is transmitted over HTTPS/TLS.
  • We use organization scoping in application logic and storage records to separate customer workspaces.
  • We rely on AWS infrastructure and related cloud controls for storage and service operation.
  • Access to automation features, portal credentials, and Google Drive connections is limited to the relevant organization workspace and depends on the product features you enable.

7. Retention and Deletion

We retain account data, company profile information, documents, extracted outputs, automation settings, and related records for as long as needed to operate your workspace, comply with legal obligations, resolve disputes, and enforce our terms.

  • You can move documents to trash in the product and restore them later.
  • You can permanently delete a document and its associated extracted record only after it has been moved to trash.
  • Disconnecting Google Drive removes the live integration and clears connected-folder settings and stored Drive tokens used for sync.
  • Saved portal settings may remain until you remove them or we delete the workspace data associated with them.

Document deletion in the current product removes the stored file from application storage and deletes the indexed document and extraction records after the trash step. Limited residual copies may still persist for a period in backups or infrastructure logs.

8. Your Choices

  • You may update company profile data and review or correct extracted fields inside the application.
  • You may manage document lifecycle actions available in the Data Entry workflow, including trash, restore, and permanent record deletion after trashing.
  • You may disconnect Google Drive if you no longer want Drive-based syncing.
  • If you need help with a data access, correction, or deletion request that is not available in-product, contact us.

Privacy requests can be sent to privacy@enterprisely.biz.

9. Changes to This Policy

We may update this Privacy Policy as our platform evolves. Material changes will be communicated via email or an in-app notification. Continued use of Enterprisely after changes constitutes acceptance of the updated policy.