Skip to main content
DriveByCloud
Version privacy-draft-v1

Privacy Notice

This draft explains the information the planned v1 website handles for inquiries, test-store orders, protected downloads, and local administration. It requires legal and deployment review before publication.

Legal review required

DRAFT — LEGAL REVIEW REQUIRED BEFORE ANY PUBLIC OR PRODUCTION USE.

1. Controller

The planned controller is DriveByCloud Kft, Műegyetem rakpart, BME J building, 5th floor, Office 514, 1111 Budapest, Hungary.

[LEGAL REVIEW TODO: confirm the controller’s registered details and add the required privacy contact channel.]

2. Information handled

The site is designed to handle contact details and inquiry text submitted through the contact form; buyer and order details supplied during test checkout; license acceptance; order and payment-state references returned by Stripe; download records; and limited technical information used for security and rate limiting.

  • Contact form: name, email, optional company, message, consent, and anti-abuse fields.
  • Test store: selected packages, license version and acceptance, buyer details, order state, and Stripe references.
  • Protected downloads: order-item reference, time, and minimal privacy-preserving client metadata.
  • Administration: authentication and security events needed to protect the local admin area.

3. Why information is handled

The intended purposes are to respond to inquiries, operate the test-mode checkout, confirm entitlement, provide protected synthetic downloads, maintain security, and demonstrate local administrative workflows.

[LEGAL REVIEW TODO: assign and document the lawful basis for each purpose, including any legitimate-interest assessment.]

4. Service providers and recipients

Stripe is intended to process test-mode checkout information. An email provider receives inquiry details only when optional SMTP delivery is configured. Hosting and infrastructure providers may process limited data when the site is deployed.

[LEGAL REVIEW TODO: confirm all processors, data locations, transfer safeguards, and processor notices for the actual deployment.]

5. Retention and security

The application is designed to persist inquiries, orders, status events, and download records locally and to protect administrative and download access with authentication or signed tokens.

[LEGAL REVIEW TODO: approve concrete retention periods, deletion routines, security disclosures, and incident contacts.]

6. Rights and complaints

Depending on applicable law, individuals may have rights concerning access, correction, deletion, restriction, objection, portability, and complaints to a supervisory authority.

[LEGAL REVIEW TODO: add verified request instructions, response details, and the competent supervisory authority.]

7. Cookies and browser storage

The planned v1 site uses browser storage for the cart and an HTTP-only cookie for local admin sessions. No advertising or third-party analytics integration is included in the implementation plan.

[LEGAL AND DEPLOYMENT REVIEW TODO: verify the final cookie and tracking inventory before publication.]