Privacy & contact

Indevaro is in public beta: the service is available with paid plans, and features may still change. This notice explains which personal data Indevaro processes, why, on which legal basis, for how long, who helps us process it and which rights you have.

The controller of the personal data described here is LimitWaste Sp. z o.o., ul. Wspólna 19/72, 25-003 Kielce, Poland, KRS 0000803658, NIP 5272905462, REGON 384349430. You can reach us about anything in this notice at contact@indevaro.com. We have not appointed a data protection officer, because Art. 37 GDPR does not require one for our processing; send privacy requests to contact@indevaro.com.

What we store

Signing in uses your email address and a verification code. The workspace stores the app profiles, plans, drafts and results you add. When you connect an integration, Indevaro stores connection credentials on the server and imports the data needed for that feature, such as store listings, advertising reports or keyword rankings.

Workspace data is accessible to authorized members of that workspace. Authentication cookies keep you signed in. Hosting and authentication services process the technical information needed to serve the site and protect access.

You can disconnect integrations and use the workspace data controls to export or delete workspace data. For account deletion or questions about your information, contact contact@indevaro.com.

When you buy a paid plan, the payment is handled by Polar, which acts as the merchant of record: as the seller, under its own privacy policy, it collects the billing details and the card data needed to take the payment, charges and remits the applicable tax, and issues the invoice. Indevaro never receives or stores card details. What we store about a purchase is the subscription itself — which plan, which billing period, its status and its dates — together with the provider’s identifiers for it and the events the provider sends us; personal details in those events, such as an email address, name, billing address or tax identifier, are removed before the event is stored. You can see and export this through the workspace data controls, and manage or cancel the subscription in the provider’s customer portal.

RevenueCat is connected through a separate OAuth authorization. Indevaro stores encrypted access and refresh tokens on the server, the authorized project/app catalog, the explicit app binding, sync status, and project-total gross revenue for the requested date range. It does not import subscribers, customer identifiers, entitlements, transactions, chart series, or per-app revenue. Disconnecting deletes the stored token; revoke the provider-side grant in RevenueCat if you also want to invalidate access there.

Product analytics

We measure how Indevaro is used so we can see which steps help and where people get stuck. For this we run our own instance of OpenPanel, an open-source analytics tool, on a server we operate in the European Union. Self-hosted means no third-party analytics company receives it. We do not use analytics cookies, and nothing is stored in your browser for analytics.

On the home page, this page, pricing, the sign-up and sign-in pages, the free listing review, the Next Move page and the public playbook pages, your browser reports a page view through our own website: which of these pages was opened and the website you came from, without its path. On the home page and this page it also reports the utm_source, utm_medium, utm_campaign and utm_content labels if the link you used had them; nothing else from the address is sent. On the home page it also reports a click on the main button to sign up or to ask for access, without cookies and in the same way as a page view, with only which of the two buttons it was. It also reports clicks to free Next Move (header, hero or the Next Move section), the first interaction with the product walkthrough (hero, player, chapter or inline control), and which of its four steps you visit. These events contain only those fixed labels, not app links, form values, account identifiers or demonstration content. On the free listing review and playbook chapter pages, we also count clicks to Next Move using a fixed placement label. On the pricing page we count a click on a plan's checkout button, with only the plan and whether it was the monthly or the yearly price. Pricing, sign-up, sign-in, listing review, Next Move and playbook page addresses are sent without query parameters or fragments. Signed-in pages and every other page send nothing. OpenPanel combines your network address and browser type with a value that changes every day into a code used to count visits; we configure it not to keep your network address. It also derives an approximate location (country, region, city) from it.

On our servers we record a few steps in the product: a sign-up was requested, a sign-in was confirmed, an app was added, keyword monitors were added (only how: by hand, from a file, from a suggestion or during sign-up, and whether they were the workspace's first), a Next Move analysis was requested while signed in (only whether it was new or a refresh, and whether it was accepted or why it was refused), an integration was connected (only which provider and whether it was the workspace's first integration) or was refused because the plan does not include it (only which provider), a plan limit was reached (only which limit, such as apps or keyword monitors), the AI visibility, Learnings, Product evidence or Competitors screen was opened, a checkout was started (only the plan chosen and the plan before it), a subscription started, was canceled or ended (only the plan), and a subscription moved to another paid plan (only the plan before it, the new plan and whether it was an upgrade or a downgrade). The keyword, integration, limit, screen, checkout and Next Move steps also carry the workspace's plan. A step taken in your account carries a code derived from your account ID with a secret key, never your email, your name, your app's name, an amount or anything you typed. A subscription step belongs to the workspace, not to a person, and carries a code derived the same way from the workspace; a checkout step carries both.

If your browser sends Global Privacy Control or Do Not Track, we record nothing about you, on public pages or in your account. You can also turn product analytics off for your account in Account settings, under Security; while it is off we record no steps for your account. Subscription steps are about the workspace's billing, not about you, and are recorded regardless of that setting. Analytics records are deleted after 13 months. We rely on our legitimate interest in understanding and improving the product (Art. 6(1)(f) GDPR), within these limits.

Separately, our hosting provider Vercel counts visits to the same public pages with Vercel Web Analytics, without cookies: the page address without its query part, the referring website, country, browser and device type.

Next Move

Next Move reads only public store pages: the App Store or Google Play listing of the app you enter, its public reviews (on the App Store, up to 100 of the most recent reviews in Apple's public feed; on Google Play, the reviews shown on the public page), and, if you add one, one competitor's public listing. It does not connect to your store accounts or read private data. Reviewer names, profiles and photos are not kept; a result quotes only short review excerpts, with email addresses, phone numbers, handles and links removed. The public facts and the goal you choose are sent to an AI model provider to draft the recommendation.

If you are not signed in, pressing Generate starts a separate guest session in this browser. It is not an Indevaro account and gives no access to workspaces. To limit abuse, the network address of a request is stored only as a keyed hash, for 48 hours. We keep a usage record (dates and counts, no content) to apply the free limits.

Time limits, counted from when an analysis is created (opening it does not extend them): an analysis that is not saved can be opened for 7 days; a link to save it to an account works for 24 hours; a saved analysis can be opened for 90 days, or less when your plan keeps history for a shorter time (30 days on Free), and after that only a placeholder with its dates remains in Saved plans. Public store facts, including review text and screenshots, are reused for at most 24 hours. Expired content is then deleted by the cleanup that runs with every pass of the Next Move worker.

Saving an analysis moves it to your verified account; it does not create a workspace or add an app. The save link keeps only a keyed hash of the email address you enter, to match it to your account. Adding the app to a workspace or preparing the move in Indevaro is a separate step you choose.

Feedback is optional: a reason, a report of a wrong fact and, with an account, a short note. When the analysis is deleted or expires, only anonymous counts remain (the reason, the kind of recommendation and the day), without the analysis, its author or the note.

With an account you can choose to share a public summary of an analysis. It contains only the app's public listing facts (such as name, developer, category, version and rating) and a fixed checklist, never your goal, the recommendation, its material, reviews or a competitor you added. Anyone with the link can open it; the page asks search engines not to index it. It stops working when you revoke it, when the analysis is deleted or expires, and after at most 7 days. Copies that others have already saved are outside our control.

To learn whether Next Move helps, we keep a usage record of our own. It notes when a step happens (an analysis is requested, a result is ready, it is saved, the app is added, the move is prepared) and, only while you have a guest session or are signed in, a few page actions: opening a result, the playbook or an outcome, and copying or downloading material. Each entry has a random identifier that is not your account ID, the kind of step, its time and, if the link you arrived from had them, its utm_source, utm_medium, utm_campaign and utm_content labels. It never holds your email, the app you entered, the analysis, your workspace or your network address, and nothing is kept in your browser for it. If your browser sends Global Privacy Control or Do Not Track, page actions are not recorded. Entries about a step also point to the Next Move record they came from until that record is deleted. When your account is deleted, the link between the identifier and your account is removed, and so are those pointers; what remains is the random identifier, the kind of step, its time and the labels. Visits to the public Next Move and playbook pages are counted by our site statistics without cookies and without the address's query part; this record is not shared with them or with anyone else.

You can clear a guest analysis at once with Clear my analysis, and delete a saved one from Saved plans. Deleting your account removes its Next Move analyses, feedback and links. For an export of your saved analyses or account deletion, contact us at the address above. Next Move has no marketing opt-in and adds no one to a mailing list; it sends only the sign-in or save email you ask for.

AI processing

Some features use AI models. Our servers send these requests through Vercel AI Gateway, which forwards each one to the model provider: requests to GPT models go only to OpenAI, requests to Claude models go only to Anthropic, and requests to Gemini models go to Google (through its Gemini API or Vertex AI). Vercel states that it does not train on the content of these requests and deletes it once the request completes; it records request metadata, such as the model, token counts and cost. Under their paid API terms, OpenAI, Anthropic and Google do not use the requests to train their models. They keep them for a limited time to detect abuse: OpenAI generally for up to 30 days, Anthropic for up to 30 days, or up to 2 years for requests its safety systems flag as breaching its usage policy, and Google for up to 55 days on its Gemini API, or up to 90 days for prompts its safety systems flag on Vertex AI. Your browser never talks to a model directly, a request carries only what the feature needs, and our code checks every answer before it is shown. An AI answer is a proposal for you to review; it is never used to make a decision about you.

What each feature sends: Case diagnosis sends a bounded set of the case's facts (measurements, dates and their labels) and up to five of its notes, redacted first, without any workspace, app or account identifier. Drafting material sends the app profile and the plan you are drafting for (its goal and tasks). Keyword ideas send the app's name, description and listing text, your seed and tracked keywords and competitor names. Feedback topics send the text of store reviews and survey answers you import, after email addresses, links, phone numbers, network addresses and similar details are removed. AI visibility checks send questions about your app's market, with the country to answer for, to see which apps the answers mention: either to OpenAI models with web search through Vercel AI Gateway, or through treg to cloro, which returns the answer that ChatGPT, Google Gemini or Microsoft Copilot gives to that question, for each assistant you choose. These requests carry no account, workspace or user identifier. Next Move sends the public store facts, review excerpts and screenshots and the goal you choose, as described in the Next Move section.

We keep the result with the feature that produced it, together with a cost record (model, token counts, price). Error reports never include what was sent to a model or what it answered. We rely on the contract with you for AI features you use in your workspace, and on our legitimate interest in providing the free Next Move analysis you request (Art. 6(1)(b) and 6(1)(f) GDPR).

Error reports

When something fails on our servers or in your browser, an error report is sent to our own instance of GlitchTip, an open-source error tracker, which runs on a virtual server we operate at Hostinger in Germany. No error-tracking company receives it. A report holds the error message and where in our code it happened, the page address, the browser and operating system type, the time and the release. For about one in ten page loads and server requests we also send timing data to measure speed.

We configure it not to collect your account details or cookies, to drop sign-in headers and the headers that carry your network address, to drop address values such as tokens, codes and email addresses, and not to record database query values, program variables or console messages; there are no session recordings. Error reports are therefore not meant to contain your network address or who you are. Before a report leaves, our code also removes email addresses, keys, tokens and passwords it recognises in the text. Error reports and timing data are kept for up to 90 days. We rely on our legitimate interest in keeping the service working and secure (Art. 6(1)(f) GDPR).

Who helps us process data

These providers process personal data for us, under our instructions and under the data processing agreement that is part of each provider's terms, except Polar, which sells the subscription to you itself, and treg, which provides its service under its own terms and to which we send no personal data:

Accounts you connect yourself, such as App Store Connect, Google Play, RevenueCat, PostHog or Sentry, are not our providers: we exchange data with them on your instruction, and their own terms apply. If you turn on browser notifications, they are delivered by the push service your browser vendor runs, under the browser's terms; the content is encrypted so that only your browser can read it.

Transfers outside the EEA

Some of these providers are established in, or may process data in, countries outside the European Economic Area, in particular the United States. Vercel, Resend, Google and Cloudflare are certified under the EU-US Data Privacy Framework, and the data processing agreements of Vercel, Resend and Cloudflare also include the European Commission's Standard Contractual Clauses. Supabase's data processing agreement includes the Standard Contractual Clauses. Requests to OpenAI, Anthropic and Google go through Vercel, under our agreement with Vercel. treg is established in, and hosts its service in, the United States and relies on the Standard Contractual Clauses with its own providers; cloro (Malta) relies on the Standard Contractual Clauses for transfers to the United States. We send them no personal data. Hostinger (Cyprus) and DataForSEO (Estonia) are established in the EU, and our Hostinger server is in Germany; where their own subcontractors process data outside the EEA, they rely on the Standard Contractual Clauses or an adequacy decision. You can ask us for a copy of the safeguards at contact@indevaro.com.

Why we process data and on which legal basis

Your email address is needed to create an account and sign in; without it we cannot provide the workspace. Using Next Move without an account does not require you to give us personal details. We do not sell personal data.

How long we keep data

Your rights

Under the GDPR you have the right to access your personal data and get a copy of it (Art. 15), to have it corrected (Art. 16) or erased (Art. 17), to restrict its processing (Art. 18), to receive the data you gave us in a portable format (Art. 20), and to object at any time to processing based on our legitimate interest, including product analytics (Art. 21). We tell the providers above about a correction, erasure or restriction (Art. 19). We make no decisions about you based solely on automated processing that have legal or similarly significant effects (Art. 22).

To use these rights, write to contact@indevaro.com. We answer within one month; if a request is complex we may extend this by up to two more months and will tell you why. Many requests you can also handle yourself: the workspace data controls export and delete workspace data, and Account settings turn product analytics off.

You also have the right to lodge a complaint with a supervisory authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl. You may also complain to the authority in the EU country where you live or work.

Changes to this notice

Indevaro is a tool for businesses and is not directed at children. We will update this notice when what we process changes, and tell signed-in users about material changes before they take effect. Last updated: 26 October 2026.

Back to Indevaro