Privacy
What Eurobase needs to run accounts, deploys, security, support, and billing.
Eurobase is operated by Giovanni Liber as a Polish sole proprietorship.
Operator
Eurobase is a product operated by Giovanni Liber, an individual business registered in Poland. Registered address: Solec 24 lok. 199, 00-403 Warszawa, Poland. NIP: 7011185691. EU VAT: PL7011185691. REGON: 527526866.
The operator controls account, authentication, support, security, platform usage, and billing data. Privacy contact: privacy@eurobase.dev. Support and general contact: support@eurobase.dev.
Customer content
For code, files, deployment artifacts, logs, and application data inside customer workloads, Eurobase acts as a processor for the customer.
Data
- Account, email, login provider, organization, and role data.
- When you sign in with Google or GitHub: the provider account identifier, email address and whether the provider verified it, your GitHub username, and your profile picture link. Eurobase does not receive your provider password.
- Session, CSRF, security, audit, and request data.
- GitHub, repository, branch, commit, webhook, and deploy metadata.
- Project, runtime, storage, log, usage, quota, and health data.
- Support, invoice, tax, payment status, and cancellation data when billing is active.
- Sign-up and sign-in attempt counts per network address and per email address, kept only as keyed hashes, with counting periods of at most one day, then removed by scheduled cleanup; cleanup can be delayed by a backlog or failure; during unusually heavy traffic from one network the browser may be asked to perform a short computation before continuing.
Basis
- Contract (GDPR Article 6(1)(b)): account creation and service delivery where the individual is a party to the contract.
- Legal obligation (Article 6(1)(c)): applicable Polish tax, invoice, accounting, and statutory duties.
- Legitimate interest (Article 6(1)(f)): managing business customer contacts, service security, abuse and fraud prevention, reliability, debugging, audit logs, and support, subject to necessity and the individual's rights.
- Consent: optional marketing, optional analytics, or optional cookies only when Eurobase asks for GDPR consent.
Retention
The table describes current retention controls and their limits. A legal minimum is different from an automatic deletion date. Some records currently have no automatic age-based deletion; this does not authorize keeping personal data indefinitely. Aggregated totals linked to an account or project are not anonymous. For customer workload data, including visitor logs, Eurobase follows the customer's instructions under the DPA; the customer determines its own legal basis.
| Data class | Period or trigger | Deletion and aggregation | Legal basis |
|---|---|---|---|
| Invoices, payments and billed usage totals | Polish tax records: until the tax liability limitation period expires, normally five years from the end of the calendar year when tax payment was due; suspension or interruption can extend it. Where the Accounting Act applies, books and ordinary accounting evidence: at least five years from the start of the year after the financial year concerned. | Invoice and billing records are retained separately from visitor logs. Monthly usage totals currently have no automatic age-based deletion. There is no automatic purge at the end of the statutory period. | Article 6(1)(c) for required accounting and tax evidence; 6(1)(b) or 6(1)(f) for service usage and billing administration. |
| Raw usage records and delivery receipts | No general automatic age limit currently applies to per-request or per-invocation usage and receipt records. | Usage is aggregated for reporting and reconciliation. Aggregation does not erase the source records or the receipts needed to prevent duplicate accounting. No general 90-day deletion is implemented. | Article 6(1)(b) or 6(1)(f) for metering, reconciliation and billing integrity; DPA instructions for customer personal data. |
| Project access logs, including IP, location and request path | Eligible for cleanup thirty days after ingestion; volume cleanup keeps at most 10,000 rows per project in each log category and can remove older rows sooner. | Deleting a log removes its attached payload, including stored IP and location details. Rows still needed for telemetry aggregation wait for that processing. Backlogs or cleanup failures can delay deletion beyond thirty days. This window does not cover separate security evidence or provider copies. | Customer instructions under the DPA; Article 6(1)(f) where Eurobase processes necessary evidence for its own security and reliability. |
| Project traffic and activity aggregates | Five-minute buckets: seven days; hourly buckets: 30 days; daily buckets: 180 days, measured from the bucket end. | Scheduled cleanup removes expired buckets in batches and can be delayed. These windows cover project traffic and activity counters; separate container request metrics, provider usage rollups, monthly usage totals and delivery receipts have different retention controls. | Article 6(1)(b) or 6(1)(f) for service reporting and reliability; DPA instructions where applicable. |
| Security, abuse and audit evidence | Ordinary CLI credential audit: eligible for cleanup after 90 days; account-wide authority-revocation audit is excluded and has no automatic age limit. Project enforcement records: after one year from creation, except the record maintaining an active suspension. Other incident and operator audit records have no general automatic age limit. | Cleanup is batched. Active suspension evidence remains while it supports that suspension. Authentication counters become eligible for removal five minutes after their counting window ends. There is no general 180-day incident deletion rule. | Article 6(1)(f) for security, abuse prevention and necessary claims evidence; 6(1)(c) only for a specific applicable legal duty. |
| Account, membership and support data | While the account is in use. Account deletion starts on a confirmed request, rather than after a fixed inactivity period. Support records have no general automatic age limit. | Account deletion first cancels subscriptions immediately, without refunding the current period. Only already-accrued usage may be charged on a final invoice; nothing renews after deletion. If Stripe is unavailable, deletion waits and retries. Shared projects you own or pay for must first be transferred to another member or explicitly deleted, with the project name confirmed and members notified. Account deletion then waits for cleanup of solely owned projects and resources. Failures or unsettled usage can delay completion; projects with other owners remain. Deleting an account does not itself erase every billing, receipt, support or provider record. No fixed completion time is promised. | Article 6(1)(b) or 6(1)(f) for account and support administration; 6(1)(c) for records that must be retained by law. |
| Temporary Gateway delivery spool | Removal after the API has acknowledged the exact records for all required destinations. | Acknowledged records are removed during compaction. Pending or quarantined records remain until delivery or resolution; there is no fixed age limit or promise of immediate removal after acknowledgement. The API copy follows its own retention class above. | Article 6(1)(b) or 6(1)(f) for reliable delivery and accounting integrity; DPA instructions where applicable. |
A specific dispute, incident or legal order can require preserving relevant evidence until that case and any applicable legal period end. It does not extend retention of all visitor logs. Unnecessary personal data remains subject to deletion; contact privacy@eurobase.dev for a request or the applicable reason for retention.
Backup and infrastructure-provider copies have separate lifecycles. No fixed backup expiry or simultaneous erasure from all provider copies is currently confirmed here. Stripe may also retain records under its own legal duties. Invoices submitted to Poland's KSeF are stored there for ten years from the end of the issue year; this period applies to those invoices. For your invoice's KSeF submission status, contact billing@eurobase.dev.
For example, after an access log is removed, the monthly usage total and invoice can still remain. A total does not contain the deleted log's visitor IP, and does not mean that all separate technical evidence has been erased.
Legal references: Polish Accounting Act, Articles 2 and 74; Tax Ordinance, Articles 70 and 86; VAT Act, Articles 112–112aa; GDPR, Articles 5, 6, 13, 17 and 28; UODO retention guidance.
Rights
Account, payment, support, and billing details are required to provide paid service access; optional marketing or analytics data is optional. Eurobase does not use Article 22 automated decisions for account or billing eligibility. Users can request access, correction, deletion, restriction, objection, portability, consent withdrawal, and complaint handling through privacy@eurobase.dev. Users can also complain to the Polish supervisory authority, the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl), or to the supervisory authority of their EU country of residence or work.
Processor terms
For business customers where Eurobase processes customer workload data, the DPA at /legal/dpa provides the processor terms. Accepted customer terms or a signed order control where a business customer needs a binding Article 28 contract.