Privacy Policy

Account and profile. Email address, name, optional avatar, sign-in method (email/password, Google, or GitHub), and your onboarding answers (how MILO should address you, communication style, what you are building, and your home territory).

Platform credentials. The App Store Connect API key you upload (the .p8 key with its issuer and key identifiers). This is the most sensitive data we hold and is treated accordingly; see the Security section.

Store data.Data the Service retrieves from your App Store Connect account on your instruction: apps, pricing, listings and localizations, screenshots, builds, TestFlight data, customer reviews, and analytics reports. Customer reviews may contain personal data of your app's users; for that data you are the controller and we process it on your behalf to display and answer it.

MILO conversations.Your chat messages, voice transcriptions, images you attach, the tools MILO ran and their outcomes, and MILO's replies. For voice, audio streams in real time to our AI provider for processing; we store the resulting transcript, not the raw audio.

MILO memories. Durable facts and preferences MILO saves to serve you better (for example, your preferred form of address). Memories are fully visible, editable, and deletable by you in Settings.

Change history. An audit log of every change applied to your store through the Service (what changed, the before/after diff, when, and through which surface: chat, voice, MCP, or manual).

Studio projects and uploads. Screenshot studio projects and the images you upload to them, stored in private storage.

Usage and billing. Metered usage events (MILO actions, voice minutes, AI translations), subscription status, and plan. Payments are handled by Paddle, our merchant of record: we receive subscription and transaction metadata but never your full card details.

Technical data. Product analytics events (via PostHog), error reports (via Sentry), and standard server logs (IP address, user agent, timestamps) used for security and reliability.

• To provide the Service (contract): operating the dashboard, executing the operations you request against App Store Connect, rendering screenshots, tracking ASO keywords, and keeping your change history and revert capability.
• To power MILO (contract): interpreting your instructions, maintaining conversation history and memories, and proposing previews.
• To meter and bill (contract): enforcing plan quotas and processing subscriptions through Paddle.
• To secure and improve the Service (legitimate interest): fraud and abuse prevention, error monitoring, and aggregate product analytics.
• To communicate with you (contract or legitimate interest): service emails such as sign-in confirmations and password resets, and replies to your support requests.

MILO, translations, and vision features are powered by Google Gemini models via Google's API. When you use them, the relevant content (chat messages, voice audio, images you attach, and the store data needed to answer) is sent to Google for processing under Google's API terms. Under those terms, Google does not use data submitted through the paid API to train its models.

• Voice audio streams directly from your browser to Google using a short-lived, single-use token; the token never exposes our API key or your credentials to the browser.
• Your App Store Connect credentials are never included in any AI prompt or shared with the AI provider.
• MILO may automatically extract durable memories from conversations; you can review, edit, or delete every memory in Settings.

We do not sell personal data and we do not share it for advertising. We share data only with the processors needed to run the Service:

• Supabase: database, authentication, and file storage.
• Vercel: application hosting.
• Google: AI model processing (Gemini), and sign-in with Google if you choose it.
• Paddle: payments, as merchant of record. Paddle acts as an independent controller for the payment data it collects.
• PostHog: product analytics.
• Sentry: error monitoring.
• Apple: we transmit the changes you confirm to App Store Connect on your behalf.
• GitHub: sign-in with GitHub, if you choose it.

Reference data providers (for example exchange-rate and World Bank data used by the pricing engine) receive no personal data. We may also disclose data where required by law or to protect our rights, and in a merger or acquisition your data may transfer to the successor under this same policy.

Our processors operate infrastructure in the European Union and the United States, so your data may be processed outside your country. Where data leaves the EU/EEA or Albania, we rely on recognized safeguards such as the EU Standard Contractual Clauses and, for US providers, the EU-US Data Privacy Framework where the provider is certified.

• Account, conversations, memories, projects: kept while your account exists; deleted when your account is deleted.
• Platform credentials: kept until you disconnect the platform or delete your account, then deleted.
• Change history: retained according to your plan's retention window, and deleted with your account.
• Billing records: retained as long as tax and accounting law requires.
• Logs and error reports: retained for short operational windows, then deleted or anonymized.
• Trial-abuse markers: when you delete your account, we retain a one-way cryptographic hash of your email address and sign-in identity (never the email or any readable data itself) so that a deleted account cannot be recreated to restart the free trial. This is done on the basis of our legitimate interest in preventing abuse; the hash cannot be reversed to identify you and is used for no other purpose.

Residual copies may persist briefly in encrypted backups until those backups rotate out.

Security measures include:

• TLS encryption for all data in transit.
• Envelope encryption for platform credentials: each credential is encrypted with its own AES-256-GCM data key, which is itself encrypted under a master key held in a separate vault. Credentials are decrypted only in server memory at the moment of use, are never logged, and never reach your browser.
• Database row-level security, so every record is scoped to its owner.
• A strict confirmation model: nothing writes to your store without your explicit confirmation, on any surface.
• Hardened HTTP security headers, upload validation by file content (not claimed type), and audit logging of every applied change.

No system is perfectly secure. If we learn of a breach affecting your personal data, we will notify you and the competent authority as required by law.

Under the GDPR and Albania's Law No. 124/2024 "On Personal Data Protection", you have the right to access, rectify, erase, and receive a portable copy of your personal data, to restrict or object to certain processing, and to withdraw consent where processing is based on consent.

You can exercise most of this directly: edit your profile and MILO memories in Settings, disconnect platforms, and delete conversations. For anything else, including full account deletion, email support@hysa-tech.com; we respond within 30 days.

You also have the right to lodge a complaint with the Albanian Information and Data Protection Commissioner (idp.al) or your local supervisory authority.

If the law of your place of residence grants you additional privacy rights (for example the UK GDPR, or US state laws such as the CCPA/CPRA where they apply), we honor those too: the same contact address handles all requests, and we do not "sell" or "share" personal data as those laws define it.

The only cookies we set are essential session cookies (Supabase Auth) that keep you signed in. They are SameSite-restricted and the Service cannot work without them, so no cookie consent banner is required.

Our product analytics (PostHog) runs cookieless: it stores nothing on your device, keeps its identifiers in memory for the current session only, and runs only inside the authenticated app, never on the public website. We use no advertising or cross-site tracking cookies of any kind.

The Service is a professional tool and is not directed to anyone under 18. We do not knowingly collect data from children; if you believe a child has created an account, contact us and we will delete it.

We may update this policy as the Service evolves. For material changes we will notify you by email or in the app before they take effect. The effective date at the top always reflects the current version.

Hysa Tech SHPK, Tirana, Albania. Privacy questions and data requests: support@hysa-tech.com. See also our Terms of Service.