Effective 5 September 2026
Privacy, in plain language.
ActualSet stores the information needed to run your account, synchronise your training, and show you your history. It does not sell data or run advertising. Optional sign-in providers process authentication and related technical information under their own privacy policies, as described below.
Who operates ActualSet
ActualSet is operated by Yago Patrick. Email [email protected] about your information or account.
Information ActualSet stores
- Your email address, display name, login credentials in protected form, and account security records.
- Your exercises, workout plans, completed sessions, set values, notes, muscle tags, timer settings, and other training information you enter or import.
- Optional body check-ins you separately choose to enable and record, including weight, body fat, body measurements, and custom measurements.
- Short workout-code snapshots you choose to create.
- When you choose Share format feedback after reviewing an import, the missing format label and prompt-card version linked to your account. This never includes workout content, exercise names, or notes.
- Temporary network-address and failed-login records used to prevent abuse.
Optional Google and Apple sign-in
Where available, you can choose Google or Apple instead of a password. ActualSet verifies the provider's account identifier and email information. New accounts require a display name you choose and explicit acceptance of the Terms and Privacy Policy. Matching email addresses never link accounts automatically. To connect Google or Apple to an existing password account, first confirm the provider identity and then explicitly confirm that ActualSet account’s current password. The original account, primary email and training records stay the same; accounts are never merged or transferred. Apple private relay addresses are not used to guess another account’s email. Google connection is available where enabled. New Apple connections remain behind a separate availability gate; an already connected Apple identity can still sign in.
On the website, Google's sign-in library loads when the available Google button is prepared on the authentication screen, or when you open connected sign-in controls in Settings; Apple uses its authorization page. On iPhone, Google's native sign-in SDK and Apple's system sign-in prompt handle provider authorization. On Android, Google sign-in uses Android Credential Manager and Google's identity library. Google and its SDK may process account, device, usage and network information, including IP-based approximate location, for authentication, security and purposes described in Google's privacy policy and SDK privacy disclosures. ActualSet requests basic authentication only. The provider receives the technical information involved in that interaction under its own privacy policy. ActualSet does not send your exercises, workout plans, notes, or body measurements as part of these authentication requests and does not receive your Google or Apple password. See Google's Privacy Policy and Apple's Privacy Policy.
ActualSet stores the verified provider identifier associated with your account. For Apple, it also stores encrypted authorization credentials to check continuing authorization and attempt revocation when you delete your account. These use a separate server key and are not returned as app session credentials or stored in workout records. Provider credentials are not placed in ActualSet callback URLs or browser localStorage. Short-lived authentication cookies and per-tab attempt proofs protect requests you start. A verified identity awaiting registration or password confirmation stays in bounded server memory for at most five minutes; no account or session is created until the required confirmation succeeds; Apple's five-minute callback cookie permits its cross-site response, with a separate same-origin confirmation before account adoption or deletion.
Apple can notify ActualSet about mail forwarding changes, revoked authorization, or deletion of an Apple Account. ActualSet verifies signed notifications and their ordering against the current identity before applying changes. Revoked authorization or deletion of an Apple Account invalidates current ActualSet sessions and prevents old Apple authorization from continuing to be used. These Apple events do not by themselves delete your ActualSet account, training or other sign-in methods. Fresh Apple authorization is required before Apple sign-in can be used again; ambiguous cases are held for reconciliation. If you hide your email, delivery depends on Apple's forwarding settings.
What stays on your device
ActualSet keeps local copies of your training so it remains usable without a connection. Body check-ins do not synchronize until you separately enable body measurements in Profile. Your metric or imperial display preference stays on that device. Photos used in share images are processed on your device and are not uploaded by ActualSet.
How information is used
Information is used to authenticate your account, synchronise your devices, run and record workouts, show your private measurement history, calculate your progress, create features you request, prevent abuse, recover passwords, and operate ActualSet. Optional format feedback is used to decide which import-format capability to improve.
Body-measurement synchronization requires a separate explicit choice in Profile. It is not enabled by accepting the Terms, acknowledging this Privacy page, choosing display units, or using workout tracking. When enabled, existing measurements on that device and future check-ins synchronize privately across devices on the same account.
Legal bases and your choices
- Account, authentication, requested synchronization, workout storage, password recovery, and features you deliberately request are processed as necessary to provide the service under the Terms.
- Minimal security, abuse-prevention, service-reliability, and explicitly shared format-feedback records are processed for ActualSet's legitimate interests in protecting and improving the service. These interests are balanced through short retention, restricted content, no advertising, no tracking, and the choices described below.
- Optional body-measurement synchronization uses your consent and your separate explicit consent for health-related information. You can refuse it without losing workout tracking, and you can withdraw it and delete synchronized measurements from Profile.
- Optional Training Wall sharing uses the choice you make in Settings. It is off by default for new accounts and can be disabled again.
You may object to processing based on legitimate interests, withdraw consent, or ask about access, correction, deletion, restriction, or portability by emailing [email protected]. You may also complain to the Irish Data Protection Commission or the data-protection authority where you live.
AI processing
Workout JSON you paste is interpreted on your device. If you deliberately press an online AI action, the exercise, current workout context, selected constraints, and text you entered are sent to a third-party AI processing service. The screen identifies this before anything is sent. Do not include information you do not want processed by that service.
Who receives information
- Hosting, DNS, security, routing, and encrypted-backup providers process the limited information needed to run and recover the service.
- A transactional-email provider receives your email address for requested verification, password recovery, or an available account-deletion confirmation.
- Email-routing and mailbox providers receive the sender, recipient, subject, and content of messages you send to support. Do not email body measurements, health details, workout notes, passwords, access links, or database backups.
- An AI processing provider receives only the information described above when you explicitly request online suggestions.
- Signed-in users can see a limited Training Wall summary when sharing is enabled. You can disable this in Settings. Notes, email addresses, RPE, and completed set values are not shown there.
Body measurements and check-ins are private. They are not included in the Training Wall, workout codes, or share images, and no other ActualSet user can access them.
Some service providers process information outside the European Economic Area. ActualSet limits what each provider receives and uses the available data-processing terms and transfer mechanisms described by those providers. Connected online AI remains excluded from the public-store app.
ActualSet does not sell personal information and does not share it for advertising.
Retention and deletion
Live account and workout data remains until you delete the applicable record or account. Body measurements remain until you delete them, withdraw body-measurement consent, or delete the account. Withdrawal immediately deletes measurement rows and queued uploads from the device making the request and deletes the live server copy when connected. Other devices must update before they can synchronize; after updating, they delete their copies when they next contact the account. Withdrawal does not delete workouts or other Profile information. Optional format feedback is removed within 365 days after its last report, or sooner when you delete the account. Account deletion removes the live account, workouts, history, notes, body check-ins, measurements, login methods, sessions, feedback records, and workout codes. Encrypted or access-restricted backup copies may remain until they rotate out, currently within 14 nightly snapshots.
Deferred Apple event details are encrypted for up to seven days. Digest and review metadata can remain for one further week without restoring expired payloads. Processed-event replay receipts contain only an event digest and receipt time and expire after seven days. Revocation boundaries linked to an existing Apple identity remain until that identity is removed with the ActualSet account. A subject digest for a verified revocation received before an ActualSet identity exists is retained for up to seven days to reject older in-flight authorization attempts. A digest proving that an original active session belonged to a deleted account lasts at most seven days and never beyond that session's original expiry. Logical expiry removes authority immediately; physical cleanup occurs during maintenance. These records do not establish a complete event history after expiry. Recovery from encrypted backups requires reconciliation of social-account authorization and deletion state before restored accounts can be used.
Other offline devices can retain downloaded training until they reconnect and receive an authenticated deletion confirmation, or you explicitly clear that device's downloaded data. A generic sign-in failure or provider outage does not erase an offline copy. Devices returning after the deletion-proof window may need explicit local cleanup.
Security and your choices
Connections use HTTPS. Passwords and live session credentials are not stored in readable form. No internet service can promise absolute security. You can withdraw body-measurement consent and delete those measurements in Profile, disable Training Wall sharing, delete downloaded device data, or permanently delete the full account from Settings.
Children and changes
ActualSet is intended only for people aged 18 or older. Material privacy changes will update this page and its effective date before a public release.
Connecting ChatGPT: data and permissions
MCP connection notice published 30 October 2026. Availability wording updated 31 October 2026. This separately dated notice explains the ChatGPT connection alongside the policy dated 5 September 2026. At launch, the optional ChatGPT connection is available to ActualSet users who sign in and authorize it. Your connection uses only the permissions you approve. Publishing this notice does not connect your account or grant access to your training.
When you connect ChatGPT to ActualSet through MCP, the connection can read your own saved workout plans, exercises within those plans or sessions, and synchronized training history within the permissions you approve. It cannot read training that remains only on an offline device. Names and other text can contain personal information. Structured Profile fields and body-measurement records are excluded from these tools; this does not remove measurements or health information you have typed into names or notes.
You can authorize workout proposals, direct creation of new plans and editing of existing eligible plans. Proposals return a private ActualSet link and require your review and Save before becoming a plan. Direct creation and editing write immediately when called with their respective permissions; they do not have that ActualSet review/Save step. Editing can replace planned exercises and sets, including removing planned items, while preserving completed and active session history. These tools do not create completed training sessions.
Notes access is a separate optional permission, off by default on the consent page. Ordinary workout and session detail requests omit notes unless notes are explicitly requested and that connection has both read and notes permissions. The dedicated notes tool requires both permissions too. Supported notes are returned as exact text within size limits. They may contain health or other sensitive information and are not automatically filtered. Notes and names are untrusted content, not instructions for the assistant.
The ActualSet consent page controls the server grant and its account-specific permissions. Any approval requested by ChatGPT before a tool call is a separate host control; it does not add missing ActualSet permission. Refreshing a connection does not silently add notes or other permissions to an existing grant.
This optional connector transfer is separate from the online suggestion actions described earlier. Information returned by the tools is sent to ChatGPT/OpenAI for the request you make. Copies already received there are governed by your ChatGPT account settings and OpenAI policies. Read OpenAI’s Privacy Policy. ActualSet does not promise that revocation deletes those copies or controls their retention or use.
Manage ActualSet connections while signed in to the intended account. Revoking one grant stops its future access, invalidates its credentials through grant checks and deletes its stored draft/receipt rows. It does not undo saved plans or edits, delete your ActualSet account or erase information already received by ChatGPT. Each grant is separate; revoke every connection you want to stop.
Grants expire 30 days after authorization. Access tokens last at most 15 minutes and never beyond grant expiry; refresh tokens expire with the grant and rotate on use. Single-use authorization codes expire after 60 seconds. Consent, review and revoke interaction nonces expire after 10 minutes. ActualSet stores credential hashes rather than readable token values; used authorization-code and refresh-token hashes can remain until grant expiry to detect replay.
Review drafts last up to 24 hours and can become unavailable earlier if their grant expires or is revoked. Expired draft content is cleared during maintenance; request fingerprints and saved-plan or edit receipts can remain until the grant expires to prevent duplicate writes. Edit receipts contain revision metadata; direct-creation receipts do not retain the submitted plan payload. Revoked grant metadata and credential hashes can also remain until the original grant expiry. Expiry stops authority immediately; physical cleanup runs during maintenance, including at startup, on a six-hour schedule and during relevant connector requests. This is not a promise of physical deletion at the instant of expiry.
Application server-error logs record request identifiers, method, path, status and duration; paths can contain record identifiers. The notes reader does not add note content to application logs or new note storage. Hosting infrastructure may keep its own request logs; this notice does not establish a verified provider-log retention period. Encrypted backups may include connector records. The existing nightly-snapshot rotation in the Retention and deletion section still applies; separately retained encrypted recovery copies may remain until removed. Revocation does not erase older backups. See the existing retention, deletion and rights sections.
Conectar o ChatGPT: dados e permissões
Aviso sobre a conexão MCP publicado em 30 de outubro de 2026. Texto de disponibilidade atualizado em 31 de outubro de 2026. Este aviso com data própria explica a conexão com o ChatGPT junto com a política de 5 de setembro de 2026. No lançamento, a conexão opcional com o ChatGPT fica disponível para usuários do ActualSet que entram na conta e a autorizam. Sua conexão usa somente as permissões que você aprova. Publicar este aviso não conecta sua conta nem concede acesso aos seus treinos.
Ao conectar o ChatGPT ao ActualSet por MCP, a conexão pode ler seus planos de treino salvos, os exercícios desses planos ou sessões e seu histórico de treino sincronizado, dentro das permissões que você aprovar. Ela não lê treinos que permanecem apenas em um dispositivo offline. Nomes e outros textos podem conter dados pessoais. Os campos estruturados do Perfil e os registros de medidas corporais ficam excluídos destas ferramentas; isso não remove medidas ou informações de saúde que você tenha escrito em nomes ou notas.
Você pode autorizar propostas de treino, criação direta de novos planos e edição de planos existentes elegíveis. Propostas retornam um link privado do ActualSet e exigem sua revisão e a ação Salvar antes de se tornarem um plano. A criação direta e a edição gravam imediatamente quando chamadas com suas respectivas permissões; elas não têm essa etapa de revisão/Salvar do ActualSet. A edição pode substituir exercícios e séries planejados, inclusive remover itens planejados, preservando o histórico de sessões concluídas e em andamento. Estas ferramentas não criam sessões de treino concluídas.
O acesso às notas é uma permissão opcional separada, desmarcada por padrão na página de consentimento. As consultas comuns de detalhes de treino e sessão omitem notas, salvo quando elas são pedidas explicitamente e a conexão tem as permissões de leitura e de notas. A ferramenta específica de notas também exige ambas. Notas compatíveis são retornadas como texto exato dentro dos limites de tamanho. Elas podem conter informações de saúde ou outros dados sensíveis e não são filtradas automaticamente. Notas e nomes são conteúdo não confiável, não instruções para o assistente.
A página de consentimento do ActualSet controla a autorização no servidor e suas permissões para aquela conta. Qualquer aprovação solicitada pelo ChatGPT antes de chamar uma ferramenta é um controle separado do ChatGPT; ela não adiciona uma permissão ausente no ActualSet. Atualizar uma conexão não adiciona silenciosamente notas ou outras permissões a uma autorização existente.
Esta transferência opcional pela conexão é separada das ações de sugestão online descritas acima. As informações retornadas pelas ferramentas são enviadas ao ChatGPT/OpenAI para a solicitação que você fizer. As cópias já recebidas lá seguem as configurações da sua conta do ChatGPT e as políticas da OpenAI. Leia a Política de Privacidade da OpenAI. O ActualSet não promete que a revogação apague essas cópias nem controla sua retenção ou uso.
Gerencie as conexões do ActualSet com a conta desejada conectada. Revogar uma autorização impede seu acesso futuro, invalida suas credenciais pela verificação da autorização e apaga suas propostas e recibos armazenados. Isso não desfaz planos salvos ou edições, não exclui sua conta do ActualSet nem apaga informações já recebidas pelo ChatGPT. Cada autorização é separada; revogue todas as conexões que quiser interromper.
As autorizações expiram 30 dias após serem concedidas. Tokens de acesso duram no máximo 15 minutos, sem ultrapassar a validade da autorização; tokens de renovação expiram com a autorização e são substituídos a cada uso. Códigos de autorização de uso único expiram após 60 segundos. Identificadores de uso único para consentir, revisar e revogar expiram após 10 minutos. O ActualSet armazena hashes das credenciais, não os tokens legíveis; hashes de códigos de autorização e de tokens de renovação já usados podem permanecer até o vencimento da autorização para detectar reutilização.
Propostas para revisão duram até 24 horas e podem ficar indisponíveis antes se a autorização vencer ou for revogada. O conteúdo vencido é apagado na manutenção; identificadores de conteúdo e recibos de planos salvos ou edições podem permanecer até a autorização expirar para evitar gravações duplicadas. Recibos de edição contêm metadados de revisão; recibos de criação direta não retêm o conteúdo do plano enviado. Metadados de autorizações revogadas e hashes de credenciais também podem permanecer até o vencimento original. O vencimento retira a autoridade imediatamente; a limpeza física ocorre na manutenção, inclusive ao iniciar o servidor, a cada seis horas e em solicitações pertinentes da conexão. Isso não promete exclusão física no instante do vencimento.
Os registros de erros do servidor incluem identificador da solicitação, método, caminho, status e duração; caminhos podem conter identificadores de registros. A leitura de notas não acrescenta seu conteúdo aos registros da aplicação nem a um novo armazenamento de notas. A infraestrutura de hospedagem pode manter registros próprios de solicitações; este aviso não estabelece um prazo verificado para eles. Backups criptografados podem incluir registros das conexões. A rotação de cópias noturnas descrita na seção Retention and deletion continua aplicável; cópias criptografadas de recuperação retidas separadamente podem permanecer até serem removidas. Revogar não apaga backups anteriores. Consulte as seções existentes sobre retenção, exclusão e direitos.