Privacy Notice
Invoance provides neutral cryptographic proof and verification infrastructure for businesses. This Privacy Notice explains what information Invoance collects, how it is used, and what choices you have when you access our website or use our services.
This notice applies to visitors to the Invoance website, registered users and tenants of the Invoance platform, and individuals whose records or events are processed through Invoance as part of a verification or proof workflow.
Because Invoance is infrastructure and not a consumer product, the information it processes is primarily technical and organizational in nature. Invoance is designed to minimize the collection of personal data while maximising the integrity and verifiability of business event records.
Information we collect
The information Invoance collects depends on how you interact with the platform. We collect only what is necessary to operate, secure, and provide our services.
When you create or manage an account, we collect information such as your name, email address, organization name, and authentication credentials. This information is used to identify your tenant, manage access, and communicate service-critical updates.
When events are anchored through Invoance, we record associated metadata including timestamps, cryptographic hashes (SHA-256), Ed25519 signatures, event identifiers, and tenant references. This metadata constitutes the ledger entry and is necessary for proof generation and verification.
When you verify your organization's domain via DNS TXT record, we record the verified domain and associated tenant relationship. This is used to establish organizational legitimacy for issued proofs.
We collect IP addresses, device and browser information, API request logs, and diagnostic data as necessary for security monitoring, abuse prevention, and reliability. This data is retained only as long as operationally required.
If you contact Invoance via support, inquiry forms, or email, we retain those communications in order to respond and, where necessary, to maintain a record of the interaction.
What we do not collect
Invoance is not a consumer product and does not require sensitive personal data to operate. The following categories of data are explicitly outside the scope of what Invoance collects:
Invoance does not collect national identity numbers, passport numbers, tax identification numbers, or similar government-issued identifiers.
Invoance does not collect fingerprints, facial recognition data, voice prints, or any other biometric identifiers.
Invoance does not collect payment card numbers, bank account numbers, or financial account credentials. Billing is handled by a third-party payment processor.
Invoance does not collect health records, medical history, or any data classified as protected health information under applicable law.
Unless you explicitly enable optional document storage, Invoance does not store the original contents of submitted documents or event payloads. Only the cryptographic fingerprint is retained as the source of truth.
Invoance does not use advertising trackers, behavioral profiling, or cross-site tracking technologies. No data is sold to or shared with advertisers or data brokers.
How we use information
Information collected by Invoance is used exclusively to provide and operate the proof infrastructure service. Invoance does not use data for advertising, profiling, or any purpose unrelated to the delivery and security of the service.
To provide, operate, and maintain the Invoance event anchoring, signing, and verification infrastructure.
To generate, store, and expose cryptographic proof records in an append-only ledger that preserves the integrity of all anchored events.
To monitor for unauthorized access, detect and prevent fraud, and protect the security and reliability of the platform.
To manage tenant accounts, domain verifications, API credentials, and billing relationships.
To respond to inquiries, support requests, and service-critical notifications.
To comply with applicable laws, respond to valid legal processes, and fulfill contractual obligations.
Event ledger and immutability
The core function of Invoance is maintaining an append-only, tamper-evident ledger of anchored business events. This design is intentional and has direct privacy implications that you should understand before using the service.
Once a ledger entry is created, it cannot be modified, redacted, or deleted. This immutability is a foundational property of the system and is what enables cryptographic proof to function. Any metadata recorded as part of a ledger entry — including timestamps, hashes, tenant identifiers, and event references — is retained for the duration of your plan's retention period and cannot be removed earlier.
Before anchoring events that may include personal data in their metadata, you should assess your obligations under applicable data protection laws including GDPR, and ensure that immutable retention is consistent with your legitimate purpose and legal basis for processing. Invoance is infrastructure and does not make this determination on your behalf.
Document retention
Invoance stores a cryptographic fingerprint (SHA-256 hash) of every submitted event by default. This fingerprint is the source of truth for verification and is sufficient to independently prove that a specific document or payload existed, unchanged, at a specific point in time.
Storage of the original document or event payload is an optional feature available on eligible plans. When enabled, the original content is retained for retrieval convenience and is not required for verification. Verification always resolves against the cryptographic fingerprint, not the stored document.
If original document storage is not enabled, Invoance does not receive, process, or retain the underlying content of submitted events. The submitting party is responsible for maintaining custody of original documents and making them available when verification is required.
Your rights
Depending on your location and applicable law, you may have rights in relation to personal data that Invoance holds about you. These may include the right to access, correct, or delete personal data, or to object to or restrict certain processing.
Some rights may be limited in the context of Invoance's services. In particular, ledger entries are immutable by design and cannot be altered or deleted in response to a data subject request where doing so would undermine the integrity of the proof record. Where this conflict arises, Invoance will explain the limitation and assist you in identifying alternative measures where possible.
To exercise any applicable rights, contact Invoance via the contact page. We will respond within the timeframe required by applicable law.
Security
Invoance implements technical and organizational security measures designed to protect information against unauthorized access, loss, misuse, or alteration. These include cryptographic signing of all ledger entries, append-only database enforcement, multi-tenant isolation, and access controls.
Security measures are applied by design and are not optional features. The cryptographic guarantees that protect proof records — SHA-256 hashing, Ed25519 signatures, and Merkle tree aggregation — also protect the integrity of any associated metadata.
No system can be guaranteed to be completely secure. In the event of a security incident affecting personal data, Invoance will respond in accordance with applicable legal requirements and notify affected parties as required by law.
Changes to this notice
Invoance may update this Privacy Notice from time to time to reflect changes in the law, the services, or our data practices. Material changes will be reflected by updating the date below and, where required by applicable law, providing additional notice to affected users.
Your continued use of Invoance after a revised notice is posted constitutes acceptance of the updated terms. If you do not agree with a material change, you should discontinue use of the services and contact Invoance regarding the handling of your data.