ENTITY account privacy notice Version: early-access-pending-20261118-v1 Reviewed: 2026-11-18 These documents cover free early-access registration held in pending access. Registration records your interest; it does not activate ENTITY services, an API entitlement, a paid plan or a usable workspace. **Who is responsible** Sustema AG, Sihlquai 125, 8005 Zurich, Switzerland, is responsible for the processing described here. Contact privacy@sustema.io about your information, withdrawal or rights. This notice covers creating and managing an ENTITY pending account and recording a request for service availability. Website browsing and any later activated service have their own applicable notices. **Information and purposes** We use your email address, its verification status and the sign-in provider's account identifier to establish and recognise your account. The identity service processes credentials and security information needed for verification, sign-in, multifactor authentication and recovery. The ENTITY application receives identity claims and does not need your identity-service password. We record the pending-account identifier and status, your availability-notification request, registration and account timestamps, and the versions of the terms and privacy notice presented when you registered. We keep the acceptance record and transaction references needed to explain that registration. Our identity provider records IP addresses, browser and device identifiers, language, authentication times and security events. Our application keeps account, transaction and session identifiers and timestamps; the inspected pending-account tables do not store separate IP-address or browser-profile fields. The email provider processes recipient, message and delivery information. Open and link tracking were previously enabled for account emails. We disabled both default settings on 15 November 2026. Earlier tracking records may remain. Individual messages can override these defaults, so we do not claim that these settings alone prevent all email tracking. We do not treat tracking as necessary merely because an email concerns your account. We use necessary session and security storage to maintain sign-in and protect requests. The supplier information below distinguishes verified settings from remaining uncertainties; it does not permit adding advertising trackers. We use this information to provide the pending account you requested; send necessary account and availability messages; respond to support and rights requests; protect the service; and prevent a closed account or withdrawn notification request being restored by an old backup or repeated request. We do not use the availability request as consent for general marketing or sell it as a marketing list. Pending registration does not require payment-card information, a company profile or uploaded customer datasets. **Legal grounds where the GDPR applies** For information objectively necessary to provide the pending-account registration and related messages you request, the basis for processing objectively necessary for this registration is performance of the registration contract. This does not cover unrelated processing merely because it appears in the terms. For proportionate security, investigating abuse, handling disputes and preventing restoration of a closed account, the basis for this processing is our legitimate interests in protecting accounts and respecting withdrawal. We assess necessity, alternatives and the effect on you, including the length of retention and the ability to request human review. This does not treat all provider collection or retention as necessary for the registration contract. Where a specific legal obligation requires a particular record, we retain only what that obligation requires. We do not claim that law requires the general 90-day period below. Optional marketing, if offered separately in future, requires its own applicable basis and choice. Declining it will not prevent pending registration. **Who receives information and where** Authorised Sustema personnel and contracted suppliers receive information needed for their tasks. Our identity service, auth.sustema.io, is hosted in Switzerland on Zitadel Cloud. Our application runs on AWS in Frankfurt, Germany, and its database is hosted by Neon in the same region. Postmark handles account email in the United States. We do not claim that support, telemetry, subprocessors or every copy of your information stays in Switzerland or Germany. **Supplier information** Application logs are encrypted and configured for seven-day retention. Load-balancer access, connection and health-check log exports are disabled. The retention setting does not establish when every backup or other copy is erased. Identity — Zitadel Cloud. Our identity service is hosted in Switzerland. CAOS AG in Switzerland is the contracting party for Zitadel’s self-service Cloud service; its US parent is Zitadel, Inc. The standard Cloud terms incorporate a data-processing agreement covering processing across the group and standard contractual clauses, including Swiss provisions, for relevant international transfers. Zitadel’s published subprocessor list identifies Google Cloud Platform for Cloud infrastructure and optional US providers Postmark for email and Twilio for SMS. Our configured email route uses Postmark. The list alone does not establish that our account uses Twilio, and Swiss hosting does not mean every support activity, recipient or copy remains in Switzerland. Zitadel subprocessor list (https://trust.zitadel.com/subprocessors). The published DPA permits personal-data retention until that DPA ends, subject to its processing instructions and rights-request provisions. Closing an ENTITY pending account does not establish that the identity-provider agreement has ended. Identity deletion prevents further authentication while a deletion audit record can remain; an ongoing historical-event or backup-erasure schedule for this installation is not verified. We will assess an individual closure or deletion request without deleting a shared identity used by other applications automatically. Published log-retrieval limits do not establish when underlying identity events are erased. Zitadel terms (https://zitadel.com/docs/legal/terms-of-service), DPA (https://zitadel.com/docs/legal/data-processing-agreement). Database — Neon, part of Databricks. The published standard platform terms identify Databricks, Inc. and incorporate its master agreement and DPA. Our selected database region is Frankfurt. The supplier also uses infrastructure and support subprocessors beyond that region. The database's point-in-time recovery window is currently one day. Separately, Neon documents recovery of a deleted project for seven days. Neither period describes every export, support record or other copy. Neon terms (https://neon.com/platform-terms), project recovery (https://neon.com/docs/manage/projects#recover-a-deleted-project). Account email — Postmark / AC PM LLC. Postmark processes email through US infrastructure. The account has 45-day activity retention selected and reports indefinite statistics retention. Postmark states that message content and metadata are removed after 45 days under its standard setting. It retains bounced, complained-about and unsubscribed addresses indefinitely in suppression lists to prevent unwanted delivery. Backups and archival copies remain subject to the applicable agreement and rights-request process; we do not claim that the activity window proves deletion of every copy. Open and link tracking defaults were disabled on 15 November 2026. Earlier tracking records may remain, and individual messages can override the defaults. Postmark's published DPAs are incorporated into its terms, with different versions for customer signup cohorts. Postmark DPA (https://postmarkapp.com/dpa), processing locations (https://postmarkapp.com/eu-privacy). We may disclose information when a binding legal requirement applies or where necessary and lawful to protect rights. The standard supplier agreements described above include contractual safeguards for international transfers. Zitadel’s data-processing agreement includes standard contractual clauses and Swiss provisions for relevant transfers. You can ask us for information about the safeguards used for your data at privacy@sustema.io. We do not rely here on a claim of independently verified Data Privacy Framework certification. **How long information is kept** Your pending registration remains active for up to 180 days from creation, unless you withdraw or make a separately explained transition to an available service. Signing in does not restart the period, and registration does not renew automatically. We review the programme and send an expiry notice at least 14 days before closure at the end of the registration period. Registration is free and does not promise a service launch date or admission. When we retire the pending registration, we suppress availability notifications, revoke its sessions and remove the email address from the application principal record. This does not itself delete the identity-service account, email-provider records or backups; those are handled through the supplier-specific process. The policy provides a 90-day restricted period after retirement for the remaining application identity, interest and acceptance records, to resolve closure errors and questions about the registration. Disposal takes place after that period and after any longer verified backup or recovery horizon and necessary documented hold have ended. These are disposal conditions, not a promise that every provider copy disappears on day 90. The supplier information above distinguishes the known periods from unverified provider-copy criteria. We do not dispose of these records while they are still needed to prevent restoration from a permitted backup or replay. Sign-in transaction records become eligible for cleanup 20 minutes after creation, and application session records after 24 hours. Scheduled maintenance removes eligible records, except where a justified hold applies. These are eligibility times, not promises of deletion at that exact moment, and they do not extend how long you can use a session. A separate restricted record survives application-record disposal. It contains the identity issuer and subject identifier, an internal account identifier, closure reason and timestamps, and evidence references needed to prevent resurrection of the closed account. These identifiers remain personal data. This record is not used to send availability messages or reactivate the account. We review its necessity at least every 30 days, considering remaining restore and replay routes, misuse risks, legal holds and whether safe removal is possible. There is currently no automatic removal or re-registration mechanism. If you request deletion or challenge retention, a person reviews the need and available safe action; we do not promise complete erasure or immediate re-registration. A technical inability to delete does not, by itself, justify keeping information indefinitely. Postmark currently has a 45-day activity-retention setting selected and states that statistics are kept indefinitely. The 45-day setting is not a verified deadline for deletion of every provider copy; provider-copy deletion propagation remains unverified; suppression retention is described above. Email suppressions, operational logs, identity records and backups have the distinct periods, criteria and limits described above. Anonymous statistics may be kept longer only if they no longer identify you; we do not assume that all supplier aggregates are anonymous. **Your choices and rights** You can withdraw the availability request or ask to close the pending account at privacy@sustema.io. Without the information necessary to verify and maintain the account, we cannot provide pending registration; public documentation can still be read without registration. Depending on applicable law, you can request access, correction, deletion, restriction or portability, and object to processing based on legitimate interests. If processing relies on consent, you can withdraw it without affecting earlier lawful processing. We may verify your identity proportionately before acting. If we cannot comply fully, we explain the reason and any continuing retention. Account and security rules can refuse a request automatically, including expired or withdrawn registrations. Contact us for human review rather than creating another identity to bypass a restriction. You may complain to the Swiss Federal Data Protection and Information Commissioner or, where applicable, your local data-protection authority. **Changes and scope** We will keep the notice accessible before registration and explain material changes. A new purpose or longer registration period is not inferred from continued sign-in. The supplier information above is part of this notice. Registration is limited to pending access; any later activated service has separate applicable information and access conditions.