Privacy Policy

1. Who is responsible for data processing

The controller responsible for data processing in connection with the CorvusLLM public website, order handling, support, and related operational services is the operator identified on the Legal Notice page.

2. Contact details for privacy-related requests

If you have questions about this Privacy Policy, want to exercise a data protection right, or need clarification about a specific order-related data point, you can contact CorvusLLM using the privacy contact route.

3. What data is collected

CorvusLLM collects only the categories of data needed to operate the site, accept orders, deliver digital access, protect the service, and answer support requests. The exact data processed depends on what you do on the site.

• Contact data such as your order email address and any support contact information you provide.
• Order data such as product selection, order number, purchase timestamp, and quoted payment amount.
• Transaction-assignment data such as destination wallet, blockchain transaction hash, confirmation state, and matched payment amount.
• Optional account data such as connected Google or GitHub identity details, verified email addresses, session records, and account security activity when you use the portal.
• Technical request data such as IP address, user agent, page requests, timestamps, and error or abuse-prevention logs.
• Support communication content if you contact CorvusLLM through Telegram, email, or another listed support route.

4. How data is collected

Data is collected in several different ways depending on the action involved. Some information is provided directly by you, some is created by technical operation of the site, and some is generated when a payment needs to be matched to an order.

Payment assignment data can also come from infrastructure used to observe incoming blockchain transfers for order matching.

5. Why data is processed

CorvusLLM processes personal data only for operational purposes connected to the service. These purposes include site delivery, fraud and abuse prevention, order handling, payment assignment, delivery of access information, support, troubleshooting, and record-keeping where needed.

• To render and protect the public website and checkout flow.
• To create, identify, and fulfill an order.
• To confirm that a blockchain payment belongs to the correct order.
• To send delivery information and order-related messages.
• To answer support or legal questions.
• To maintain security, debug failures, and protect the service from misuse.

6. Legal bases

Where European data protection law applies, CorvusLLM generally relies on the following legal bases depending on the context:

• Contract performance and pre-contract measures for handling orders, assignment of payment, and delivery of access information.
• Legitimate interests for website security, fraud prevention, abuse controls, technical monitoring, and reliable operation of the service.
• Legal obligations where retention, accounting, or compliance duties apply.

If a processing purpose would require a different legal basis in a specific case, CorvusLLM aims to use the basis that actually matches the situation rather than making broad unsupported compliance claims.

7. Order, support, and communication data

When you place an order, CorvusLLM processes the order email, product choice, payment asset, quoted amount, order number, and delivery status. This information is necessary to fulfill the order and provide support if something goes wrong.

If you later claim an order or create a portal account, CorvusLLM also processes the linking information needed to connect that guest purchase to your user account. This can include a one-time claim token, a magic-link sign-in email, account session data, and connected-provider metadata.

If you contact support, CorvusLLM also processes the contents of that conversation so the issue can be understood and resolved. Support messages may contain technical details, screenshots, order numbers, or transaction hashes that help identify the request.

8. Technical, log, and access data

Like most hosted services, CorvusLLM and its infrastructure providers can process technical request and access data when the site is loaded or when the public checkout and API routes are used. This can include IP address, timestamp, user agent, referring page, response status, route accessed, and similar operational information.

These logs are used for delivery of the service, performance monitoring, abuse resistance, debugging, and security review. They are not described here as a promise of perfect observability, and they are not intended to support advertising profiles.

9. Cookies, sessions, and browser storage

The public site is primarily built around static pages, checkout interaction, and technically necessary browser-side state. CorvusLLM mainly relies on technically necessary storage behavior for page delivery, limited checkout recovery behavior, and secure account-session handling when a user chooses to sign in.

• The public checkout does not intentionally store API keys in browser storage.
• The public checkout avoids storing full sensitive order objects unnecessarily.
• Short-lived session-related state can still exist where needed to keep checkout recovery usable.
• The optional customer portal uses secure session handling so signed-in users can view orders, deliveries, and security activity.

This page does not claim that the service is entirely storage-free. It states the practical design goal: use only the browser-side state that is necessary for the experience and avoid storing unnecessary secrets client-side.

10. Hosting, infrastructure, and auth providers

CorvusLLM uses third-party infrastructure to operate the public site and related service components. Based on the current site setup, this can include providers used for public hosting, dashboard or API hosting, database operation, payment monitoring, support or communication routing, and optional sign-in providers.

• Public site hosting and CDN delivery
• External dashboard or API hosting where applicable
• Database hosting and storage
• Payment monitoring and assignment infrastructure
• Optional authentication providers such as Google and GitHub when you choose to sign in that way
• Email or messaging infrastructure for support and delivery communications

These providers may process technical metadata on CorvusLLM's behalf to perform their role.

11. Payment monitoring, portal, and service tools

Because payments are made in cryptocurrency, CorvusLLM processes the blockchain transaction information needed to match a payment to an order. Blockchain transactions are inherently public on their respective networks, so some transaction details may be visible independently of CorvusLLM.

CorvusLLM only needs the data required to determine whether a payment was sent to the correct destination address, for the correct order amount, and with the confirmation state required for the service.

Where you use the optional customer portal, CorvusLLM also uses service tooling needed to manage delivered access, show order and delivery history, record session and security events, and send account-related emails such as claim links or sign-in links.

12. Data sharing and recipients

CorvusLLM does not describe itself as a broad data-sharing business. Personal data is shared only where needed to operate the service, fulfill orders, communicate with you, or comply with legal obligations.

• Infrastructure and hosting providers involved in the operation of the site or backend.
• Payment monitoring or email delivery providers used to complete operational tasks.
• Professional advisers or authorities where legally required or reasonably necessary.

CorvusLLM does not claim that data is never touched by any third-party processor. The accurate statement is narrower: data is shared only where service operation actually requires it.

13. International transfers

Some infrastructure providers may operate in or use systems located outside the country in which you access the service. Where this happens, transfer mechanisms and contractual safeguards depend on the provider and the legal situation at the time of transfer.

CorvusLLM aims to use providers that offer an adequate level of protection or appropriate contractual safeguards where needed, but this page does not claim blanket geographic localization that the current distributed infrastructure does not support.

14. Retention and deletion

CorvusLLM keeps data only for as long as it is needed for the relevant purpose, such as fulfillment, support, security review, abuse prevention, or legal retention duties. Different categories can have different retention periods.

• Order and billing-related records may be kept longer where legally necessary.
• Support records may be kept while an issue is active or while follow-up remains reasonably necessary.
• Operational and technical logs are typically kept only as long as needed for security, debugging, and service integrity.

15. Your rights

Subject to the applicable legal conditions, you may have the right to request access, rectification, deletion, restriction of processing, data portability, or objection to certain processing. The exact scope of these rights depends on the law that applies in your case.

If you want to exercise a right, contact CorvusLLM using the privacy contact address and include enough information for the request to be identified and processed.

16. Complaint route

If you believe that your data protection rights have been violated, you may have the right to lodge a complaint with a competent supervisory authority. This can include the authority in your place of residence, place of work, or the place where the controller is established, depending on the applicable legal framework.

CorvusLLM encourages users to contact the privacy route first so issues can often be clarified quickly, but this does not remove any complaint right that may exist under applicable law.

17. Security summary and limits of security claims

CorvusLLM uses technical and organizational measures that are intended to reduce unauthorized access, misuse, and accidental disclosure. These measures can include scoped infrastructure access, monitoring, defensive configuration, and operational checks.

This page does not promise perfect security, zero risk, or formal certification unless explicitly stated elsewhere. Security work reduces risk; it does not eliminate it completely.

18. Business, sensitive, or regulated data warning

The public site and its products are not positioned as a specialized environment for highly sensitive, medical, legal, regulated, or classified information. If your workflow involves special-category personal data, regulated records, or material business secrets, you should evaluate whether the service is appropriate before using it for that purpose.

As a practical rule, do not send more sensitive information to support or checkout than is actually required to solve the issue or fulfill the order.

19. Changes to this Privacy Policy

CorvusLLM may update this Privacy Policy when the service setup, legal context, data flows, or providers change. The version published on this page is the current reference version for the public site.