LEGAL · PRIVACY

Privacy Policy

Last updated: September 28, 2026

This Policy explains how Averidi handles information through its website, customer accounts, ordering system, project workspaces, support functions and business data and analytics services.

1. Information we collect

Depending on how you use Averidi, information can include your name, email address, optional company and contact details, account and verification information, order and questionnaire responses, project descriptions, requested deadlines, uploaded files, project messages, revision requests, support messages, invoices, payment and subscription status, notifications and records associated with service delivery.

Authentication and security systems also process information needed to protect accounts and services, including session records and information used for rate limiting and request security.

2. Business and project data

Files, datasets and other information supplied for an order are used to review and deliver that project, communicate about it, produce agreed deliverables and provide related support. Uploaded files are associated with the relevant order and access to project information is controlled through customer account or secure order access.

Project data may itself contain information about other individuals. Customers are responsible for ensuring that they are permitted to provide that information for the requested work. Averidi treats non-public customer project data as confidential and uses it for the project and related service operations rather than treating it as public information.

Averidi Analyst is a standalone subscription. Subscribers may upload supported business-data files or use an authenticated live source without ordering another Averidi service. Analyst preserves the supplied source, creates a protected analytical copy, profiles data quality, applies bounded safe normalization and infers analytical field roles automatically. Material preparation and semantic decisions are recorded with the dataset version.

3. Accounts, authentication and cookies

Averidi uses cookies necessary for signed-in sessions and secure order access. Current session and order-access cookies are HTTP-only, use SameSite protections and are configured for secure transmission in production. They can remain valid for up to 30 days unless they expire or are cleared earlier.

Password credentials are stored as password hashes rather than readable passwords. Verification and password-reset processes use time-limited token records.

4. Orders, project workspaces and communications

Order records can include selected services, prices, project information, questionnaire responses, uploaded files, messages, deliverables, revisions and project status. Order Chat and Support messages are stored so the relevant request or project can be handled and its history maintained.

Averidi may send transactional email relating to account verification, password reset, orders, payments, project notifications and support. The current application uses an email-delivery provider to send these messages.

5. Payments and subscriptions

Stripe processes one-time payments and recurring subscription checkout. Averidi sends information needed to create the checkout, such as the customer email, order or service description, amount, currency and internal order or subscription identifiers. Stripe sends payment and subscription status events back to Averidi so orders, invoices, payment records and subscriptions can be updated.

Payment-card details are handled through Stripe's payment process rather than stored as card numbers in the Averidi application.

6. Website analytics

Averidi currently records first-party website analytics events to understand use of the site. For page views, this can include the page path, referring page, UTM source, medium and campaign values, and a grouped traffic-source label. When a visitor is signed in, an analytics event may be associated with that customer account.

The current page-view implementation sends these analytics records to Averidi's own application rather than loading a third-party advertising tracker for that purpose.

7. How we use information

Information is used to create and secure accounts; create, administer and deliver orders; review and analyze project data; provide deliverables; process and reconcile payment status; operate recurring services; communicate with customers; respond to support requests; maintain service and security records; understand website use; prevent abuse; and operate and improve Averidi's services.

8. Averidi Analyst and automated analytics processing

Averidi Analyst uses Averidi's deterministic analytics and modeling code to prepare supported business data, plan bounded analytical operations, calculate results and preserve supporting evidence. Verified business calculations are not delegated to a hosted language-model provider.

The current Analyst architecture does not require a paid or metered hosted AI API. An optional self-hosted language model running within Averidi's controlled environment may assist with interpretation of ordinary analytical questions. Its proposed analytical plan is validated against approved dataset fields and supported operations before Averidi code performs the calculation. The language layer is not permitted to execute arbitrary code, SQL, filesystem operations or unrestricted tools.

Analyst can also create deterministic month-over-month comparisons and customer-configured KPI threshold alerts from approved metrics. Alert triggering is performed by Averidi's calculation logic rather than delegated to the AI model. Customers may save verified Analyst answers and may opt into scheduled monthly summaries. When email delivery is enabled for a summary or an alert fires, the relevant summary or alert text is sent through Averidi's configured transactional email provider.

Advanced Analyst can derive forecasts, scenario outputs, statistical anomaly evidence and bounded predictive-model evaluations from approved customer data. Forecasts and anomaly records retain the source-version lineage used to calculate them and are removed when a retained source version in that lineage is removed. Predictive-model evaluations are bound to their approved dataset version and are removed with that version.

Customers may create an authenticated inbound Analyst webhook. Averidi stores only a one-way hash of the webhook secret. Each delivery is treated as a complete dataset snapshot, stored within the subscriber's protected Analyst workspace and passed through the same autonomous preparation and semantic-reconciliation controls as a manual upload. Schema changes are recorded rather than routed to a human reviewer.

9. When information is shared

Customer project data is not sold, published or disclosed to unrelated third parties. Information may be processed by service providers where necessary to operate Averidi securely and deliver the service—for example, Stripe for payment processing and the configured email-delivery provider for transactional email—subject to appropriate safeguards where applicable. The current Analyst architecture does not require customer project data to be sent to a hosted language-model provider; any optional language-model assistance described above is self-hosted within Averidi's controlled environment. Information may also be disclosed where required by law, to protect the rights or security of Averidi or others, or as part of a legitimate business reorganization subject to appropriate safeguards.

Averidi does not make customer project files public merely because they are uploaded for a project. Published Example Work on the site is identified as fictional and uses synthetic data.

10. Storage and security

The application uses access controls for accounts and orders, hashed passwords and session tokens, same-origin checks on sensitive requests, rate limiting for selected actions, file-type and file-size validation, and audit or operational records for parts of the service. Uploaded project files are stored in the configured Averidi upload storage and linked to the relevant order.

No online system can guarantee absolute security. Customers should avoid submitting information that is unnecessary for the agreed project and should contact Support if they suspect unauthorized access.

11. Retention and deletion

For a completed or cancelled one-time project, retained project files, project attachments and retained deliverable files are normally kept in active project storage for 90 days after the project closes and are then deleted through Averidi's retention process. For Monthly Analytics, data files for a delivered monthly cycle are normally deleted after the same 90-day period. Standalone Averidi Analyst workspace data is normally scheduled for deletion 90 days after the Analyst subscription ends unless the subscription is reactivated before deletion. Analyst source files, prepared copies and derived workspace records are covered by that standalone lifecycle.

The 90-day period is the standard project-data schedule. A different period may apply where required by law, reasonably necessary for an unresolved matter, or agreed with the customer. A customer may request earlier deletion after a project is completed or cancelled. Averidi reviews the request before carrying it out, and where necessary the automatic deletion schedule can be placed on an auditable hold or rescheduled with a recorded reason.

Deleting project files does not mean that every record connected with the customer or transaction is deleted. Order records, invoices, payment records, contracts or confidentiality records, consent records, audit and security records, support records and similar business records follow separate retention periods based on accounting, security, dispute-handling, contractual and legal needs. NDA records and signed NDA PDFs are treated as contractual/confidentiality records rather than project-data files and therefore are not automatically deleted on the 90-day project-data schedule.

12. Privacy requests and choices

You may contact Averidi to ask about personal information associated with you, request correction or deletion, or raise another privacy concern. Available rights can vary according to where you live and the law that applies. Averidi will assess requests under applicable requirements and may need to verify the requester's identity before acting.

13. International use

Averidi is an online service and customers may access it from different locations. Service providers and systems involved in operating the service may process information in locations different from your own. Where applicable law requires safeguards for an international transfer, the appropriate requirements must be followed.

14. Children's privacy

Averidi is a business data and analytics service and is not directed to children. Do not create an account or submit personal information through the service if you are not legally able to use the service.

15. Third-party services and links

The website may direct you to third-party services such as a payment provider. Their handling of information is governed by their own privacy practices when information is processed independently by them.

16. Changes to this Policy

This Policy may be updated as Averidi's services, systems or legal requirements change. The current version will be published on this page with its updated date.

17. Contact

Use the Support page for privacy questions, access, correction or deletion requests, or concerns about project information. See the Terms of Service for the contractual rules governing use of Averidi.