Consent record
Your choices. A record you can understand.
Appsolutely Labs LLC keeps an electronic record of agreements and consent for myHealthPal. It shows what you were told, what you chose and when. We believe in being transparent about what we record, why we keep it and how it is used. This page explains that record; it does not replace the app’s privacy notice or terms of service.
Agreements and permissions are separate
We record acceptance of the terms of service, acknowledgement of the privacy notice, and consent given or withdrawn for particular app features. A privacy-notice acknowledgement records that you saw the information; it is not blanket consent to every use of your data. Optional permissions are recorded separately.
What the record contains
The Consent Record contains evidence of agreements, permissions and data requests. It can include an account identifier, your choice, event and server timestamps, document version, the wording shown or its integrity hash, app version, platform and language. It does not contain a copy of your journal, symptoms, measurements or health history.
A permission entry records your choice about a type of data, not the data itself. For example, permission to use cycle records does not include period dates; permission to use mood records does not include mood entries or journal text. The choice itself is personal, so we treat it with care.
Why keep it on our servers?
A server-held record provides a consistent history even if a phone is replaced or the app is removed. It helps us demonstrate what was agreed, respect withdrawals, investigate questions or complaints, and meet applicable accountability obligations. It also provides evidence where necessary for a legal claim. It is not kept for advertising or marketing.
When you change your mind
You can withdraw consent for optional processing through the relevant app controls. A new entry records the change without silently rewriting the earlier choice. Withdrawal stops future processing that relied on that consent; it does not make earlier lawful processing unlawful. It is not permission to continue using your health information.
Encrypted records, controlled
access.
We are designing myHealthPal to store consent records in encrypted form. Reading a stored record will require authorised decryption. Approved systems may decrypt records to provide your history, handle a privacy request or meet a lawful obligation. Encryption does not make a record anonymous.
What happens when you delete your account?
Account deletion preserves a limited server-side consent record, linked to an internal account identifier and relevant dates, rather than erasing the history of agreements and choices. This allows us to explain what permission existed at a particular time, record its withdrawal, and address applicable legal obligations or claims. The retained evidence does not keep your account active.
This is not a blanket exception to deletion rights. We may retain identifiable evidence only where necessary and lawful for a specific purpose. A consent record can itself be personal or sensitive data: applicable law may require deletion, restriction or redaction of some or all of it.
- While your account is active
- We keep the agreement versions and choices needed to operate your account, respect your current permissions and explain relevant changes. Older entries are reviewed so that we keep only what is still needed.
- After account deletion
- We retain limited evidence of your agreements and choices where necessary and lawful to demonstrate what you accepted, meet legal obligations, and establish, exercise or defend legal claims. The retention period depends on the applicable law and relevant claim periods. Records needed for an existing or reasonably anticipated dispute may be kept until that matter is resolved. This does not keep your account active or mean we retain your full health records.
- Your data requests and their outcomes
- When you ask for a copy of your data or deletion, this part of your Consent Record records the request type and date, identity-verification outcome, action taken, response date and any reason for a refusal or limitation. It records that a copy was provided, not another copy of the exported data. We plan to keep these request records for 24 months after the request is closed, where lawful, separately from agreement evidence. Where the CCPA applies, request-and-response records must be kept for at least 24 months.
- Sensitive feature details
- We delete or redact health-revealing permission details when fulfilling a valid deletion request, unless a specific legal requirement or exception justifies retaining particular information. Keeping a consent history does not by itself justify retaining sensitive details.
A longer legal hold will apply only to specifically necessary records for a documented legal obligation or claim. The hold will be reviewed at least every six months and the affected records removed when the justification ends, unless another lawful retention requirement applies.
Start your request in the app
You will be able to request a copy of your data or deletion through the app’s account controls. Your request will be recorded and timestamped in your Consent record, then processed automatically where possible. You will receive confirmation, progress updates and the outcome. Requests needing identity checks or a legal decision will be reviewed, with updates throughout.
Choose and confirm
Choose a copy of your data or account deletion in the app and complete the identity check. The app will explain what is included and any information that must be retained before you confirm.
Follow its progress
Your Consent record will capture the request type, time received, confirmation and outcome. You will be told the applicable response deadline, any action needed from you, and the reason and revised date for any permitted extension.
Receive the outcome
For a copy request, you will receive secure access to the available data. For deletion, you will receive confirmation of what was deleted and details of any limited record retained, its reason and retention period. You will continue to receive updates even after account access ends.
Connected apps, copies and deletion
Supported records can reach myHealthPal through Apple Health or Health Connect, including records shared by apps such as Oura or Ultrahuman. Availability depends on the source, device and permissions. This does not give myHealthPal access to your entire account with that provider.
A copy of the data we process
A data-access request covers personal information for which we are responsible, including imported copies and related source or connection records we hold. We do not exclude information just because it came from another app. Applicable exemptions and other people’s rights still apply. Device-only records may need to be included through the in-app export.
Linked or viewed without keeping a copy
Viewing data without storing it does not automatically remove our privacy obligations. We explain what we access and process. A link does not give us control of another provider’s full records; request their complete account data directly from them. We cannot recover records we no longer hold and cannot access.
Removing the myHealthPal copy
Disconnecting Apple Health or Health Connect stops imports and removes the imported copy from myHealthPal on that phone. It does not erase the source records. Reconnecting may import them again. Deletion may also attempt to remove supported entries myHealthPal itself wrote to a health service, subject to permissions; removal there is not guaranteed.
Records held by another service
Deleting your myHealthPal account does not delete your Oura or Ultrahuman account, or source records created by other apps in Apple Health or Health Connect. To remove those independent copies, use the relevant health-service controls and the source app’s deletion process, or contact that provider. Deleting a record in one place does not necessarily erase copies already held elsewhere.
When you can expect a response
The response times below apply where the relevant law covers your request. They are separate from the periods for keeping consent records. We will act sooner where possible and tell you about any lawful extension or necessary verification.
European Union / EEA
We will respond without undue delay, normally within one calendar month of receiving your request. If complexity or the number of requests permits an extension, we will explain it within the first month; the extension can be up to two further months. Your response will include the available data or the deletion outcome and reasons for any lawful limits.
United Kingdom
We will normally respond within one calendar month. If an extension of up to two further months is legally permitted, we will explain why within the initial month. We will tell you if identity verification or clarification affects the deadline and explain any information retained or withheld.
Brazil
We will provide a simplified confirmation or access response immediately, or a complete access statement within 15 days. For deletion or other rights, we will take prompt action and explain any factual or legal reason preventing immediate completion. The 15-day access period is not a universal deadline for every type of request.
California
Where the CCPA applies, we will confirm receipt within 10 business days and respond within 45 calendar days of receipt. If necessary and permitted, we will explain an extension of up to 45 additional days before the first deadline. A limited compliance log of the request and response will be kept for 24 months; this is not permission to keep the underlying health records.
Washington
For requests covered by My Health My Data, we will act without undue delay and within 45 days of receipt. A necessary extension of up to 45 further days will be explained before the first deadline. Deletion will cover affected health data and relevant shared copies; we will notify recipients. If a permitted archive or backup delay is needed, it will not exceed six months from authentication. We will explain a refusal and how to appeal.