Prelaunch information · reviewed October 6, 2026. Public app launch is pending; no effective date has been set.

RoutineArc privacy policy

Who is responsible

RoutineArc LLC, registered in Hawaii, United States, provides RoutineArc. Johan Andres Uribe operates the service. Contact us about privacy, your information, or support at routine.arc@gmail.com.

RoutineArc helps adults create routines and record workouts. Our initial service is intended for English-speaking people aged 18 or older in the United States. The upcoming app will ask you to confirm eligibility before sign-in without asking for your date of birth. If you believe a child has provided personal information, contact us so we can investigate and address it.

Information and purposes

• Account information: sign-in provider identifiers, email when supplied by the provider or by you, an optional display name, account settings, and session records. We use this to create and secure your account, connect sign-in methods, and respond to account requests. Your provider may supply a relay email address.
• Routines and workouts: routine descriptions and exercise plans, sets, repetitions, exercise loads, timers, workout progress, and history. We store and synchronize this information to provide your library and workout features. Text you choose to enter may reveal health information. Avoid including medical records or information about other people.
• Routine generation: your description, equipment, experience, and requested duration, generated routine content, and processing metadata. We use these to produce and validate a requested routine. Generation is automated and may produce mistakes.
• Device and service diagnostics: installation identifiers needed for workout synchronization; request, session and account identifiers; timestamps, error codes, and security events. Network services necessarily receive connection information such as an IP address. We use necessary operational information to authenticate requests, prevent abuse, troubleshoot, and keep the service working.
• Optional product analytics: if you opt in, events about app sessions, routine and workout interactions, synchronization outcomes, app/build and OS versions, platform, connectivity category, and telemetry identifiers help us understand and improve the app. Pseudonymous identifiers can still link events to an account; they are not anonymous.
• Support correspondence: your email address, messages, and information you choose to provide when contacting us, used to answer requests and verify account ownership safely.

Service providers

Amazon Web Services hosts the backend, database, processing queues, private objects, and operational logs. The selected generation service is Amazon Bedrock using Amazon Nova Micro and safety checks. The model receives your routine description and generation preferences; RoutineArc's processing systems also hold identifiers linking the request to your account. Do not include secrets in a generation request.

Our configured primary AWS Region is US West (Oregon). The selected US inference profile can process generation requests in other US Regions. This is not a promise that every sign-in, email, or device-platform provider processes all information only in the United States.

Apple or Google processes information when you choose its sign-in service under its own terms and privacy policy. Our public support mailbox uses Google's Gmail service. We may disclose information when legally required or as necessary to address fraud or protect the service and people's rights. We do not sell your information or use your fitness content for advertising.

AWS currently states that it does not use Amazon Nova inputs and outputs to train its models. Provider retention depends on the selected service, model, and configuration; RoutineArc also keeps its own processing records. This does not mean all copies disappear immediately.

Your choices

In the upcoming app, optional analytics will start off. You will be able to opt in and later turn it off in Account without losing the core service. Turning it off will stop new optional collection and delivery and clear unsent events. Requests already transmitted can finish; withdrawal does not erase records already received. Necessary security and service diagnostics continue for their stated purposes.

You can change available account settings and request account deletion in the app. You can also request deletion without the app using our account-deletion instructions. Contact us to request access to or correction of your information or to raise a privacy concern. We may need to verify that a request concerns your account. We will not ask you to email a password, sign-in link, or authentication code.

Storage, retention, and deletion

RoutineArc stores workout data and queued updates on your device so you can use supported features offline. Sign-out clears account-scoped local data and credentials through the app's cleanup process. An installation identifier can remain on the device. Deleting the app does not delete your server account, and a remote request cannot instantly erase an offline device or a backup you control.

Saved routines and workout history remain while your account is active. An accepted account-deletion request revokes access and schedules removal of account records; removal is not immediate. The current account-record purge becomes eligible 30 days after the request and depends on the maintenance process completing. Temporary generation inputs and unsaved previews have a seven-day logical expiry; cleanup of processing copies happens separately.

Our database backup configuration uses seven-day automated retention. Backup aging can pause while the database is stopped. Other recovery copies, including retained snapshots and generation recovery records, do not yet have a verified maximum removal period. Operational log configurations use 14 or 30 days depending on the resource, with provider deletion delay after expiry. Account deletion does not currently demonstrate removal of every linked processing or log copy. We are correcting these limitations before public app launch.

Support messages are used to handle your request. A removal schedule for resolved correspondence has not yet been operationally verified. Contact us for the status of a deletion request or associated data; we will explain any specific security or legal retention rather than treating all remaining copies as an exception.

Security and updates

We use access controls and encryption in transit and for configured cloud storage to protect information. No service can guarantee absolute security. We will identify the effective date of the published policy and explain material changes before applying new practices that require your choice.