Privacy Notice

Operator

This Privacy Policy applies to Evidentia, operated by L-ark Inc.

Contact and operator

For privacy, security, legal, or operator questions during Open Beta, use the Contact page as the primary contact path.

Data we may store

• Account and workspace information, such as name, email address, company name, organization membership, and authentication metadata.
• Proof metadata, including event hashes, signatures, timestamps, proof identifiers, verification URLs, anchoring metadata, status, usage records, and related operational metadata.
• API logs and security logs needed to operate, debug, protect, rate limit, and monitor the service.
• Session cookies and authentication cookies needed for login, account security, and application access.
• Contact form submissions, including name, work email, company, plan interest, use case, and message content.

Analytics and telemetry

Evidentia may use analytics and telemetry to understand usage, detect abuse, monitor operations, and improve the product during Open Beta.

• Usage analytics may help us understand which pages, workflows, and product areas are used.
• Telemetry may help with abuse detection, rate-limit tuning, reliability monitoring, debugging, and product improvement.
• We aim to minimize unnecessary tracking and data collection wherever reasonably possible.

Data we are designed not to store by default

Evidentia is designed to avoid storing raw AI data by default.

• Evidentia does not intentionally store raw prompts or outputs by default unless explicitly submitted by the customer.
• For Open Beta, customers are encouraged to submit hashes, summaries, and metadata instead of raw prompts, outputs, personal data, or confidential information unless explicitly intended.
• Customers should keep original AI prompts, outputs, business context, and internal logs inside their own systems unless they deliberately choose to submit them.

Third-party services

Evidentia may use third-party services to operate the product, protect access, process payments or payment readiness, and deliver communications.

• Cloudflare Turnstile or equivalent anti-abuse tooling may be used to verify signup, login, and inquiry requests.
• Stripe may be used for billing infrastructure, checkout readiness, customer records, and webhook processing, even when paid plans are not enabled during Open Beta.
• Email or SMTP providers may be used to deliver contact form submissions and service communications.
• Blockchain networks, including Solana mainnet during Open Beta limited activation, may be used for anchoring metadata.

Customer responsibility

• Customers are responsible for lawful data handling, governance policies, regulatory obligations, internal controls, audit preparation, and data retention decisions.
• Customers are responsible for ensuring they have legal authorization to process and disclose submitted data.
• Customers should not submit personal data, confidential business data, raw prompts, or raw outputs unless they have intentionally decided to do so and have the right to do so.