SpikeSmart Support

Apple Health access

SpikeSmart requests permission to read blood glucose, steps, and workouts from Apple Health. If no glucose readings appear, confirm that your CGM app writes glucose data to Apple Health and that SpikeSmart has permission to read it. Activity context remains optional; SpikeSmart can still review glucose when step or workout access is unavailable.

On iPhone, open the Health app, tap your profile picture, choose Apps, select SpikeSmart, and review its blood glucose, steps, and workouts permissions. Apple may adjust these menu names between iOS releases.

About GMI estimates

GMI is an estimate derived from available glucose readings. Short or incomplete data windows may produce less representative results. SpikeSmart’s estimates and planning features are informational and are not a substitute for laboratory results or guidance from a qualified healthcare professional.

Free access and subscriptions

The public App Store version offers 60 days of full access after usable glucose data is available. You do not need to subscribe upfront, and free access does not automatically become a paid subscription. If you choose to subscribe, Apple shows the localized price and billing period before you confirm. Monthly and yearly plans include the same full access; the yearly plan is billed in full once a year. TestFlight access does not run a trial countdown.

Open Settings → Access to see your access status, available plans, Restore purchases and Manage subscription. Use the Apple Account that purchased the subscription to restore it. Canceling automatic renewal preserves access through the current paid period. After access expires, you can still view and export saved records and reach privacy, backup-account management and restoration controls.

Existing beta lifetime memberships remain valid when new enrollment closes and when you update to the App Store version. Under Settings → Access, use Keep your lifetime access to save an existing membership with Apple for recovery on another iPhone, or Restore beta lifetime access with the same linked Apple Account. This does not enable optional backup or usage sharing.

Optional backup

You do not need an account to use SpikeSmart. Signed-out and offline use remains fully functional for local meal logging, saved icons, labels and summaries. Optional Backup is off by default. In current TestFlight builds with backup enabled, enrollment is automatic after you enable the default-off Back up my data toggle and complete Sign in with Apple. No manual approval or enrollment ID is required for these builds. Builds without backup enabled remain local-only. You can use Sign in with Apple to synchronize all supported user data: meals, explicit predictions, spike labels, original food images, reusable foods, recorded Quest activation, manual days and acknowledgements, goals, workflow dates and notification preferences. Food history, Quest, library and settings contents are encrypted on your devices; compatible label backup also sends labels and processed custom images to the service. Restored settings appear in Settings for preview and explicit confirmation. Turning backup off stops synchronization while retaining local data, the saved account link and remote backup. Recovery, disconnect and remote deletion remain available. SpikeSmart does not request your name or email address from Apple. Backup does not upload Apple Health samples, glucose values or histories, GMI results, or other on-device calculations.

Food icons

In builds with Flare food icons, described meals are saved immediately while their icons are created in the background. New icons require an internet connection. The app authenticates automatically using Apple App Attest; Apple sign-in and Optional Backup are not required. OpenAI receives only the icon description. To revise an icon, open the meal’s Edit form, choose Change icon or Regenerate icon, then Save changes. Your current icon remains until the replacement is ready; generation failures keep your meal saved. You can also choose a standard food emoji or reuse a saved icon without a network request.

Update to the latest TestFlight build before enabling backup. If you see an enrollment error, turn backup off and contact support with the build number and error wording. Do not send an Apple subject, token, glucose reading, or other health information. Do not uninstall the app, reset its encryption key, or delete your remote account to troubleshoot a sign-in problem.

For an enabled backup account, labels are matched across your authorized devices with keyed pseudonymous event identifiers and encrypted event locators. The matching key remains on authorized devices rather than the backup service. Access or non-destructive writes may be paused during staged rollout. If backup is paused or offline, you can keep using the app normally. Changes are saved to the protected local copy and retry when the app is active and the service accepts writes. Remote-account deletion remains available during a write pause. A retained local copy on an iPhone stays linked to the Apple account that first enabled backup on that iPhone.

Sign in with Apple authorization

For a person who enables backup, the service stores a bounded set of encrypted Apple refresh credentials (at most eight in total across the live account and same-account cleanup work). It checks only the newest active credential, no more than once per day, to confirm that authorization remains valid and handles every retained credential when a remote account is deleted. A successful reauthorization may retire an older encrypted generation until deletion-time cleanup. These credentials cannot be used to read Apple Health data or your Apple profile, and SpikeSmart requests no name or email scopes.

For an enabled backup account, Apple may send the service a signed notification if you revoke consent or request deletion of your Apple Account. After verifying Apple's signature and event scope, the service stops sessions and deletes the remote backup while leaving the protected local copy on your iPhone. Notification replay/action records keep only one-way replay and account verifiers plus minimal type, timing, and processing state. A pending action has no expiry while unresolved; a processed replay/action record is kept only through the 14-day period measured from notification receipt. A provider-confirmed deletion separately retains a one-way account-generation status selector while pending and then only as part of the 90-day completion receipt. Its read-only status lookup accepts a canonical device proof only as request/rate-limit material; it never stores or binds that proof. The service does not keep the raw notification, Apple subject, plaintext account identifier, or device deletion proof.

If Apple conclusively rejects the active credential or a verified response identifies a different Apple subject, enabled backup pauses and you are asked to sign in with Apple again. Your local and remote copies remain while you reauthenticate. Temporary Apple, network, key, or configuration failures retry instead of forcing reauthentication or deleting data.

Disconnecting and deleting an account

For an enabled backup account, Disconnect Backup on This iPhone revokes only that app refresh-token family, removes that iPhone's saved service credential, and stops synchronization. It keeps the local copy, remote account, remote backup, and Sign in with Apple authorization. Delete Remote Account revokes the Apple authorization and deletes backed-up labels, custom images, and service sessions while keeping the local copy on that iPhone.

Deletion is recorded before provider cleanup starts. Temporary Apple or storage failures remain pending and retry; the app does not claim success early. A verified Apple consent-revoked or account-deleted event can also start the same remote deletion process. If a network interruption or event race hides the final response, the app can use its exact retained account-generation pair for the separate read-only status lookup. Its canonical proof is request/rate-limit material only, never stored or bound; the normal deletion receipt remains the proof-based completion check. Keep the app installed until it confirms deletion.

If, after at least a 24-hour recovery window, every stored Apple credential is proven absent or unrecoverable, SpikeSmart finishes deleting the remote backup and preserves a reminder that Apple access may still require manual removal. Follow that reminder to remove SpikeSmart from your Apple Account’s Sign in with Apple settings, then acknowledge it in the app. Temporary provider, key, or configuration failures remain pending and retry instead. The service keeps only a one-way completed-deletion receipt verifier for 90 days so the app can confirm a lost final response. Deleting the app alone does not request deletion of remote backup data, so use Delete Remote Account first if you want the remote copy removed.

Privacy and data requests

Read the SpikeSmart Privacy Policy for details about Apple Health, protected on-device storage, optional account backup, the retired pre-release iCloud storage path, and early-access submissions. Privacy and deletion requests can be sent to support@a14ylabs.com.

Medical emergencies

SpikeSmart does not monitor you in real time and should not be used for urgent alerts or treatment decisions. If you believe you may be experiencing a medical emergency, contact local emergency services or a qualified healthcare professional.