Account & Data Deletion

1.Who this applies to

Amaina is operated by Smart IT US Inc., a company incorporated in Wyoming, United States.

Mailing address: 30 N Gould St Ste R, Sheridan, Wyoming 82801, USA Privacy & legal contact: legal@smart-it.io Product support: support@smart-it.io

In this page, "we," "us," and "our" mean Smart IT US Inc. doing business as Amaina. "You" means anyone with a Amaina account. Amaina is for adults 18 or older.

2.Two ways to delete your account

You can delete your account and the data tied to it in either of two ways. Both do the same thing — pick whichever is easier for you.

Option A — In the app (fastest)

1. Open the Amaina app and make sure you're logged in.
2. Tap Settings.
3. Scroll to Delete Account.
4. Read the short confirmation screen — it lists what will be deleted.
5. Confirm. You may be asked to re-authenticate (Sign in with Apple, Google, or your email) to make sure it's really you.
6. That's it. Your account is scheduled for deletion and you're signed out.

Option B — By email

If you'd rather not use the in-app button, email legal@smart-it.io from the email address on your account (or tell us which account to close) and ask us to delete your account.

• We may need to verify your identity first — this protects you from someone else deleting your data.
• We'll confirm when it's done.

Either way, deletion is free and you don't need to give a reason.

3.What gets deleted

When your account is deleted, we remove the personal data we hold about you, including:

• Your profile — your first name, email, date of birth, and — if you provided it — your optional sex (Female / Male / Other / Prefer not to say). Date of birth and sex are both optional; we use date of birth only for age context in your insights, never to verify your age.
• Your attack logs — every migraine episode you logged: time, intensity, duration, symptoms, aura, medications and effectiveness, triggers, and your own notes.
• Health readings we stored — only what's written into your attack log is stored on our side (including any barometric pressure you saved alongside an attack). Raw readings we read from your Health app, and the live weather/location we look up, are processed on your device and not stored on our side, so there's no separate stored health dataset to delete beyond your attack log.
• AI-processed data — the structured fields and any doctor-summary text generated for you from your logs.
• Usage-analytics & subscription data on Amplitude — Two kinds of data may reach Amplitude (our analytics processor), both keyed to your anonymous internal user id (your Firebase UID): (a) if you turned on 'Usage analytics', anonymous behaviour/product-usage events — app/onboarding funnel, logging method, report and paywall interactions, an anonymous weather-banner event, and privacy-safe proxies such as attack severity as a coarse bucket, medication as a yes/no, and a trigger count (full event list: ANALYTICS_EVENTS.md); and (b) subscription-lifecycle events (trial started, purchased, renewed, cancelled) that our billing processor (RevenueCat) forwards to Amplitude to reconcile billing — treated as contractual/billing data and sent regardless of your 'Usage analytics' choice (no card data, no health data). Neither kind contains raw or derived health data, medication or trigger names, dates, or pain-location values, so there is no health content on that side to erase. Deleting your account severs that identity for both: we stop sending events, and events already collected are no longer linked to an active account and are aged out / de-identified per our retention. IP address, geo (country/region/city/DMA/lat-lng), carrier, and advertising id capture are disabled in the Amplitude SDK (TrackingOptions, build 18) — so no IP or location is collected, and turning Usage analytics off does not depend on any console setting.
• Account and login records — the authentication record that lets you sign in.

Your data is stored in Google Firebase / Firestore (our database) with authentication via Firebase Auth, and crash diagnostics via Firebase Crashlytics. Deleting your account removes your records from these systems. Crashlytics crash reports are anonymous and are not linked to your identity (no name, email, or Firebase UID is attached, and no health data is in them), so there is no user-identified crash data tied to your account to delete.

4.What happens on the AI provider's side

Some Amaina features send the text of your logs to our AI subprocessor, Anthropic (Claude), to turn your natural-language entry into structured fields (time, intensity, duration, symptoms, aura, medication, triggers) and — where the feature uses it — to draft a descriptive doctor summary. (The tap / manual-entry path works entirely without any AI.)

Here's the important part for deletion:

• Audio never reaches us or the AI. Voice is transcribed by Apple's speech recognition — which may run on your device or on Apple's servers — and we only ever receive the resulting text.
• Anthropic does not train on your data. Your content is used only to produce the structured output for you, never to train the AI provider's models.
• Content is automatically deleted within 30 days. Anthropic auto-deletes the text of AI requests (inputs and outputs) within 30 days — keeping it longer only if content is flagged for a safety/policy review (see the note below). We asked Anthropic for Zero Data Retention, which would remove even that short window, but it is currently offered only to large enterprise accounts, so we rely on this standard 30-day-deletion policy together with our data-processing agreement and our own data minimization.
• We minimize what we send. Only text is sent — never your name, email, date of birth, audio, or raw health-app readings — no health identifiers are used as field labels, and the AI is called only from our own backend — never from your browser.

Bottom line: because that content is auto-deleted downstream within 30 days — aside from the narrow trust-and-safety retention noted below — deleting your account doesn't leave a lingering AI-side copy that we then have to hunt down and erase. For the fuller picture of how AI processing works and the consent we ask for it, see the AI Processing Disclosure. If a lawyer or you would like the underlying documentation, our AI subprocessor operates under a signed Data Processing Addendum (with Standard Contractual Clauses) — email legal@smart-it.io.

5.Your Apple Health / Health Connect data stays yours

This is the one part people find surprising, so we want to be crystal clear.

With your granular permission, Amaina can:

• Read certain data from your Apple Health or Google Health Connect (for example sleep, menstrual cycle, and workouts) to compute your in-app insights. Raw readings are processed on your device and are not retained by us beyond what's needed.
• Write your headache episodes into your Apple Health / Health Connect so they live alongside the rest of your health record.

When you delete your Amaina account:

• We stop reading from and stop writing to your Health app.
• Raw sleep, cycle, and workout readings we read from your Health app are processed on your device where possible and not stored on our side, so there's nothing separate for us to delete — only your attack log (with any recorded barometric pressure) is stored in your account and removed on deletion.
• We delete the copies of health data stored in your Amaina account (see section 3).
• But anything Amaina already wrote into your Apple Health / Health Connect stays there. That store belongs to you and lives on your device / your Apple or Google account — we cannot reach into it to delete those entries. Only you can.

How to remove Amaina-written entries from Apple Health (iOS)

1. Open Apple's built-in Health app (the white icon with a red heart, pre-installed on your iPhone).
2. Tap your profile picture (top right) → Apps and Services (or Privacy → Apps).
3. Find Amaina and open it.
4. You can turn off Amaina's access to each data type, and you can delete data Amaina wrote from here.
5. To remove a specific data type entirely, open that category in Health (e.g. Headache) → Show All Data → swipe to delete, or use Edit → Delete All.

How to remove Amaina-written entries from Health Connect (Android — where available)

1. Open Health Connect (via Settings, or the standalone app).
2. Go to App permissions → Amaina to revoke read/write access.
3. Go to Data and access → choose a data type → See all entries to review and delete entries by source (Amaina), or use Delete all data options as needed.

Menus differ slightly by OS version; if you can't find these, your device maker's Health documentation has the current steps.

6.Revoking permissions (HealthKit, location, microphone)

You can withdraw any permission at any time — you don't have to delete your account to do it.

• HealthKit / Health Connect: see section 5, or Settings → Privacy & Security → Health → Amaina (iOS) / Health Connect → App permissions → Amaina (Android).
• Location: Amaina uses when-in-use location only to fetch local barometric pressure and a short (~24-hour) forecast so it can show a general colour-coded weather heads-up and let you see pressure alongside your attacks. We send approximate coordinates to OpenWeatherMap only to perform that weather lookup; we do not store them and never use them for tracking or ads. To turn it off: iOS Settings → Privacy & Security → Location Services → Amaina; Android Settings → Location → App permissions → Amaina.
• Microphone: used only when you choose voice logging (transcribed by Apple Speech, on your device or on Apple's servers). Turn it off in iOS Settings → Privacy & Security → Microphone → Amaina (Android: Settings → Apps → Amaina → Permissions). The tap / manual-entry path still works with the mic off.

Turning off a permission stops future collection; it doesn't delete data already saved to your account — use section 2 to delete that.

7.Timeline

• We complete account deletion within 30 days of your in-app request or email — usually much sooner.
• Backups roll off on their normal cycle shortly after; deleted data is not restored from backups except as strictly required to meet a legal obligation.
• If anything delays us past 30 days for a lawful reason, we'll tell you.

8.What we may keep (and why)

A few narrow things may survive account deletion:

• Records we're legally required to keep — for example, transaction/tax records for a subscription you purchased (subscriptions are billed through the Apple App Store; Apple handles your card, and we do not see or store your card data), or records we must retain to comply with a legal obligation, resolve a dispute, or enforce our agreements. We keep only what the law requires, for only as long as required.
• De-identified / aggregate data — statistics that can no longer be linked to you (e.g. "X% of users logged an attack this week"). Because these can't identify you, they aren't personal data, and we may keep them to understand and improve the product.
• Suppression / do-not-contact records — if you asked us not to email you, we keep the minimum needed to honor that.
• Security & abuse logs — limited technical logs kept briefly to protect the service.

We do not keep your health logs, insights, or AI-processed content after deletion outside these narrow, lawful cases.

9.Payments and your subscription

If you subscribed, your subscription is an auto-renewable subscription sold through the Apple App Store as an in-app purchase (Apple StoreKit, managed with our subprocessor RevenueCat). Apple processes the payment and handles your card — we never see or store your card data. RevenueCat receives only the purchase receipt, an app-assigned user identifier, and your subscription/entitlement status (no card data, no health data) so we can validate the purchase and unlock paid features. To reconcile subscriptions, we also forward subscription-lifecycle events (trial / purchase / renew / cancel) from RevenueCat to our analytics processor (Amplitude), keyed to your anonymous Firebase user id. These carry no card data and no health data, and — because they are billing/contractual — they are sent regardless of your 'Usage analytics' choice. They are severed and de-identified on account deletion (see section 3).

Deleting your Amaina account does not cancel your App Store subscription or issue a refund. These are two separate things:

• To cancel or manage billing, go to Settings → [your Apple ID] → Subscriptions on your iPhone (or App Store → your account → Subscriptions) and cancel Amaina there. If you delete your account without cancelling, Apple can keep charging your Apple ID — so cancel in Apple's subscription settings before or alongside your deletion request.
• Refunds are handled by Apple, not by us — we cannot directly refund an App Store purchase. Request a refund through Apple's Report a Problem page (reportaproblem.apple.com) or Apple Support.

Your subscription automatically renews at the then-current price unless auto-renew is turned off at least 24 hours before the end of the current period; payment is charged to your Apple ID at confirmation of purchase. Questions about your subscription: support@smart-it.io.

10.How your deletion request is protected

We treat symptoms, diagnoses, and medications you log as sensitive consumer health data. Deleting it is your right — and in several US states an explicit one:

• Under Washington's My Health My Data Act (MHMDA) and Nevada's SB 370, you can request that we delete your consumer health data, and we will.
• Under California's CPRA, you can request deletion of your personal information, including sensitive personal information.
• Under the FTC Health Breach Notification Rule, if a breach of your unsecured health data ever occurred, we'd notify affected users and the FTC (within 60 days), plus media notice if 500+ residents of a state are affected.

We may need to verify your identity before deleting, to make sure the request is really yours. For the full set of privacy rights and how we handle consumer-health-data collection and sharing consent, see the Privacy Policy. For all deletion and privacy requests: legal@smart-it.io.

11.If you're outside the US (EU / UK)

We do not currently target the EEA or UK — Amaina launches US-only. If that changes, EU/UK users would also have the right to erasure ("right to be forgotten") under the GDPR / UK GDPR, exercisable the same way (in-app Settings → Delete Account or legal@smart-it.io), subject to the same narrow legal-retention exceptions in section 8. Our AI subprocessor's Data Processing Addendum includes Standard Contractual Clauses covering such transfers.

12.Contact us

• Delete right now: In the app, Settings → Delete Account.
• Privacy / deletion by email: legal@smart-it.io
• Billing / subscription: support@smart-it.io
• Mail: Smart IT US Inc., 30 N Gould St Ste R, Sheridan, Wyoming 82801, USA

This page is written in plain English. If anything is unclear, email legal@smart-it.io — we'll explain and help you through it.