Privacy in DriveTurn.

Development privacy reference — not yet a final real-user policy.

This privacy notice describes the current iOS development implementation of DriveTurn, published by Steffen Aspe under the SABONEX brand. In this notice, references to SABONEX mean Steffen Aspe operating under that brand.

For personal data that the current development setup or support channel actually receives or controls, Steffen Aspe is the data controller as applicable. DriveTurn is not publicly released, and activation with real shared child/family or location-related data remains blocked until retention, deletion and the remaining privacy gates are explicitly approved and verified.

The hosted Shared Transport foundation has been technically tested with synthetic acceptance data. This page must therefore be reviewed again against the final production backend and release candidate before real-family use or public release.

Visits to this page or the wider SABONEX website are covered separately by the SABONEX website privacy notice.

Authenticated identity defines who may access a household.

The current app uses Supabase Auth with email and a one-time code (OTP). The email address is used to deliver the sign-in code; the authenticated user ID and session are used to establish the account identity.

DriveTurn then resolves live household memberships from the backend. Those memberships determine which household workspaces a signed-in user may select and use. Local display names, adult IDs or driver IDs are not treated as authentication or authorization credentials.

On sign-out, visible account-scoped state is cleared before the auth sign-out completes so the previous household is not left visible while a network call is in flight. Sign-out is not the same as account/data deletion.

Structured data is used for specific coordination functions.

The current development model can process structured information such as:

• Household identity, name and adult membership — used to define the family workspace and access boundary.
• Child first names or limited share labels — used to identify the children involved in the user's own household activities and bounded coordination views.
• Activities, timing and recurrence — used to represent recurring family activities and concrete occurrences.
• Participation and transport needs — used to represent whether a ride is needed for a particular direction/occurrence.
• Driver commitments, capacity and passenger allocation — used to determine coverage and show the relevant driver/passenger plan.

Unactivated/private work can remain account- and household-scoped on the device. Once a supported activity or transport state is deliberately activated as shared, the Supabase backend becomes authoritative for that shared state and the local copy serves as bounded cache/offline support.

Connection does not mean unrestricted family access.

DriveTurn's current privacy rule is minimum structured disclosure: only information needed for the concrete coordination task may leave the device or be projected to another household.

Household membership, a connection between households and disclosure for a specific transport need are separate authorization boundaries. A connection does not automatically expose complete child lists, household rosters, private notes or full calendars.

Shared feeds and share cards are bounded projections. Server authorization is based on the authenticated Supabase user and live household membership. Invitation and connection flows require explicit actions, and one-time invitation secrets are stored server-side as hashes after creation.

Address-book uploads, live GPS tracking, route history, broad behavioural tracking and unrelated family/child data are outside the current default boundary.

Local state is scoped to the signed-in account and household.

DriveTurn stores private local state, cache, migration information and offline support inside the app's iOS container under an account- and household-scoped Application Support structure. Local files carry ownership/context information that is checked before the data is treated as belonging to the current user and household.

When remote shared state is authoritative, the local copy is treated as cache/offline support rather than a competing source of truth. Stale/offline state is surfaced instead of silently treating a failed network request as an empty household.

Protection therefore relies on the app's account/household scoping, backend authorization, iOS app sandboxing and the security of the user's device. These technical boundaries do not replace the still-open real-user retention/deletion requirement.

Supabase provides the current authentication and backend foundation.

The current app uses Supabase and the supabase-swift SDK for authentication and server functions supporting household membership, activities, trusted household connections, bounded sharing, transport needs, requests and driver/passenger state.

The current development OTP setup sends authentication email through a custom Gmail SMTP configuration connected to Supabase. This is a development operations choice and is not yet locked as the final public-release email provider.

Provider regions, subprocessors, international-transfer disclosures and final data-processing arrangements must be reviewed against the actual production configuration before real-family activation. This development notice does not claim that Supabase or email processing occurs in a specific country where that has not been verified for the final production setup.

No live GPS tracking or separate advertising/analytics SDK in the verified app.

The current Xcode configuration has no Core Location/location-permission integration, StoreKit payment flow, advertising SDK, AdSupport integration or separate analytics SDK. DriveTurn does not track live GPS position or route history in the verified implementation.

The product roadmap may later include limited activity-venue information, notifications and a deliberately chosen monetization model, but those future decisions are not presented here as current data handling. Any material change requires a new privacy review.

The final real-user retention/deletion policy is still a release blocker.

The current DriveTurn project explicitly blocks activation with real shared child/location-related data until retention, deletion and any required cleanup/deletion implementation have been defined, approved and verified.

Because that work is not complete, this page does not invent a production retention period or claim a finished account-deletion flow. Current development/local caches and hosted synthetic acceptance data are development artifacts, not a promise about how real user data will be retained after release.

Support correspondence is kept while a matter is active and afterwards only while there is a reasonable need for follow-up, security, documentation, dispute handling or legal obligations. Privacy and deletion questions can be sent to info@sabonex.com.

Rights apply to personal data actually processed in the development/support setup.

For personal data that Steffen Aspe/SABONEX actually holds — for example support correspondence or personal account data used by an authorized development/test account — applicable privacy law may give you rights including access, correction, deletion, restriction, objection and, where applicable, data portability.

Support correspondence is processed to answer the request, troubleshoot the app and keep necessary follow-up or records. Depending on the context, this may be based on steps requested by you or performance of an agreement, legitimate interests in providing and securing support, or a legal obligation.

Questions or requests can be sent to info@sabonex.com. You may also have the right to complain to the competent data protection authority where you live or work, or where an alleged infringement occurred. In Denmark, the supervisory authority is Datatilsynet.

Before public release, DriveTurn still requires a verified product-level retention/deletion flow for real family data; individual privacy requests do not substitute for that unfinished release requirement.

The DriveTurn policy follows the actual development and production data flow.

DriveTurn remains under active development, including the activity-centered product realignment and later V1 slices. This page will be updated when the data model, hosted production configuration, retention/deletion, notifications, payments, analytics, location handling or other material processing changes.

Before real-family TestFlight/pilot or public App Store release, this notice must be reviewed against the final release candidate, the actual hosted production setup and the completed retention/deletion implementation.