Home/Privacy Policy
LEGAL DOCUMENTATION & DATA PROTECTION

Privacy Policy

Effective Date: October 23, 2026
Last Updated: October 23, 2026
Status: MVP Operational Release
++
Transparency & Pre-Publication Notice

This Privacy Policy reflects the actual technical implementation and data-handling architecture of the MyLedgerLens platform as of October 23, 2026. Certain administrative identity placeholders (such as registered commercial entity name and registered office address) are marked for pre-launch confirmation prior to formal corporate incorporation.

1. Introduction & Scope

MyLedgerLens ("we", "us", or "our") provides an AI-native business document intelligence and verification platform. The service is designed specifically for business-to-business (B2B) operations—including distributors, wholesalers, accounting firms, and commercial enterprises—processing incoming supplier invoices, receipts, and associated paperwork.

This Privacy Policy explains how MyLedgerLens collects, processes, stores, and protects information when authorized users access our public website, register for an account, create workspaces, upload invoice documents, and utilize our verification and export workflows.

Target Audience: MyLedgerLens is intended exclusively for commercial entities and business representatives acting on behalf of an enterprise. It is not directed to consumers or individuals acting for personal, family, or household purposes, nor is it directed to children under 18 years of age.

2. Information We Collect

We limit data collection to the categories necessary to operate our document verification platform. We collect information directly when provided by users or generated through system operations:

A. Account & Authentication Information (Required)

To access the application, create workspaces, or process documents, users must create an account.

  • Email address
  • Encrypted password credentials (managed securely via Supabase Auth; raw passwords are never visible to or stored by MyLedgerLens)
  • Assigned internal user UUID and email confirmation status
  • Authentication session tokens and login timestamps

B. Workspace & Membership Information (Required)

Information required to organize multi-tenant data boundaries and assign permissions.

  • Workspace name and unique workspace identifier (UUID)
  • Workspace membership associations and user role designations (owner, admin, member, reviewer)
  • Workspace creation and modification timestamps

C. Uploaded Invoice Documents (User-Provided)

Commercial files uploaded by authorized workspace members for extraction and verification.

  • Original document binary content (PDF, PNG, or JPEG formats up to 20MB)
  • File metadata: original file name, MIME type, file size in bytes, and magic-byte header validation record
  • Storage path scoped to the active workspace: {workspace_id}/{document_id}.{ext}

D. Extracted Invoice Fields & Derived Records (Application-Generated)

Structured data extracted via AI vision and deterministic parsers from uploaded documents.

  • Supplier details: trading name, legal address, tax identifier (VAT / TIN / EIN)
  • Buyer details: customer name, billing address, purchase order number
  • Invoice metadata: invoice reference number, issue date, due date, payment terms, currency code
  • Financial figures: subtotal, applied tax rate, calculated tax amount, discounts, shipping fees, grand total
  • Line-item records: description, unit quantity, unit price, line total, and verification flag
  • Extraction metadata: confidence ratings (high, medium, review), estimated bounding-box percentages, and extractor provider ID

E. Human Corrections, Review Actions & Lifecycle Decisions

Decisions made by human reviewers in the review console.

  • Manual field adjustments and correction overrides saved by reviewers
  • Approval certifications and rejection decisions (including optional rejection reasons)
  • Deterministic validation issue flags (arithmetic discrepancies, missing mandatory fields, date inconsistencies, duplicate invoice warnings)

F. Append-Only Audit Trail Records

Immutable event log maintained in PostgreSQL for organizational governance and accountability.

  • Lifecycle event types: processing_queued, processing_started, extraction_completed, validation_failed, field_corrected, approved, rejected, exported
  • Associated timestamps, actor UUIDs, previous/new status values, and event payload details

G. Technical Diagnostics & Operational Logs

Standard technical logs generated when interacting with serverless API functions and application endpoints.

  • Serverless execution logs (HTTP method, route, sanitized status code, duration)
  • Sanitized client error logs (database error codes such as PostgreSQL / PGRST are stripped to protect infrastructure details)

3. How Information Is Used

MyLedgerLens uses the collected information strictly for operational and functional purposes to deliver our core B2B invoice intelligence service:

  • Document Extraction: Converting unstructured document images and PDFs into structured financial fields.
  • Deterministic Arithmetic & Rule Verification: Mathematically verifying line-item totals (quantity × unit price), reconciling subtotals against line sums, and validating grand totals with a strict 0.02 rounding tolerance.
  • Duplicate Invoice Detection: Comparing extracted invoice numbers and normalized supplier legal names against existing records in your active workspace to alert reviewers to duplicate billing.
  • Human Review & Field Corrections: Displaying side-by-side document views with bounding-box highlights to assist human reviewers in inspecting and correcting values.
  • Workflow Progression & Audit Governance: Progressing documents through the deterministic state machine (uploaded → queued → processing → review_required → approved / rejected) and recording an unalterable history of actions.
  • Secure CSV Exports: Producing formula-injection-sanitized CSV files containing approved invoice records for export to accounting software.
  • Platform Security: Authenticating users, enforcing workspace multi-tenant Row Level Security boundaries, and rejecting spoofed or oversized files.
  • Customer Support: Diagnosing service issues and responding to direct inquiries sent to support@myledgerlens.com.
Explicit Negative Assurances:

MyLedgerLens does not sell, rent, or trade customer documents, financial records, or personal data. We do not use uploaded documents or extracted invoice data to train public foundation models or third-party artificial intelligence engines. We do not run third-party advertising networks, behavioral profiling, or cross-site tracking scripts.

4. AI Extraction & Third-Party Processors

To provide multimodal visual extraction, database storage, and hosting, MyLedgerLens utilizes established cloud infrastructure providers:

Google Gemini Multimodal Vision API (Google Cloud / Google AI)

AI Extraction Engine

Role: When an authorized user requests invoice processing, the document image or PDF is transmitted server-side via encrypted HTTPS to Google Gemini (gemini-2.5-flash) using structured multimodal vision prompts.

Data Handling Disclosures: Invoices contain commercial and financial data. When processed via the Gemini API, document content is transmitted to Google's infrastructure. Google processes requests under Google Cloud and Google AI Studio API Terms of Service. Enterprise API tiers generally stipulate that user inputs are not used to train Google models; however, customers should review Google's published developer terms. MyLedgerLens cannot independently guarantee that upstream providers do not maintain transient security or diagnostic logs.

Offline / Heuristic Fallback: If the external Gemini API is unreachable, unconfigured, or encounters an upstream timeout, MyLedgerLens utilizes a local, deterministic server-side heuristic fallback extractor (server_heuristic_v1) that processes documents locally without communicating with external AI services.

Supabase Inc.

Database, Auth & Private Storage

Role: Supabase provides managed PostgreSQL database infrastructure, Supabase Auth user management, and private encrypted object storage (invoices bucket). Data is stored in isolated multi-tenant relational tables protected by PostgreSQL Row Level Security (RLS).

Vercel Inc.

Hosting & Serverless Functions

Role: Vercel hosts the static React Single Page Application and executes stateless serverless API functions (POST /api/documents/:id/process, GET /api/workspaces/:id/export-csv, GET /api/health). Serverless functions process incoming requests ephemerally and do not persist customer files on local function disks.

5. Storage, Security & Data Retention

We implement defense-in-depth technical and operational safeguards verified within our production architecture:

  • Private Storage Bucket: The invoices storage bucket is configured with public = false. Files cannot be accessed via public URLs.
  • Time-Limited Signed URLs: Document previews in the human review console are served exclusively via short-lived signed URLs (default duration: 3,600 seconds / 1 hour) generated dynamically for authenticated members.
  • Server-Side Secret Isolation: Privileged credentials (SUPABASE_SERVICE_ROLE_KEY, GEMINI_API_KEY) are stored exclusively in serverless environment variables and are never bundled into client browser code.
  • File Signature & Magic-Byte Verification: Uploads undergo client-side and server-side magic-byte inspection (%PDF-, PNG, JPEG SOI) to reject disguised executable files or file extension spoofing.
  • Formula Injection Sanitization: CSV exports automatically prepend an apostrophe to cells beginning with formula triggers (=, +, -, @, \t, \r) to safeguard spreadsheet users from formula execution.

Data Retention & Deletion Behavior

To maintain accuracy and auditability, we describe our actual implemented retention behavior:

Continuous Storage:Uploaded documents, structured extractions, and validation records remain stored in your workspace until an authorized user requests their deletion or until the workspace is decommissioned.
No Automated Deletion Timers:The platform currently does not run automated deletion timers or scheduled time-to-live (TTL) expiration routines. Records persist until manually purged.
Immutable Audit Trail:Records in invoice_audit_events are append-only. The database schema strictly prohibits UPDATE and DELETE operations to preserve a verifiable record of accounting approvals and lifecycle actions.
Current Deletion Capabilities:While database Row Level Security policies permit document deletions, the current frontend MVP user interface does not yet expose a self-service "Delete Document" or "Delete Account" button. Account or document removal requests must be submitted directly to our support team at support@myledgerlens.com for manual administrative fulfillment.

6. Multi-Tenant Workspace Isolation

MyLedgerLens employs a centralized multi-tenant architecture where organizational data is isolated by workspace:

  • Every document, extraction record, validation issue, and audit event belongs to a designated workspace_id.
  • Database queries are restricted at the PostgreSQL engine level via Row Level Security (RLS) policies. Users cannot view, query, update, or export records belonging to workspaces where they do not hold active membership.
  • Storage access is validated via PostgreSQL security definer functions (storage_workspace_id) that parse the storage path prefix and verify the caller's membership before permitting file download or upload.
  • Serverless API processing endpoints independently verify the caller's JWT authentication token and confirm active workspace membership before initiating document extraction.

7. Your Data Rights & Regulatory Compliance

Depending on the jurisdiction where your business operates, you may have specific statutory rights regarding personal data:

  • Right of Access & Portability: You can view all processed documents, extractions, and audit records within your workspace, and export approved invoices to CSV at any time.
  • Right to Rectification: Reviewers can correct any extracted invoice field, supplier information, or line item directly via the Human Review Console prior to approval.
  • Right to Erasure (Deletion): You may request the deletion of your account, workspace, or uploaded documents by contacting support@myledgerlens.com.
Applicable Data Protection Frameworks & Legal Flag

MyLedgerLens seeks to adhere to core data-protection principles under the Nigeria Data Protection Act 2023 (NDPA), as well as international principles of purpose limitation, storage minimization, and data accuracy. Formal registration with national data protection authorities (such as the Nigeria Data Protection Commission - NDPC) and appointment of an external Data Protection Officer (DPO) will be completed upon corporate entity incorporation.

*Pre-launch note: Prospective enterprise customers requiring customized Data Processing Agreements (DPAs) or Standard Contractual Clauses (SCCs) may contact support@myledgerlens.com.

8. Policy Updates & Contact Information

We may revise this Privacy Policy periodically to reflect enhancements in application functionality, third-party provider updates, or changes in regulatory obligations. Any material modifications will be posted to this page with an updated "Last Updated" date. Because the current MVP does not operate an automated broadcast email system, we encourage users to review this page periodically.

Privacy Inquiries & Data Protection Contact

For questions regarding this policy, data subject requests, or privacy compliance, please contact:

Project: MyLedgerLens
Lead Developer / Product Owner: David Osili
Legal Entity Name: [LEGAL_ENTITY_NAME — Pending Pre-Launch Incorporation]
Registered Office Address: [LEGAL_BUSINESS_ADDRESS — Pending Pre-Launch Confirmation]