Loading workspace...
Legal and Contact
This page centralizes the controller details, operating setup, processor map, and privacy entrypoints that keep HackCode running as a live product.
Controller: Michaela Vavrova
Legal form: Sole trader / Slovak trade-license holder (zivnostnik, SZCO)
Place of business: Tehelna 1024/23, 920 01 Hlohovec, Slovakia
IČO: 57 433 917
Trade register no.: 250-62235
Legal and privacy email: hackcode.eu@gmail.com
Public product URL: https://hack-code.net
Hosting region: Self-managed VPS, Amsterdam, Netherlands
AI provider: Google Gemini
Blob storage: Vercel Blob
Email delivery runtime: Mailtrap, Google Gmail SMTP
Payments runtime: Not configured
| Processor | Role | Purpose | Region / transfer note |
|---|---|---|---|
| VDSina | processor | Infrastructure hosting for the public site, application runtime, database, backups, and host-level logs. Data: Account data, demo requests, educational progress data, audit logs, and operational metadata stored on the VPS. | Amsterdam, Netherlands The current deployment VPS is operated through VDSina. A specific hosting region is published only if explicitly confirmed in deployment configuration. Official page |
| Google Gemini | processor | AI generation for course hints, mentor sessions, and challenge autofill routes. Data: Prompt content, challenge/course context, and limited request metadata needed to produce the response. | Europe-region processing The current deployment is configured to use Europe-region processing for Google AI workloads. Any later processor-region change must be reflected in the legal surface before rollout. Official page |
| Vercel Blob | processor | Public object storage for profile avatars and banner uploads. Data: User-uploaded profile images and the public URLs generated for those assets. | Vercel-managed object storage Blob storage is active in the current environment for public asset uploads and delivery. Official page |
| Mailtrap | processor | Transactional email delivery (primary) for invite, demo, and privacy emails. Data: Recipient email address, sender address, message subject, and message body for invite/demo/privacy emails. | Mailtrap-managed infrastructure Configured in the current environment for transactional email delivery. Official page |
| Google Gmail SMTP | processor | Transactional email delivery (fallback) for invite, demo, and privacy emails. Data: Recipient email address, sender address, message subject, and message body for invite/demo/privacy emails. | Google-managed email infrastructure Configured as the active SMTP relay in the current environment; message processing follows Google mail infrastructure locations. Official page |
Use the form below for access, correction, erasure, portability, or objection requests. The request is logged into the privacy operations queue and routed to the legal contact channel.
Use this form for access, erasure, portability, or correction requests. We verify identity before acting on sensitive requests.
Signed-in users can export a JSON package containing core account data, educational profile data, privacy requests, feedback submissions, and recent audit or product events tied to the account.
Sign in first if you want a direct account export. Otherwise use the privacy request form above.