We do not sell personal data or run advertising trackers. A free account lets you continue past the first catalog page and save private research.
If you sign in, we store your account identity and the research you save. Official keyword sample reports are public. Private report and request records are separated by account and excluded from the public catalog. Pro purchasing and new user queries are not open yet.
Using the public site
The first page of each catalog search, app details, official sample reports and published research can be read without an account. Continuing past page one requires free sign-in. The application stores filter state and login continuation in the URL and session storage; local browser storage remembers your authentication session and the pricing period you select.
Cloudflare processes ordinary request data such as IP address, user agent, requested URL and security signals to deliver and protect the site. This is infrastructure logging, not an advertising profile.
The private preview additionally uses Cloudflare Access to restrict entry and verify an allowed email address. This preview gate is separate from the optional Supabase account used for saved research and keyword-query permission.
Optional account data
Sign-in is handled by Supabase Auth. Depending on the method you choose, the authentication service may process your email address, Google account identifier, session tokens and security metadata. The site never receives or stores your Google password.
When you use the private workspace, we store:
- the account identifier needed to separate your data from another user's;
- favorite app records and private notes you enter;
- saved catalog filters and the names you give them;
- timestamps needed to show and update those records.
These records are stored in Supabase, protected by database row-level policies and excluded from the public catalog. Signed-in keyword eligibility is checked with Supabase using your session token and confirmed email address.
Official samples and private Google research
The site prepared the official public samples from selected App Store listings. Their phrases, keyword estimates, dates and sources can be read by other visitors. Free users cannot submit new queries. Pro purchasing is not open; when private research becomes available, it will require verified paid access and an explicit submission. Opening an app, editing a phrase or reading a report does not itself send a query to DataForSEO.
A new query sends selected seed phrases, country, language and search options from our server to DataForSEO under the site’s provider account. The current research scope is United States and English. The keyword payload does not include your Supabase account ID, sign-in email, favorites, saved filters or private notes.
Cloudflare D1 stores official sample reports separately from account-owned reports. A private report includes its owner ID, app ID, normalized research phrases, keyword results, market, language and capture time. Private results and phrases are returned only after verifying the owner's session and do not overwrite or become public sample reports.
Do not put personal information or confidential material in research phrases. A private report remains processed by the external keyword provider. Private notes are not sent with a keyword query.
Private keyword request records
A submitted new query creates a private record in Cloudflare D1 containing the account ID, app ID, request ID, period, timing, query status and submitted phrases and options needed to identify duplicate requests. Usage and provider cost records enforce account and platform limits and help prevent duplicate provider charges. Future verified subscription identifiers and paid-period dates are stored separately from public data; card details will not be stored by this application.
The request record is not included in the public report or public API responses. Reading a saved report does not create a new paid-query record. A failed or interrupted query may retain its record because the provider may already have processed it.
Why we use it
- To authenticate you and keep your session active.
- To save and restore the research you explicitly ask us to keep.
- To serve official samples, keep account research private, verify query permission, enforce usage limits and prevent duplicate charges.
- To investigate abuse, security incidents and service failures.
- To answer access, correction or deletion requests sent to the contact address above.
Service providers
Cloudflare hosts and protects the site and stores the catalog, official samples, private keyword reports and request records. Supabase handles account sign-in and stores favorites, private notes and saved searches. Resend delivers sign-in emails and processes the destination address and message content needed to send your code. DataForSEO processes submitted keyword payloads and returns search estimates. Browsing does not create a new keyword request.
Each provider has its own data-handling terms. This application does not set a deletion schedule for DataForSEO’s own records. See the DataForSEO privacy policy for its notice; the site’s 30-day report freshness window is not a promise about that provider’s retention.
App icons load from the image addresses captured in the App Store listings. The image host receives your IP address and ordinary request metadata when your browser loads an icon; these requests omit the page referrer. Opening an App Store link takes you to Apple's service and is governed by Apple's privacy policy.
Retention and deletion
Favorites, private notes and saved searches remain until you remove them or request account deletion. Authentication and infrastructure log retention follows the providers’ settings and policies; this page does not claim a single fixed period for those separate systems.
The 30-day keyword cache controls freshness, not deletion. Older official reports remain readable and are labelled stale. Each private report has its own ID; a new report does not overwrite the public sample or previous private versions. You can delete a private report from your history. Request and usage records remain for duplicate-charge protection and support; there is no automatic age-based purge of these records.
This version has no self-service account-deletion button. Send an access, correction or deletion request from your account email to hello@saasnichefinder.com. Specify whether it concerns your account, private saved research, query records or personal information accidentally included in a shared report. We will verify the request, identify the records we control and confirm the action taken.
Removing a favorite or deleting a Supabase account does not automatically remove official samples or separate D1 report and request records. These are checked during account-deletion handling. We cannot recall downloaded copies or promise deletion from a provider's systems through a local action.
Your choices
You can browse without signing in, sign out at any time, clear local browser state, or ask for access, correction or deletion of account data. You may also object to processing or ask a question about where data is stored.
We do not use personal data for automated decisions that produce legal or similarly significant effects.
Changes to this policy
31 October 2026: clarified public samples, free catalog access, login continuation, planned Pro availability and the separation of private reports from public data.
28 October 2026: added DataForSEO keyword requests, the distinction between shared reports and private query records, and the difference between cache freshness and data deletion.
If the data model, providers or tracking practices change, this page will be updated and its effective date changed. A material change will be described on the page rather than hidden in a generic site rebuild.