Encrypted keys
Your App Store Connect, Google Play, Apple Ads and RevenueCat keys and your alert channel secrets are stored encrypted with AES-256-GCM and never shown again once saved.
Uptika stores integration keys encrypted with AES-256-GCM, checks workspace isolation on every API call, never sees your card details and lets you download or delete your data whenever you want.
What we do, and what we do not do yet, plainly.
Your App Store Connect, Google Play, Apple Ads and RevenueCat keys and your alert channel secrets are stored encrypted with AES-256-GCM and never shown again once saved.
Your password is never stored as plain text; it is hashed with scrypt.
The session cookie is HttpOnly and SameSite=Lax, valid for 30 days. Resetting your password signs out open sessions.
Every API call is checked so a request only reaches its own workspace data.
Shown only once; you see when each was last used and can revoke it at any time. The API is read-only; its one write is adding keywords.
Nothing that could raise spend happens without your explicit approval, and every change is logged with its before and after values.
Card payments are handled by iyzico; your card details never reach Uptika.
Two-factor authentication (2FA) is not available yet. Use a strong password you do not use anywhere else.
Keyword ranks, category charts, app listings and reviews are read from the App Store's and Google Play's public data. None of this needs a connected account.
To improve the product and find bugs we keep product analytics events, sign-in events and presence for 180 days and the error log for 90 days. Free-tool visitor usage counters are deleted after 2 days. All retention periods are on the Capabilities page.
The only thing that leaves your dashboard is the score page and badge you switch on.
A public score page exists per storefront only if you turn it on. Turn it off and the badge goes neutral with no score; rotate the link whenever you like.
The public page and the badge show only the parts computed from the store listing.
Store console data such as installs, revenue and conversion shows only in your dashboard and your report, never on the public page.
Uptika uses outside services for a few jobs; each one receives only what that job needs.
| Service | What for | What it receives |
|---|---|---|
| iyzico | Card payments | What the payment needs. Your card details never reach Uptika. |
| Resend | Transactional e-mail: password resets, team invites, receipts, the contact form | The recipient's e-mail address and the e-mail's content |
| DeepSeek | AI text: Uptika's take, Ask AI answers, drafts | Only the numbers on screen and your question. Your store credentials are never sent. |
| Browsers' push services | Delivering Web Push notifications to your phone or computer | The notification text, sent to the subscription address your browser provides |
Payment and receipt records are kept for 10 years under Turkish tax law, without the Turkish ID number.
Uptika reads from the accounts you connect. The one exception is Apple Ads, where a change happens only when you approve it in the dashboard, and it is logged. Your listing and your app are never touched.
For Uptika's take, Ask AI and drafts, only the numbers on screen and your question are sent to DeepSeek. Your keys and account details are not sent.
Not yet. Until then, use a strong password you do not use anywhere else.
Write to destek@uptika.app with the details. We ask that you do not share it publicly until it is fixed.