Privacy Policy

1. Scope and who we are

Search Console for iOS ("the App") and the website at search-console.org ("the Site") are operated by an independent solo developer ("the developer," "we," or "us" in this policy).

This Privacy Policy explains what information is processed when you use the App or Site, how it is used, and what choices you have. It applies together with our Terms of Service.

Not affiliated with Google. The App is an independent client for Google Search Console. It is not made by, endorsed by, or sponsored by Google LLC. Google trademarks belong to Google LLC.

Plain-language note: This policy describes how the App and Site work today. The developer does not run user databases or sell data. Third-party services (Google, Apple) process information under their own policies. This page is not legal advice.

2. Summary

• The developer does not collect App usage data on personal servers. No developer-run user accounts, analytics SDK, or database of Search Console metrics.
• Search Console data stays between you, Google, and your device. The App fetches it from Google and displays it locally.
• The developer does not sell data.
• Third parties process data on their own. Google (sign-in, APIs, AdMob on the free tier), Apple (App Store, subscriptions, notifications), and Google Analytics on this website each follow their own policies.
• Pro subscription (weekly or monthly) removes in-app ads and unlocks every property, the Blink assistant, Core Web Vitals checks, URL inspection, and widgets. Billing is handled by Apple, not the developer.
• Support is optional. Only if you choose to use the Site contact form or in-app feedback or bug report does the developer see what you submit.

3. Google Search Console data

The App displays data from your Google Search Console account. That data originates from Google and reflects what Google collects about your sites and what your Google Account permissions allow.

Depending on the OAuth access level you choose, the App may access:

• Account profile: name, email address, and profile picture for sign-in and display
• Search analytics: clicks, impressions, CTR, average position, queries, pages, countries, devices, and related dimensions
• Properties: site URLs you can access in Search Console
• URL Inspection, sitemaps, and related API features when you use those screens
• PageSpeed / Core Web Vitals for URLs you analyze through Google's PageSpeed Insights API

Search Console data is fetched from Google's servers, shown on your device, and may be cached locally (memory, app storage, iOS Keychain for auth tokens). The developer does not receive, store, or host this data on servers they operate.

You can review or revoke App access at any time:

• Google Account app permissions
• Google Account data and privacy
• Google Privacy Checkup

4. App features and data

This section maps what the App actually offers to how data is handled. Unless noted, data is fetched from Google for display on your device and is not sent to the developer.

Sign-in and access levels

• Google Sign-In (OAuth 2.0) with scopes you approve at onboarding or in Settings (read-only: Search Console read access plus email and profile; optional editing: full Search Console access plus email and profile). If you choose to connect them in Integrations, the App also asks for read-only access to Google Analytics and to Google AdMob reporting. You can connect these from the same or a different Google account, and remove them at any time in the App or in your Google account settings.
• Read-only access (default): view analytics, properties, sitemaps, URL Inspection, and Core Web Vitals
• Editing access (optional): everything in read-only, plus add/remove properties and submit or delete sitemaps where your Google role allows
• Before sign-in: your plan choice (free with ads or Pro trial) and notification preferences may be stored locally until you connect Google

Analytics and reporting (Google Search Console API)

• Overview and property detail metrics: clicks, impressions, CTR, average position
• Search queries and top pages, with filters (date range, country, device, search appearance, and related dimensions supported by the App)
• Insights summaries for your selected property and date range
• CSV and PDF export of reports you generate (exports stay on your device unless you share them)
• Property icons may load from Google's public favicon service using the site domain (display only)

Other Google-backed features

• URL Inspection for index and crawl status of URLs you inspect
• Sitemaps: list and view status; submit or delete only with editing access and sufficient Search Console permissions
• Core Web Vitals via Google's PageSpeed Insights API: URLs you choose to analyze are sent to Google for measurement
• Google Analytics (optional integration): if you connect it and link a Google Analytics property to a site, the App requests visitor figures for that property from Google and shows them on your device
• Google AdMob (optional integration): if you connect it and link an AdMob app to a site, the App requests earnings figures for that app from Google and shows them on your device. This is separate from the ads shown on the free tier
• Integration data stays on your device: access tokens for connected accounts are kept in the device Keychain, and the links between your sites and those accounts are stored locally. The developer does not receive them
• Web Console shortcuts open Google Search Console in your browser for the property you select

Subscriptions and ads

• Free tier (iPhone and iPad): limited to one Search Console property; may show native ads through Google AdMob (Google processes ad-related data under its policies). The Mac app does not show in-app ads.
• Pro subscription (weekly or monthly through Apple StoreKit): removes in-app ads on supported platforms and unlocks multiple properties, the Blink assistant, Core Web Vitals checks, URL inspection, and Home Screen widgets on iPhone and iPad; Apple processes payment data

Widgets and notifications (on your device)

• Home Screen widgets (Pro, iPhone and iPad only): selected property metrics and related display fields (which may include your account email for labeling) stored in on-device App Group storage so widgets can update; not uploaded to the developer
• Notifications (optional): all notifications are created locally on your device; there is no push server. To write them, the App fetches your recent Search Console click totals from Google, on your device, when the App is open and during iOS background refresh. Daily, weekly, or monthly summaries include those figures. Performance alerts are sent only when clicks change by a set amount, and Core Web Vitals alerts only after a PageSpeed check you have enabled. The latest totals and alert history are stored locally on your device and are not sent to the developer. Disable in App Settings or iOS system settings.
• Blink assistant (Pro, supported devices): Blink answers questions about your Search Console data using Apple's on-device language model. Your questions and the data Blink reads are processed on your device and are not sent to the developer or to a third-party AI service. Conversations are kept in memory only and are cleared when you start a new chat or close the App.
• Achievements (optional): progress stored on your device only; unlocking may trigger a local notification if notifications are enabled

Settings and support (optional, user-initiated)

• Language, haptics, motion, and other preferences stored locally
• Clear Cache and sign-out remove local cached data and tokens
• Send Feedback or Report a Bug (optional): if you submit, the App sends your message, subject or summary, device type, OS version, app version, and an optional screenshot you attach through a third-party messaging service the developer uses to receive support. The developer sees what you submit; nothing is sent unless you tap submit.

Platforms

The App runs on iPhone, iPad, and Mac. Google Search Console data stays on your device across platforms. In-app ads and Home Screen widgets are available on iPhone and iPad only (see above). The developer does not operate a backend database of your Search Console content.

5. What the developer collects

What the developer does not collect in the App

As the App operator, the developer does not:

• Collect, purchase, or rent lists of personal information
• Store Search Console metrics, queries, or site data on developer-operated servers
• Run the developer's own analytics or tracking SDK inside the App
• Sell, broker, or share your Google Search Console data
• Build marketing profiles from your App usage

What stays on your device

The App may store locally on your iPhone, iPad, or Mac:

• OAuth tokens (iOS Keychain) so you stay signed in
• Temporary cache of Search Console data for speed
• Your settings, notification preferences, and widget configuration

You can clear cache in Settings or remove everything by uninstalling the App.

Third-party processing (not controlled by the developer)

When you use the App or Site, integrated third parties may process information under their privacy policies. The developer does not receive most of this data and does not control provider logging. The main integrations are:

Review their policies for details: Google · Apple.

If you contact the developer

Only if you choose to use the Site contact form, send in-app feedback, or submit a bug report will the developer receive what you include (for example your name, email address, message text, or basic device and app version details attached to help debug). Submissions are delivered through a third-party messaging service the developer uses for support. That is direct communication from you, not automatic background collection. See Contact at the end of this page.

This website (search-console.org)

• Google Analytics: visit and usage data processed by Google (see Section 7), including a record of clicks on App Store download buttons and where on the page the button was. Google Analytics uses cookies
• Preferences in your browser: your language choice and whether Site sounds are on are saved in your browser's local storage. A service worker caches Site files so pages load faster. Neither is sent to the developer
• Video: the film on the home page is served from this Site. No third-party video player is loaded
• Contact form: if you submit, name, email, and message are sent to the developer through the same server-side support routing as above
• App Store download links: when you click Download on this Site, a lightweight server ping may record approximate region (for example country or city from hosting headers) and a click counter. It does not include your name, email, or Search Console data.

6. How the App works

The App is a client for Google Search Console. It requests data from Google using OAuth scopes you approve, then displays results on your device.

The developer does not use your Google Search Console data for advertising, resale, profiling, or any purpose other than enabling the features listed in Section 4.

Google user data (Limited Use)

Information from Google APIs is used only to provide user-facing App features you request. The developer does not:

• Sell or rent Google user data
• Use Google user data for ads or ad targeting
• Transfer Google user data to data brokers
• Use Google user data for credit, lending, or employment decisions

7. Advertising and analytics (third parties)

Google AdMob (App, free tier)

Without an active Pro subscription, the App may show native ads through Google AdMob using non-personalized ad requests. The developer does not receive ad analytics or user lists from AdMob. The App does not request Apple's cross-app tracking permission (App Tracking Transparency). Google and its ad partners may still process limited device or advertising-related data under their own policies. Subscribe to Pro to remove in-app ads.

AdMob info: Google Privacy Policy · AdMob disclosure

Google Analytics (this website only)

search-console.org uses Google Analytics. The developer does not operate this analytics system; Google processes visit data under its policies. Analytics is your choice. The Privacy button in the bottom corner of every page turns it on or off at any time. For visitors in Europe, and for any browser that sends a Global Privacy Control or Do Not Track signal, analytics stays off unless you turn it on, and nothing is requested from Google until then. Elsewhere it starts on and you can turn it off. Turning it off also removes the Google Analytics cookies this Site set. Advertising features are never enabled on this Site. You can also use Google's browser add-on or browser privacy controls.

8. Third-party services

The App and Site depend on companies other than the developer. They process data under their own terms. The developer does not control and generally does not receive their logs:

• Google - Sign-In, Search Console API, PageSpeed Insights, AdMob ads (free tier), Google Analytics and AdMob reporting (optional integrations), Analytics (Site)
• Apple - App Store, StoreKit, notifications, Keychain, and the on-device language model that powers Blink

Important links:

• Google Privacy Policy
• Google Terms of Service
• Google API Services User Data Policy
• Apple Privacy Policy

9. Storage, security, and retention

• Search Console data: on your device only; clear via Settings > Clear Cache or uninstall
• OAuth tokens: iOS Keychain on your device
• Messages you send: kept only as long as needed to reply, then deleted when no longer needed
• Subscriptions: handled by Apple; see Apple's policies
• Third-party retention: governed by Google, Apple, and other providers' policies

The App uses HTTPS for API calls and iOS encryption for local storage. No system is perfectly secure.

10. Your choices

• Revoke Google access: myaccount.google.com/permissions
• Clear local App data: Settings > Clear Cache, or uninstall the App
• Export Search Console data: use in-app CSV/PDF export or Google's tools
• Manage ads: upgrade to Pro or adjust Google ad settings
• Manage Site analytics: the Privacy button in the bottom corner of every page, browser controls, Google's opt-out add-on, or Global Privacy Control and do-not-track settings
• Push notifications: disable in App Settings or iOS system settings
• Subscriptions: manage or cancel in the Apple App Store account settings

11. Privacy rights

Depending on where you live, you may have rights regarding personal information. Because the developer does not maintain databases of App usage or Search Console data, most requests about that data should go to Google (for Search Console content) or Apple (for purchases and subscriptions).

If you previously sent a support message, you may ask the developer to delete copies still held. Use the contact details at the bottom of this page. The developer will not discriminate against you for exercising privacy rights where the law requires it.

12. California residents (CCPA/CPRA)

This section applies if you live in California.

What the developer collects as a business

The developer does not operate databases that collect App usage or Search Console content. The developer does not sell personal information for money.

The only personal information the developer typically holds is what you voluntarily send through the contact form or in-app feedback or bug report (such as your email address or message text).

Third-party "sharing" (not by the developer)

California law may treat some third-party advertising as "sharing" for cross-context behavioral advertising. That processing is done by Google AdMob and its partners, not by the developer. The developer does not receive those ad logs. For opt-out options, see Do not sell or share and Google's settings.

Google Analytics on this website is operated by Google, not by the developer.

Your California rights

You may have the right to know, delete, correct, opt out of sale/sharing, and non-discrimination. Because the developer does not collect App data on personal servers, many requests will point you to Google or Apple. For anything you sent the developer directly, use Contact at the bottom of this page.

Shine the Light

The developer does not share personal information with third parties for their own direct marketing in exchange for money.

14. EEA, UK, and Switzerland (GDPR)

If you are in the EEA, UK, or Switzerland:

• Search Console data: primarily processed by Google when you use the App; use Google's tools to exercise rights
• Support messages you send: processed only to respond to you
• Ads and Site analytics: processed by Google under its policies; use Google and Apple controls where applicable

You may lodge a complaint with your local supervisory authority. For developer-related requests, use Contact below.

15. Other U.S. state privacy laws

Residents of Colorado, Connecticut, Virginia, Utah, and other states with privacy laws may have similar rights. The developer does not collect App data on personal servers. For questions or deletion of messages you sent voluntarily, use Contact below.

16. International transfers

Third-party providers (Google, Apple) may process data in the United States and other countries under their own transfer mechanisms and policies.

17. Children's privacy

The App and Site are not for children under 13. The developer does not knowingly collect personal information from children. If you believe a child contacted the developer, use Contact below.

18. Google API Services User Data Policy

The App's use of information from Google APIs follows the Google API Services User Data Policy, including Limited Use. Google OAuth data is used only for user-facing App features you open, not for ads or resale by the developer.

19. Changes to this policy

This Privacy Policy may be updated from time to time. The updated version will be posted on this page with a new "Last updated" date. If changes are material, notice may also appear in the App or on the Site.

20. Contact

Questions, privacy requests, or concerns:

Email: info@quackdb.app

You can also use the contact form in the Site footer, or in the App under Settings > Send Feedback or Report a Bug (only if you choose to send something).

For Google Search Console data rights, use Google Account settings first.