This register explains which external services SpeedInn plans to use, why we need them, the information involved, and where to review each provider’s official documentation and legal terms.
Planned · not necessarily active
References reviewed 21 August 2026
01
Infrastructure and data services
DO
Cloud infrastructure
DigitalOcean
Planned purpose
Host SpeedInn application services, private networking, operational storage, backups, and supporting infrastructure selected for production.
Intended data scope
Application traffic, encrypted operational data required by the configured service, infrastructure logs, account and billing metadata.
Boundary
European regions and private-network controls are to be confirmed in the final production architecture. Access must be restricted and logged.
Store persistent application records and the audit metadata needed to operate the SpeedInn service.
Intended data scope
Encrypted workspace, user, reviewed guest-record, retention, and audit fields. Source identity-document images are not intended for the primary database.
Boundary
The cloud provider, region, encryption, network access, backups, and retention must be fixed in the production configuration before activation.
Provide short-lived caching, queues, rate limits, sessions, and coordination state needed for reliable processing.
Intended data scope
Ephemeral identifiers, job state, counters, and short-lived session data. Full guest records and source identity-document images are not intended for Redis Cloud.
Boundary
Values must be minimised, encrypted in transit, access-controlled, and expire automatically. Redis Cloud is not the system of record.
Distribute the Android application, manage releases and store listing information, and complete Google Play’s review and Data safety disclosures.
Intended data scope
Application packages, signing and release metadata, developer-account information, store content, and diagnostics made available through Play Console.
Boundary
Production guest records and source identity-document images are not intended for Google Play. SpeedInn remains responsible for accurate app privacy and SDK disclosures.
Sign and distribute the iOS application through Apple Developer, App Store Connect, and TestFlight, subject to Apple’s review rules.
Intended data scope
Application builds, certificates, identifiers, submission and testing metadata, developer-account information, and store listing content.
Boundary
Production guest records and source identity-document images are not intended for Apple’s developer services. App privacy answers must cover SpeedInn and integrated third parties.
Build and sign mobile applications in the cloud and submit release artifacts to Apple and Google using the selected EAS services.
Intended data scope
Source code, build artifacts and logs, project configuration, app identifiers, environment metadata, and the credentials or API keys required for signing and submission.
Boundary
Production guest records and source identity-document images are not intended for EAS. Credentials must be least-privileged, encrypted, reviewable, and revocable.
