Saltar al contenido principal
Tropixus
Legal document

Privacy policy

This policy describes how Tropixus collects, uses and protects your personal data in accordance with the General Data Protection Regulation (GDPR), the German Federal Data Protection Act (BDSG) and the German Telecommunications and Telemedia Data Protection Act (TTDSG).

Last updated: 2026-11-15· 2 reading time: min

This is an automated translation. The legally binding version is the Spanish one. If you require an official translation, please contact us at .

In summary

Your data belongs to you

We collect only what we genuinely need, store everything on EU servers (Frankfurt), never sell it, and you can request a copy or delete your account at any time from Account > Privacy or by emailing legal@tropixus.com.
1

Data controller

Eduardo Arturo Sieber Artiles<br/>Heubnerweg 9, 14059 Berlin, Germany<br/>Email: legal@tropixus.com

Given the current size of the project, we are not required to appoint a Data Protection Officer (DPO) under Art. 37 GDPR. For any privacy matter, please write to the address above.

2

Categories of data we process

We collect the following data depending on the activity:

  • Registration/login data: first name, surname, email address, password (hashed, never in plain text), country and postcode. This data is stored in the backend database and in Keycloak (identity manager). Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
  • Authentication data: HttpOnly session token (secure cookie), temporary OTP codes for the password recovery process. Legal basis: Art. 6(1)(b) GDPR + Art. 6(1)(f) (account security).
  • Rate limiting: to protect login, registration, OTP delivery and password reset forms against automated or brute-force attempts, we count attempts per IP address (and, where applicable, per email address) over short time windows (5–60 minutes). The counters are reset when the window expires. Legal basis: Art. 6.1.f GDPR (legitimate interest in account security).
  • Favourites and reminders: the businesses and events you save, and your preference for pre-event notifications. Legal basis: Art. 6.1.b GDPR.
  • Reports and feedback messages: the text you send via the “Something wrong?” button or the contact / help / for businesses forms, along with your email address (if provided) and the URL from which you are writing. Legal basis: Art. 6.1.f GDPR (legitimate interest in improving the service).
  • Website brief materials (plans with a website and Socio Digital): the logo, photos and texts you upload so we can build your website or your featured profile (style, colours, services, opening hours, domain and the details for your legal notice), change and migration requests for your website (with their attached images) and, if you cancel your plan, the reason you give us. Files are stored privately: they have no public link and only the team building your website sees them. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
  • Publication and claim requests (businesses and events): the data you send when you publish or claim a business or event: details of the business or event (name, description, contact, images), your stated role (owner, manager or authorised person) and the proof of ownership you provide (links, text or documents). They are used solely to review and verify the request. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
  • Technical browsing data: URL visited, browser type, language, city selected in the selector, date and time. Legal basis: Art. 6.1.f GDPR (legitimate interest in keeping the platform operational and secure).
  • Cookie consent record: accepted banner version, date and permitted categories. Legal basis: Art. 7.1 GDPR (burden of proof) + § 25 TTDSG.
  • Analytical cookies: anonymous identifiers served by Google Analytics 4 and Microsoft Clarity, only if you give your express consent via the banner. Legal basis: Art. 6(1)(a) GDPR + § 25(1) TTDSG. We do not currently use marketing or advertising cookies; the category exists in the banner but does not load any cookies at present; it is reserved for future campaigns and, should we activate them, they will only be loaded with your consent.
  • Location (mobile app only, optional): if you grant the location permission, the app sends your coordinates to our server for the sole purpose of detecting the nearest city and showing you relevant content. We do not build a location history and do not link coordinates to your account. You can deny the permission and keep using the app normally by picking a city manually. Legal basis: Art. 6.1.a GDPR (consent, given through the operating system permission).
  • Push notification token (mobile app only): a device identifier generated by Firebase Cloud Messaging (Google), required to deliver event notifications. It is stored against your account and removed when you delete your account. Legal basis: Art. 6.1.a GDPR (consent, given when you enable notifications).
  • Profile photo (optional): the image you upload from your gallery or camera. It is stored on Cloudflare R2 and you can replace it at any time. Legal basis: Art. 6.1.b GDPR (performance of the contract).
  • Log of actions in your business account: when you manage businesses or events (publish, claim, edit, take online or offline, delete, resend or cancel a request), we record which action you took, on which listing or request, the listing data you changed, and the date and time. We do not store your IP address, your browser, your proof of ownership or your notes to the team. Purpose: preventing abuse and being able to show who changed what on a listing. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in abuse prevention and accountability). If you delete your account, the log is pseudonymised (shown as “Deleted user”).
3

Purposes of the processing

  • Operate and maintain the platform and the mobile app.
  • Customise content according to your city and language.
  • Respond to your requests and reports via the feedback form.
  • Comply with legal obligations (invoicing, tax withholding, responses to authorities).
  • Improve the product using aggregated analytics (only with your consent).
  • Manage subscriptions to the paid plans for businesses (sign-up, payment, invoices, changes and cancellations). Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(c) GDPR (tax and accounting obligations).
  • Prevent abuse and keep changes to businesses and events traceable (action log). Legal basis: Art. 6(1)(f) GDPR.
4

Recipients and international transfers

We share data only with data processors acting on our instructions (Article 28 of the GDPR):

  • Vercel Inc., web hosting, Frankfurt region (EU). Hosts the platform and maintains technical access logs.
  • Keycloak, identity system (self-hosted in the EU). Stores account credentials, tokens and sessions.
  • Neon / PostgreSQL, backend database (EU). Stores profiles, favourites, reminders and feedback reports.
  • Resend, transactional email delivery (password recovery OTPs, confirmations). European infrastructure.
  • Hostinger International Ltd., mailbox for hola@tropixus.com (EU). Stores the emails you send us and our replies.
  • IONOS SE, IONOS AI Model Hub (Germany), only to prepare reply drafts to messages you send us, when our team requests it for a specific message. Receives your name, the subject and the message text (never your email address) and does not keep it. Every reply is reviewed and sent by a person.
  • DeepL SE, machine translation of editorial content into German and English (EU). Does not process users’ personal data, only public text from the site.
  • Anthropic, PBC, generation of editorial content for city pages (H1 headings, FAQs and SEO descriptions) using the Claude model (US). We do not send personal data to Anthropic, only the city name and prompt templates defined by us. The transfer is carried out under the European Commission’s Standard Contractual Clauses (Art. 46 GDPR).
  • Upstash, Inc., a Redis database used to control abusive attempts against the login, registration and password recovery forms (rate limiting). It processes, for short periods (5–60 minutes), an identifier derived from your IP address and, where applicable, a hash of your email address, solely for the purpose of counting attempts. Servers in the EU (Frankfurt). Legal basis: Art. 6.1.f GDPR (legitimate interest in protecting user accounts).
  • OpenStreetMap / CartoDB, map tiles in list and detail views (EU).
  • Microsoft Clarity and Google Analytics 4, web analytics (US). These are only activated if you accept analytics cookies via the banner. The transfer is carried out under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).
  • Umami Software, Inc. (US, cloud.umami.is service), aggregated analytics with no cookies or browser fingerprint. No consent required (§ 25(2) TTDSG). Transfer under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).
  • Sentry (Functional Software, Inc., US), monitoring of unhandled errors and slow transactions. Receives only the error stack trace and the URL (no bodies, headers or cookies); session replays are activated only with your analytics consent and mask all text and form inputs by default. Transfer under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).
  • Better Stack, Inc. (US), centralised server logs and uptime monitoring. Receives only server-side events with no PII in cleartext (user identifiers are passed through an FNV-1a hash before leaving our infrastructure). Transfer under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).
  • Google Ireland Limited / Google LLC, Firebase Cloud Messaging service, used exclusively to deliver the mobile app’s push notifications. It receives the device push token and the notification content; we do not send your name, email or location. The transfer to the US is made under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).
  • Cloudflare, Inc., object storage (R2) for business and event images and profile photos and — in a private area with no public link — for the logos, photos and files of your website brief. Transfer under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).
  • Stripe Payments Europe, Ltd. (Dublin, Ireland), payment processing for the paid plans for businesses (Socio Digital, online shop, website on our own hosting). Stripe receives the billing details you enter on its payment page (name or company name, address, NIF/VAT ID, email and card or account details); Tropixus never sees or stores your card details. We only send Stripe an internal customer identifier. Stripe may transfer data to Stripe, Inc. (USA); the transfer is made under the EU-US Data Privacy Framework + Standard Contractual Clauses (Art. 46 GDPR).

We do not sell personal data or share it with advertisers outside the service. We do not currently work with any marketing or advertising providers (e.g. retargeting pixels); should we do so in the future, we would add this here and it would only be activated with your express consent.

5

Retention periods

  • Account data: whilst the account is active, plus 12 months after closure for legal and security purposes.
  • OTPs and session tokens: 15 minutes (OTP) and up to 30 days (session).
  • Favourites and reminders: until you delete them or close your account.
  • Server/access logs: 30 days.
  • Feedback reports: 12 months, then anonymised (the content of the report is retained without being linked to a user).
  • Consent records: 3 years (burden of proof, Art. 7.1 GDPR).
  • Push notification token: until you delete your account or uninstall the app.
  • Profile photo: until you replace it or delete your account.
  • Location coordinates: used at query time to resolve the nearest city; they may appear in technical server logs, which are deleted after 30 days.
  • Subscription and billing data (paid plans): for as long as the subscription lasts; invoices and accounting records are kept for 10 years under § 257 HGB and § 147 AO, even if you delete your account.
  • Log of actions in your business account: 24 months, then deleted automatically. If you delete your account earlier, it is pseudonymised.
  • Website brief materials (logo, photos, attachments): files you never use in a brief, request or draft are deleted automatically after 30 days; the rest are kept while your plan runs and your website is being built, and always deleted when you delete your account.
6

Safety measures

  • Session stored in an HttpOnly + Secure cookie (not accessible from JavaScript) signed in JWE format.
  • Security HTTP headers: HSTS, CSP with per-request nonce, COOP / CORP, restrictive Permissions-Policy.
  • Passwords stored using bcrypt hashing in Keycloak, never in plain text.
  • End-to-end encrypted traffic using TLS 1.3.
  • Database access restricted to the backend VPC; no public internet access.
7

Your rights as a data subject

You have the following rights:

  • Access (Art. 15 GDPR): to obtain a copy of your data.
  • Rectification (Art. 16 GDPR): to have inaccurate data corrected.
  • Erasure (Art. 17 GDPR — "right to be forgotten"): to have your account and associated data deleted.
  • Portability (Art. 20 GDPR): to receive your data in a machine-readable format.
  • Objection (Art. 21 GDPR): to object to processing carried out on the basis of legitimate interest.
  • Restriction (Art. 18 GDPR): to restrict processing while a dispute is being resolved.

To exercise any of these rights, write to us at legal@tropixus.com. We respond within 30 days at the latest. You can also change your cookie preferences and download or delete your data at any time from Account > Privacy.

8

Right to lodge a complaint

You have the right to lodge a complaint with the relevant supervisory authority: the Berlin Commissioner for Data Protection and Freedom of Information (Friedrichstr. 219, 10969 Berlin) or the supervisory authority in the federal state where you live.

Do you have any questions about this document? Please email us at legal@tropixus.com or visit the contact form.