SaveBack

Privacy Policy

Last updated: [DATE]

Overview

SaveBack is a local-first iPhone app that helps users turn a small set of YouTube links into repeatable routines. This Privacy Policy explains what information SaveBack stores on device, what information may be sent to Apple or YouTube-related services to provide core functionality, and what SaveBack does not currently collect for its own backend because no SaveBack backend or account system is part of the MVP.

This draft is written for release preparation. It should be reviewed again before publication, before submitting the final privacy policy URL in App Store Connect, and before turning on any new data practice that is not described here.

Product Scope Covered By This Draft

iPhone app
local-first routine storage
no SaveBack account system
no SaveBack cloud sync
no SaveBack backend for routine storage
optional local reminder notifications
YouTube link import, metadata preview, thumbnails, and playback support

If the product later adds analytics, crash reporting, accounts, syncing, subscriptions, or server-side storage, this policy must be updated before those features are released.

Information Stored On Device

SaveBack stores routine-related information locally on the user's device for app functionality. This may include:

routine names
YouTube video links the user adds to routines
routine item ordering
lightweight completion and progress history
notification preference and reminder time

In the current MVP, SaveBack intends to keep this data on device rather than storing it in a dedicated SaveBack backend.

Information SaveBack Does Not Currently Collect For Its Own Backend

Based on the current MVP implementation and product scope, SaveBack does not currently require users to create an account and does not currently maintain a SaveBack-operated backend for routine data.

SaveBack therefore does not currently intend to collect or retain:

account registration information
profile information
payment information
social graph information
cloud-synced routine libraries
marketing analytics tied to a SaveBack user profile

Functional Network Requests

Although SaveBack is local-first, some app features may still cause network requests to third-party services selected or triggered by the user.

YouTube links, previews, and playback

When a user adds, previews, or plays a YouTube link, SaveBack may send limited request data to YouTube- or Google-operated services in order to resolve metadata, load thumbnails, or render embedded playback.

resolve a video title or preview metadata
retrieve YouTube page metadata
load thumbnails
render embedded YouTube playback

Based on the current codebase, SaveBack appears to use YouTube link parsing plus YouTube page or oEmbed-style metadata requests and an embedded YouTube iframe player flow. As a result, YouTube or Google may receive information such as the requested URL, IP address, device/browser-style request metadata, and other information typically involved in serving web or media content.

SaveBack does not claim ownership of YouTube content. YouTube-related content and services remain subject to YouTube's own terms, policies, and privacy practices.

Apple system services

SaveBack may also rely on Apple system services for local notification scheduling, share sheet handling, and opening external content.

Notifications

If a user enables reminders, SaveBack requests notification permission from iOS. If permission is granted, SaveBack stores reminder settings locally and schedules local notifications using Apple system frameworks.

SaveBack does not require notification permission in order to create or run routines. Notifications are optional.

Support and Feedback

SaveBack exposes a support email inside the app. If a user chooses to send feedback, the user may choose to provide information voluntarily, such as the content of their message, device details they choose to provide, and reply contact information they choose to include.

Third-Party Services

The current MVP may involve Apple platform features and YouTube or Google services for YouTube-linked metadata, thumbnails, or playback resources.

If SaveBack ships with YouTube API Services or other Google developer services in scope, SaveBack should keep a published privacy policy that clearly describes those uses and should also link users to the relevant Google and YouTube legal materials required by those services.

Data Sharing

In the current MVP, SaveBack does not intend to share routine data with a SaveBack-operated backend because no such backend is planned.

However, data may still be transmitted to third-party services when necessary to provide requested functionality, such as loading YouTube-linked metadata or playback, using Apple platform services, or sending a support email chosen by the user.

Data Retention

For SaveBack-controlled MVP data, routine and reminder data generally remain on the device until the user edits or deletes it in the app, removes the app and its local data, or platform-level storage behavior removes the data.

Children's Privacy

SaveBack is not designed as a children's app. If the intended audience changes, this policy should be reviewed again against applicable child privacy requirements and any platform-specific obligations.

Changes to This Policy

SaveBack may update this Privacy Policy as the app changes. Any material change to data handling, third-party integrations, or contact channels should be reflected in the published Privacy Policy before that change is released.

Contact

Support email: superwedge.labs@gmail.com