Website and application separated
Information website on web-01 at Contabo; personal correspondence through Hetzner Mail. Forms, the app and automated delivery are not yet released.
Trust
Security posture, documented.
How operations, data processing and passport verification are organised. Confirmed facts, existing functions and pending operational checks are distinguished.
Information reviewed 13 October 2026 · office@stoicera.com
Executive summary
Current position ahead of the free beta.
Purpose-based data use
Accounts, journey plans, preferences and inquiries require personal data. Information without names is not automatically anonymous.
Traceable calculations
The passport signs a saved calculation record. That alone establishes neither completed travel nor avoided emissions.
Verification through Farleda
Existing signature checks use Farleda’s server. Independent public-key verification and partner evidence are development targets.
Operational evidence
Deletion cycles, recovery, access controls and external data flows must be verified against actual operation.
At a glance
The short answer for every risk review.
Operator
Raphael Lugmayr & Sebastian Kern GesbR · Stoicera Group
Infrastructure
Website: Contabo. Email contact: Hetzner Mail. App and form operations require separate release.
Authentication
Magic-link sign-in. Delivery, expiry and single use require production verification.
Passport
Signed planning record; currently HMAC and server-side verification.
Transport security
Prepared website CSP and proxy controls; production acceptance remains separate.
Connections and storage
Transport security, stored data, backup protection and access controls are documented from the production setup; no unverified encryption certification.
Source code alone does not establish production configuration.
Authentication
Prepared product sign-in. Reading the website creates no app session.
Accounts and abuse prevention
Necessary sessions and rate limits support the service. IP addresses and technical identifiers may be processed.
Data model
Website submissions are separate from future app accounts, journeys and safety reports.
| Data category | Purpose | Contains PII? |
|---|---|---|
| Website submission | Contact details, inquiry content, consent and delivery status | personal |
| Account | Email, sessions and authentication data | personal |
| Journey | Routes, dates, preferences and content | may be personal |
| Safety report | Report, participants and handling | personal |
| Public metrics | Aggregated planning estimates | review aggregation separately |
Shared passports contain journey information. Account deletion and retention of safety reports or backups require separate treatment.
Website providers
A service is not automatically a processor. Roles, fields transferred and enabled features require a processing-specific assessment.
| Service | Region | Purpose | Data sent |
|---|---|---|---|
| Contabo | Contabo network in Germany; contract and location details held by the operator | Static website delivery on web-01 | Technical connection data; no form database |
| Hetzner Mail | Confirm plan, storage location and retention in the account | Personal mailboxes and inbound correspondence | Sender, recipient, content, attachments and delivery metadata |
This excerpt covers the planned website services. The complete inventory separates app integrations, direct browser requests, provider roles and configuration status.
Data protection and your rights
Rights, responsibilities and implementation scope.
Rights and contact
Access, rectification, erasure, restriction, portability, objection and withdrawal apply subject to statutory conditions. Contact office@stoicera.com; complaints may be made to the competent authority.
Retention
Concrete deletion cycles and exceptions are defined and tested per data category. This page does not certify that deletion jobs already run.
Cookies
Technical functions and optional processing explained separately.
Necessary and optional features
Sign-in sessions are necessary for accounts. Optional analytics, email tracking and external embeds are assessed before activation.
Incident response
How incidents are handled. Operational responsibilities, escalation and status updates must be confirmed before release.
- Reports are assessed, access secured and necessary containment measures taken.
- Notification duties under GDPR Articles 33 and 34 are assessed for the incident; where required, the authority is notified without undue delay and, where feasible, within 72 hours of awareness.
- Causes, measures and communications are documented without a blanket promise to publish personal incident details.
Release status
Manually maintained information about release and availability.
Free beta is planned for 31 October–31 December 2026. Public status must reflect actual availability; a date is not a technical release approval.
How we stay afloat without selling you
Current funding and the planned commercial model.
Beta
Free through the end of 2026. Stoicera currently covers operating costs.
Partners
Rail and infrastructure companies: scoped pilots, with pricing and any subsequent licence credit in the individual offer.
What will never happen
- Selling your data. To anyone. Ever.
- Ads, retargeting pixels, behavioural profiling.
- Commissions from short-haul flights or petrol-car rentals — we refuse those partnerships.
- Pre-ticked newsletter consent. Optional updates require a separate opt-in.
A FlexCo and a separate environment/transport software association are planned; the current operator is the GesbR.
Jurisdiction
Operator, responsibilities and data processing.
Contracting entity
Raphael Lugmayr & Sebastian Kern GesbR, Allerheiligen im Mühlkreis 7, 4320 Allerheiligen im Mühlkreis, Austria. UID ATU79668824.
See the security overview for implementation and release checks. Report vulnerabilities through security@farleda.eu; until that mailbox is confirmed, use office@stoicera.com.
Keep reading
