Privacy Policy

Case information you enter yourself: the scenario, amount, currency, relevant dates, item name, and description.

Evidence you upload or paste: screenshots, receipt emails or text, and the structured fields extracted from them.

Operational data we need: case status and audit logs. The service is currently free, so we do not process any payment. If we introduce paid features later, payment would be handled by our payment provider (Stripe), and we would never see or store your card details.

Account data: your email address, and — if you sign in with Google — your name and basic profile information.

Technical data: your IP address, used transiently to determine your service region and to prevent abuse. We store it only in hashed (non-reversible) form, never as a raw address.

Messages you send us: if you email us, we receive your email address and the content of your message, and use them only to reply.

We do not collect or store your Apple ID password, two-factor (2FA) codes, payment passwords, or other sensitive credentials. The tool never logs in to your Apple account.

We use the information above only to: structure your evidence, assess material readiness, generate appeal letters and a submission guide, and send follow-up reminders.

To structure your evidence and generate letters, we send the relevant case text and any images you upload to a third-party AI provider (such as Anthropic or OpenAI), which processes them on our behalf as a service provider, solely to perform these functions. The provider does not receive this information for its own advertising.

We do not sell your personal information, and we do not share it with third parties for advertising.

We use Vercel Web Analytics, provided by our hosting provider Vercel, as an analytics subprocessor to understand how the product is used and to improve it. It records aggregate, anonymous page metrics — for example the page path, referrer, coarse geolocation (country/region/city), device type, browser, and operating system — which are transmitted to and stored on Vercel's servers on our behalf. We also send Vercel one custom, non-personal product event — a signal that an appeal letter was copied — carrying only a letter-version tag (v1/v2/v3), never letter content or any case detail.

Vercel Web Analytics does not use cookies and does not build a cross-site profile of you. Visitors are counted using a temporary hash derived from the request that is discarded within 24 hours; page metrics are not tied to your IP address or to any individual identity. This is not the same as collecting no data — aggregate usage data is collected — but it is designed so that it cannot identify or re-identify you.

Separately, we record our own first-party, PII-free funnel events on our servers to measure how far people get through the flow — for example that a case was created, evidence was added, a letter was generated or copied, or an outcome was reported. These events carry only non-personal, scalar tags (such as a scenario or letter-version tag and an acquisition-source token) and never case content, evidence, your identity, or any free text. They also include two feedback counters, recording only that the feedback panel was opened and that feedback was sent, tagged only with the feedback type and where in the app it was sent from; see section 5.

Aside from this analytics data, we use only first-party cookies. Two are functional: an essential authentication/session cookie for signed-in users, and a cookie that grants access to the anonymous case you started on this device and lets us measure the PII-free funnel steps described above. We also set a functional first-touch source cookie (ca_src) that stores only a referrer host or campaign token to attribute conversions per acquisition source; it holds no identity, is limited to same-site use, and expires after about 30 days. We set no advertising cookies.

When something goes wrong in the app, we automatically record a technical error report so we can find and fix the problem. It contains the error message and technical stack trace, the page or service path where it happened (with the query string and any case or account identifiers removed), the language, your browser type (not the full browser string), and — for errors in your browser — a random code generated for that single report. Before storing it, we automatically try to remove case and account identifiers, email addresses and token-like strings from the message and stack trace. This filtering is not perfect. Error reports are not tied to your account, are not used for advertising, are not sent to AI providers, and are deleted automatically after 30 days.

If you use the in-app Feedback button, we store the type of feedback you tapped (for example "Something broke" or "Confusing") together with limited technical context: the page path with the query string dropped and any case or account identifiers removed, the language, the step of the flow you were on (on a case page, only the tab and the case status stage, never the case contents), your browser type (not the full browser string), a coarse screen-size class, the app version, and a one-way hashed form of the anonymous session cookie described in section 4 (we never store the cookie value itself).

If an error happened in the same browser tab within about the last 30 minutes, the feedback may also include a short code for each of those errors (section 4): a signature of the type of error, shared by everyone who hits the same problem, never the error report's content.

If you choose to add a short note, we store up to 280 characters of it. Before storing it, we automatically try to remove common patterns such as email addresses, web links, long numbers and token-like strings. This filtering is not perfect, so please do not include passwords, verification codes, card details, contact details or other sensitive information. Feedback never includes screenshots, your evidence or your letters.

We use feedback only to find and fix problems and to improve the product. We do not store your account, name or email address with it, and it is not used for advertising. Your note and the technical details stored with it are not sent to AI providers. Our automated engineering tools, which use an AI provider, receive only summaries that cannot identify you: the feedback type, the page path template, counts and error-type signatures. Our internal notifications about new feedback contain only the feedback type, the page path, where in the app it was sent from, and counts, never your note. We also record two PII-free counters as part of the first-party events described in section 4: that the feedback panel was opened, and that feedback was sent, tagged only with the feedback type and where in the app it was sent from.

Feedback is not a support or refund channel and does not affect how Apple handles your refund request. Feedback records are deleted automatically after 90 days.

You can export your case data at any time, and you can delete a case and its evidence. Deletion is a hard delete: associated files are removed from storage as well. These features are already available in the product.

Depending on applicable law, you may also have rights to access, correct, restrict, or object to processing.

We retain your case data while you use the service and remove it once you delete it. Account data is retained until you delete your account or ask us to delete it.

If you created a case without an account (anonymously) and do not claim it by signing in, that case — including any files you uploaded — is automatically deleted after a limited retention period (about 30 days).

In-app feedback records (section 5) are deleted automatically after 90 days.

Emails you send us (section 1) are kept only as long as needed to handle your request, and are then deleted.

Automatic error reports (section 4) are deleted automatically after 30 days.

Depending on where the service is deployed, your data may be stored and processed in Wyoming, USA. The service is currently available in the United States only; if we later serve regions covered by frameworks such as the GDPR or the Personal Information Protection Law of the People's Republic of China, we will update this policy to address them.

For data-related requests, contact support@appealo.app. Data controller: Keelstone Software LLC.