Privacy Policy

Effective Date: October 26, 2026
Last Updated: November 17, 2026

aiaq respects your privacy and is designed to keep the checks you run under your control.

This Privacy Policy is for the Android application only. It explains how the aiaq SEO & AEO Android app (“aiaq SEO & AEO,” “the App,” “we,” “us,” or “our”) handles information when you use the App on your phone.

This is the on-phone app. SEO, AEO, and keyword tools run on the device. The phone does not send the URL, domain, keyword, or text you enter to an aiaq server. aiaq does not keep a server copy of that run.

The App is an on-phone toolkit for SEO checks, answer-engine checks, and keyword checks. It shows ads through Google AdMob and measures how the App is used with Google Analytics for Firebase. It does not host your website, sign you into search engines, guarantee rankings, or provide a cloud account for your work.

The developer is aiaq. The app name on Google Play is aiaq SEO & AEO. The package name is io.aiaq.app.

1. Contact Information

aiaq

Email: support@aiaq.in

For privacy-related questions, requests, or concerns, contact us at support@aiaq.in.

2. Privacy-First Design

aiaq SEO & AEO is designed primarily as a local, on-device application.

Your tool history and credits are stored on your device rather than in an aiaq-operated cloud account.

The App does not require you to create an online account in order to use the tools.

In the current version of the App:

  • aiaq does not operate a cloud database of your checks, keywords, page text, or history.
  • aiaq does not automatically upload your tool results to aiaq servers.
  • aiaq does not ask you to sign in.
  • aiaq does not ask for a password, PIN, or one-time code.
  • aiaq does not connect to your own Google Search Console, Google Analytics, ads, hosting, or registrar account.
  • aiaq does not sell your personal information.
  • aiaq does not use your keywords, URLs, page text, or history to build an advertising profile.
  • aiaq uses Google Analytics for Firebase to understand how the App is used. It does not record the URLs, domains, keywords, or page text you enter. See Analytics.
  • aiaq does not include a crash-reporting service.

3. Information You May Enter Into the App

When using the App, you may voluntarily enter information such as:

  • A website address or domain name.
  • A keyword or a list of keywords.
  • Page text, a title, or a meta description you want a tool to review.
  • A number of pages or a crawl limit for a check that offers one.
  • Other text a tool form asks for so it can run the check you requested.

This information is used on your device to run the tool you chose, to show the result, and, when a run finishes, to keep a history entry on the phone.

aiaq does not receive or store the URL, domain, keyword, or text you type. It stays on your device, with these exceptions: a tool sends the address, domain, or keyword to the public service that answers the check you asked for, as described in What Happens When You Run a Tool; and you may save a report, share a file, or include it in an email you send to support.

4. Files You Choose

Some tools let you pick a file on the phone, such as an image for the favicon generator or a text file for keyword clustering.

You choose the file in the Android file picker. Choosing one file does not give the App access to every file on the device.

The selected file is read so the tool can do the job you asked for. The current version does not upload that file to an aiaq server.

The App does not scan your photo library in the background.

5. Information Stored on Your Device

The App stores application information locally on your Android device. Android backup of this App’s data is turned off, so a system cloud backup is not used to keep a copy.

Local information may include:

  • Tool history: the tool name, the time, a short label of what you submitted, and the result text.
  • Credits: today’s remaining balance, the day’s transaction list, and how many finished credit videos were counted today.
  • A one-time permission to run a tool after a rewarded video, used only for that run.
  • App preferences needed to show the screens.
  • A short in-memory cache of a recent check, discarded when the App process ends.
  • Data that Google Analytics for Firebase keeps on the phone until it is sent, such as a random app instance ID and recent usage events. See Analytics.

Credits reset each local calendar day. Unused credits do not carry over. The credit record is not an account and is not sent to aiaq.

Because this information is stored locally, access to your unlocked device may provide access to your history. You are responsible for the security of your device, including a screen lock and system updates.

6. Data We Do Not Automatically Collect

The current version of the App is not designed to automatically collect and transmit the following information to aiaq:

  • Your name, email address, or phone number.
  • Your tool history.
  • The URLs, domains, keywords, or page text you enter.
  • Files you select in the file picker.
  • Your contacts.
  • Your SMS messages.
  • Your call history.
  • Microphone recordings.
  • Camera recordings.
  • Your precise geographic location.
  • Your photos or videos, except a file you deliberately select for a tool.
  • Your installed-app list.
  • Passwords, PINs, one-time codes, or other account credentials.
  • Payment card numbers. The App has no purchases.

The App does not request the device location permission. An advertising partner may still derive an approximate location from an IP address when an ad is requested. That is described in the Advertising section.

The App does not intentionally collect the categories above unless a future feature expressly requires them and this Privacy Policy is updated first.

The usage events the App sends to Google Analytics for Firebase do not include any of the items above. They are described in Analytics.

7. Device Permissions

The App requests only the device capabilities its features need.

  • Internet, so a tool can request the public page, DNS record, or certificate you asked it to check, and so Google AdMob can load advertisements when the device is online.
  • Network state, so the App can tell when the internet connection is off and hide ads in that state.
  • Advertising ID and Android ad services (advertising ID, ad attribution, and ad topics). These are added by the Google Mobile Ads SDK and Google Analytics for Firebase so they can read the Android advertising ID and use Android’s privacy-preserving ad features. They do not show a permission prompt. You control the advertising ID in Android settings.
  • Wake lock and foreground service, added by Google Play services and Firebase so that usage events and ad requests can finish sending in the background.
  • Install referrer, so Google Play can tell Firebase which store listing or campaign led to an install.

Depending on the Android version, system screens may also let you:

  • Select a file for a tool that needs one.
  • Save a report into Downloads.
  • Open an email application to contact support.
  • Open an external link.

The App does not request access to your contacts, camera, microphone, SMS, phone state, or precise location. It does not require broad storage access merely to open one file you select or to save one report.

8. Reports You Save

If you save a finished report, the App writes that file to Downloads on the phone.

A saved file can contain the result of the check you ran. Treat it as your own record.

Deleting history inside the App does not delete a file already saved in Downloads. You delete that file yourself.

If you later send that file through email, cloud storage, or another app, that service’s privacy policy applies. aiaq does not control those services and does not keep a copy of the file.

9. What Happens When You Run a Tool

SEO, AEO, and keyword tools run on the phone. The App does not send the check to an aiaq server, and it does not pass the keyword or page to a rank-tracking service through aiaq. Generators that only rewrite or build text you typed also run on the phone and do not send that text to aiaq.

When a tool needs outside information, the phone asks the public service that holds it directly:

  • A page, sitemap, robots.txt file, or certificate: the website you named.
  • A DNS record: a public DNS-over-HTTPS resolver run by Cloudflare (1.1.1.1) or Google (8.8.8.8).
  • WHOIS / RDAP: public domain and IP registries, such as rdap.org, Verisign, ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC.
  • Keyword research and long-tail ideas: public search suggestion services from Google, YouTube, Bing, Amazon, and DuckDuckGo. The keyword you entered is sent to them as the search text.
  • Keyword position: public search result pages from Bing, DuckDuckGo, and Brave Search. The keyword is sent as the search. The domain you entered is compared with the results on the phone and is not sent to the search engine.

Each request includes only what that service needs to answer it: the address, domain, or keyword you asked the tool to check. The connection uses HTTPS where the service supports it.

Those parties are not aiaq. Their own logs may record the request, including your IP address, under their own policies. The App does not sign you into those services and does not send your history with the request.

A failed run is not saved as a successful result and is not charged a credit.

10. Support Communications

If you contact us at support@aiaq.in, we receive the information you voluntarily include.

This may include:

  • Your email address.
  • Your name, if you include it.
  • Your message.
  • Screenshots or files you choose to attach.
  • Device or App details you choose to provide.

We use support communications to respond to your request, investigate a reported problem, provide customer support, improve the App, and address security or privacy concerns.

Do not send passwords, API keys, recovery codes, or other account-security credentials to support.

The email service that carries the message may process it under that service’s own privacy policy.

11. Analytics

The App uses Google Analytics for Firebase, a service provided by Google, to understand how the App is used. It helps us see which tools are used, which fail, and how ads and credits perform, so we can improve the App. The App does not include a crash-reporting service.

What is collected

Firebase records some events on its own, such as the first time you open the App, app updates, sessions, uninstalls, and ad impressions. The App also sends these events:

  • Which screen or tool you open.
  • When a tool run starts, succeeds, fails, or is cancelled, the type of error, and how many seconds it took.
  • How many credits a run used or a video added, and the balance afterwards.
  • Rewarded video requests and whether the video was watched to the end, and when an interstitial or native ad is shown or not available.
  • When you download or copy a result, the file type, and History actions such as view, delete, or clear.
  • When the device goes offline.

Each event carries the tool name and simple values, such as a credit count, a file type, or an error type. The App does not send your URLs, domains, keywords, page text, files, or the content of your history or results to Firebase.

Firebase also processes device and app information, such as a random app instance ID, the Android advertising ID, device model, operating system version, app version, language, and an approximate location derived from your IP address.

How it is used

We use this information only in aggregated reports to improve the App. We do not use it to identify you, we do not combine it with a name or an email address, and we do not sell it. Google processes this information under its own privacy policy, described at https://policies.google.com/technologies/partner-sites.

The App does not use your keywords, URLs, or history for behavioral advertising.

12. Advertising

The App contains ads. They are third-party advertisements served in the Android app through the Google Mobile Ads SDK (AdMob), so the tools can stay free. The App declares that it contains ads. Ads are marked as advertisements and are separate from the tool results.

How ads look in the App

Native ads appear only on a tool page, not on the SEO, AEO, Keywords, History, or Credits tabs. There is one reserved card under the form, and a second reserved card above the questions when that tool has questions. Each card is about 220 density-independent pixels tall. A loaded native ad typically shows a media image or video, a headline, the advertiser name, a call-to-action button, and Google’s ad mark. If the device is offline or no ad is available, that space is not shown as an empty strip.

A full-screen interstitial covers the App until you close it or the system Back key dismisses it. One may appear about 40 seconds after you open the App, unless you start a tool before that timer ends. If you start a tool first, that opening interstitial is not shown. Another full-screen interstitial may appear after a tool finishes successfully. A failed run does not show that interstitial. An interstitial is not shown while a tool is still running.

A rewarded ad is a full-screen video you choose to watch. On the Credits page, a video that plays to the end can add 2 credits. Closing it early does not add credits and does not use that day’s slot. Finished credit videos are limited to 5 per local calendar day. From the out-of-credits message, a finished video can run that one tool and does not add credits. It does not use the 5-per-day credit-video slot.

aiaq does not send your URLs, domains, keywords, page text, files, or history to AdMob or to other advertising networks. Our AdMob account is linked to Google Analytics for Firebase, so the usage events described in Analytics, which include credit counts but no URLs, keywords, or page text, can also be used by Google to measure ads.

aiaq does not use that information to build an advertising profile and does not sell it to advertising companies.

Google AdMob may process limited technical information to serve, measure, and protect ads. Following Google’s disclosure for the Google Mobile Ads SDK, that can include:

  • IP address, which may be used to estimate an approximate location. The App does not request precise location.
  • Product interactions, such as app launch, taps, and video views.
  • Diagnostic and performance information related to the SDK, including launch time, hang rate, and energy use.
  • Device or other identifiers, including the Android advertising ID and the app set ID. If you are signed into Google on the device, Google may also process identifiers related to that signed-in account.

Google may use that information for ad delivery, measurement, frequency capping, aggregated reporting, fraud prevention, and related advertising operations, subject to Google’s policies and your Android ad settings.

aiaq sees only aggregated advertising reports, such as impressions and earnings. We do not combine advertising data with a name or an email address, because the App does not collect those. We do not use the app set ID to personalize or measure ads. Google’s SDK may use the app set ID for fraud prevention and analytics. That use is disclosed here as required by Google Play.

Advertising traffic uses encrypted connections (TLS).

Google may also store temporary ad files in the App’s cache on the phone. Clearing the App cache can remove those files. It does not delete your history or credits. See Deleting Your Data.

You can reset or delete the Android advertising ID in your device settings, typically under Settings > Privacy > Ads, or under Google > Ads on some phones. On newer Android versions you can delete the advertising ID. After you delete it, apps that request it receive a string of zeros instead of a personalised identifier. Google’s advertising practices are described at https://policies.google.com/technologies/ads. How Google uses information from apps that use its services is described at https://policies.google.com/technologies/partner-sites. Google’s privacy policy is at https://policies.google.com/privacy.

The App is intended for users aged 18 and older. It is not a child-directed app, and its ads are not child-directed. Children are not part of the target audience. See the Children section.

In accordance with Google Play’s Data Safety requirements, device or other identifiers used for ads, including the Android advertising ID, are processed by Google for third-party advertising, measurement, and fraud prevention. Approximate location may be inferred by Google from the IP address. Google Analytics for Firebase also reads the advertising ID to measure app usage, as described in Analytics.

In the European Economic Area, the United Kingdom, and Switzerland, the App shows Google’s certified consent message (Google User Messaging Platform) the first time you open it, before any ad loads. You choose whether Google and its ad partners may use your data for personalized ads and related purposes. If you do not agree, you may still see ads that are not personalized. You can change your choice at any time under Credits > Ad privacy choices, which appears where this message applies. You can also limit ad personalization in Android settings and in Google’s ad settings.

13. Cookies and Web Tracking

The App is an Android application. It is not a website, and it is not intended to use cookies to track you across unrelated websites.

The App does not show a website cookie banner. It is an Android application, not a website.

The App does not intentionally create a cross-app or cross-site tracking profile of you.

14. Android System WebView

The App’s screens are shown with Android System WebView. The interface is bundled with the App and loaded on the device.

Android System WebView is a system component. Depending on your device and Android settings, Google or the device maker may process limited technical diagnostic information about WebView. That system processing is controlled by the platform provider. It is not aiaq collecting your tool history.

When you run a check, the phone may request the public address you entered. That request is a tool fetch. It is not a sign-in to that website, and it is not used as the App’s own interface.

15. Google Play

If you install the App from Google Play, Google may independently process information about installation, device compatibility, security, crashes reported by Play, and other Play services.

Google’s handling of that information is governed by Google’s own terms and privacy policies. aiaq does not control information collected independently by Google Play.

16. Third-Party Services

The current version uses these outside services only in the ways described above:

  • Google AdMob, to show ads when the device is online.
  • Google Analytics for Firebase, to measure how the App is used.
  • Public search suggestion services (Google, YouTube, Bing, Amazon, and DuckDuckGo) and search engines (Bing, DuckDuckGo, and Brave Search), when you run a keyword tool.
  • Public DNS resolvers (Cloudflare and Google) and domain registries, when you run a DNS or WHOIS check.
  • The public website, DNS resolver, or certificate host you ask a tool to check.
  • Your email provider, if you write to support@aiaq.in.
  • Another app you choose, if you open or share a file you saved.

Once you intentionally send information to a third-party app or service, that party’s privacy policy applies. aiaq is not responsible for the privacy, security, or availability of those services.

17. Sale of Personal Information

  • aiaq does not sell your personal information.
  • aiaq does not sell your tool history.
  • aiaq does not sell the URLs, keywords, or files you enter.
  • aiaq does not sell personal information for cross-context behavioral advertising.

18. Sharing of Information

Because the tools are designed to run on the phone, aiaq does not routinely receive your checks and therefore does not routinely share them.

Information may leave your device when:

  • A tool requests the public site, DNS record, certificate, or registry record you named.
  • A keyword tool sends your keyword to a public search or suggestion service.
  • Google AdMob loads or measures an ad.
  • Google Analytics for Firebase sends usage events.
  • You save a report and then send that file somewhere else.
  • You email support.

If we actually hold information, such as a support email, we may disclose it where reasonably necessary to comply with law, respond to valid legal process, protect the rights and safety of aiaq, our users, or others, or investigate fraud, abuse, or a security incident.

That does not mean aiaq keeps a server copy of your local history.

19. Data Retention

On the phone

History and credits remain on the device until you delete a history entry, clear History, clear the App’s storage (Clear data), or uninstall the App. A report already saved in Downloads remains until you delete that file.

Temporary cache, including cached ad files, can remain until you use Clear cache, Clear data, or uninstall. Clearing cache alone does not remove history or credits.

Clearing the App does not delete files you saved elsewhere, and it does not delete an email you already sent.

Support email

Information you send to support@aiaq.in may be kept for as long as reasonably needed to answer you, keep a support record, prevent abuse, resolve a dispute, meet a legal duty, or protect legitimate interests. We do not intend to keep it longer than those purposes need.

Analytics data

Google Analytics keeps event-level data for 2 months and data linked to an app instance for up to 14 months from its last activity, then deletes it. Aggregated reports that cannot identify a device may be kept longer.

Advertising data

Advertising data collected by Google is kept by Google under Google’s retention rules. aiaq cannot delete Google’s ad logs. Resetting or deleting the advertising ID in Android settings is the control on the device.

20. Deleting Your Data

The App does not create an aiaq account, so there is no cloud account to delete and no account-deletion page. Google Play’s account-deletion URL is not required for this App. You delete what is stored on the phone yourself, using the App or Android settings.

Inside the App

On the History tab you can remove one entry or clear History. That deletes the on-phone history list. It does not reset credits, does not uninstall the App, and does not delete a report already saved in Downloads.

Android cache, storage, and uninstall

Open your phone Settings, then Apps (some phones say Apps & notifications or Application manager), then aiaq SEO & AEO, then Storage. Labels vary by Android version and manufacturer. Use these controls:

  • Clear cache. This removes temporary files the App and Google AdMob stored on the phone, such as cached ad images and WebView cache. It does not delete your tool history, credits, or other App storage. After you clear cache, ads may reload when you are online.
  • Clear storage or Clear data. This is the control that deletes the App’s private data on the phone. It removes tool history, credits, WebView local storage, and other files the App keeps in its own storage. The App stays installed. The next time you open it, credits start again at the daily amount and history is empty. This does not delete a file already saved in Downloads, and it does not delete an email you already sent.
  • Uninstall. Removing the App deletes the same private App data as Clear data, including history and credits. It does not delete a file already saved in Downloads. If you install the App again, it does not restore the old history or credits.

If you only want a smaller cache and you want to keep your history and credits, use Clear cache. If you want to wipe the App’s local records, use Clear storage / Clear data or uninstall.

Analytics

Analytics data is tied to a random app instance ID, not to your name or email address. Clearing the App’s storage or uninstalling the App gives it a new app instance ID, so later events are not linked to earlier ones. Because aiaq cannot connect analytics records to a person, we usually cannot find or delete one person’s events. They are deleted when the retention period in Data Retention ends.

Advertising identifier

Clearing the App cache or App storage does not reset the Android advertising ID. That identifier is a device setting. To reset or delete it, open Settings, then Privacy, then Ads (or Settings, then Google, then Ads). On newer Android versions you can delete the advertising ID. That change applies across apps on the device, not only this App. aiaq cannot delete advertising logs that Google already holds.

If you previously emailed aiaq and want that support message deleted, contact support@aiaq.in. We will handle the request subject to applicable legal, security, and record-keeping limits.

21. Security

The App uses a local-first design so your checks are not uploaded to an aiaq account. Ad requests, analytics events, and HTTPS page fetches are encrypted in transit.

No app, phone, or email can be guaranteed completely secure. You are responsible for your device, your screen lock, files you save, and the email account you use to contact support.

Install the App from a source you trust, and keep Android and Android System WebView updated.

22. Children

aiaq SEO & AEO is intended for users aged 18 and older. It is a professional SEO, AEO, and keyword toolkit. It is not directed to children.

Children are not part of the target audience. In particular:

  • The App is not directed at children under 13.
  • The App is not made for children of any age.
  • The App is not part of Google Play’s Designed for Families program.
  • The App is not a children’s app and is not offered as a family app for children.
  • Ads in the App are not child-directed and are not designed as ads for children.

We do not knowingly design the App to collect personal information from children for advertising, profiling, or any other purpose.

We do not knowingly collect from a child:

  • Name.
  • Email address.
  • Phone number.
  • Precise location.
  • Photos.
  • Contacts.
  • School or other personal details.

The App does not ask anyone to create an account, so it does not create a child’s account. It does not ask for a date of birth. It does not include social features, public profiles, or chat.

We do not use the App to build advertising profiles of children, and we do not sell children’s information. We do not knowingly allow a child to be the audience for personalized advertising.

If you are a parent or guardian and you believe a child has sent personal information directly to aiaq, for example by emailing support, contact support@aiaq.in. We will delete the support information we actually hold, subject to any record the law requires us to keep.

A parent can also remove the App, clear the App’s storage in Android settings, and reset or delete the Android advertising ID under Settings > Privacy > Ads.

23. International Users

The App may be used in different countries.

Because history and credits stay on the device, aiaq ordinarily does not transfer that local information to aiaq servers in another country.

A tool may contact a public website or DNS resolver in whatever country that host is in, because you asked the App to check it.

Google may process analytics and advertising data in the United States or in other countries where Google operates.

If you email support from outside the place where the mailbox is hosted, the message may be processed where the email service operates.

24. European Economic Area and United Kingdom Users

Where the GDPR, UK GDPR, or a similar law applies to information aiaq actually receives, you may have rights to access it, correct it, delete it, restrict it, object to certain processing, and, where the law provides it, receive a portable copy. Where processing is based on consent, you may withdraw that consent. You may also complain to a supervisory authority.

Most tool information in the current App is stored only on your device and is not received by aiaq. The direct way to control it is in the App and in Android settings.

For information you actually sent to aiaq, such as a support email, write to support@aiaq.in.

Advertising data processed by Google is controlled by Google under Google’s policies. We use analytics data on the basis of our legitimate interest in understanding and improving the App, using only events that do not contain the URLs, keywords, or text you enter. For ads, the App shows Google’s certified consent message, and you can change your choice under Credits > Ad privacy choices, as described in the Advertising section. You can also reset or delete the advertising ID to stop it being used for analytics.

25. California and Other U.S. Privacy Rights

Depending on where you live, and whether a law’s thresholds are met, you may have rights to know, delete, or correct personal information, and to opt out of sale or sharing for cross-context behavioral advertising.

aiaq does not sell personal information and does not share your local history for cross-context behavioral advertising.

For personal information aiaq actually received, contact support@aiaq.in. We may need enough detail to verify and handle a request the law applies to.

26. India Privacy Rights

Where Indian privacy or data-protection law applies to information aiaq actually processes, we handle that information in line with those duties.

For a privacy question, a correction, a deletion request, or a grievance about information aiaq holds, contact support@aiaq.in.

27. Automated Checks

The App calculates results on the device from the page, domain, keyword, or text you provide. Those results can include scores, issue lists, keyword ideas, and similar tool output.

These are tools for your own review. The App does not use them to make a legally binding decision about you, to decide creditworthiness, or to place you in a profile held by aiaq.

28. Results and Accuracy

You are responsible for reviewing what you enter and what a tool returns.

A score, a crawl, a keyword count, or a position check can change as the public web changes. A result is not a promise of search rankings, traffic, or revenue. Public sites can block a check. A DNS or certificate result describes what that public service returned at that moment.

29. Changes to the App’s Data Practices

If a future version adds accounts, cloud sync, server-side storage of your checks, crash reporting, payments, or a remote AI service that receives your text, we will update this Privacy Policy and the Play Data Safety disclosures before describing those practices as part of the App.

Where the law or Google Play requires it, we will give additional notice or ask for consent before using personal or sensitive information for a materially different purpose.

30. Changes to This Privacy Policy

We may update this Privacy Policy when the App changes, our data practices change, the law changes, or Google Play or Android requirements change. The updated policy will show a new Last Updated date.

Material changes may also be communicated in the App or another appropriate way where that is required. Review this policy from time to time.

31. Contact Us

For questions about this Privacy Policy or aiaq’s privacy practices, contact:

aiaq
Email: support@aiaq.in

Please do not include passwords, API keys, or other account-security credentials in the message.

32. Summary

aiaq SEO & AEO is built around a simple privacy principle: the checks you run should stay on your phone.

The current Android app keeps history and credits on the device. It does not require an account. It does not sell your information. It is not for children and is not directed at children.

Ads are shown by Google AdMob. Usage is measured with Google Analytics for Firebase, using events that never contain your URLs, keywords, or page text. Google may process an advertising ID, IP address, app interactions, and related diagnostics under Google’s policies. You control the advertising ID in Android settings.

Information leaves the phone when a tool checks a public address you named, when a keyword tool sends your keyword to a public search service, when an ad loads, when usage events are sent to Firebase, when you save and then share a file, or when you email support@aiaq.in.