Privacy policy
Effective 2 November 2026.
DirectoryLens (directorylens.com) is a Search Console analytics tool for directory websites. This policy explains what data DirectoryLens accesses, how it is used, where it is stored, who it is shared with, and how to delete it.
Data we access
- Google account basics. When you sign in with Google we receive your name, email address and Google account ID. We use them to create and identify your DirectoryLens account.
- Search Console data. When you connect a Google account, you grant read-only access to Google Search Console (scope
https://www.googleapis.com/auth/webmasters.readonly). With it DirectoryLens reads the list of Search Console properties that account can see and, for properties you add to DirectoryLens, their search performance data (queries, pages, clicks, impressions, CTR, position, country, device), sitemap lists and URL Inspection results. - Data you enter. Workspace names, page-type rules, categories, brand terms, listings and notes you add.
- Public pages of your site. For properties you add, DirectoryLens may fetch public pages and sitemaps from that site, following its robots.txt.
How we use it
- To show you reports and analyses about your own properties, and to keep their history over time.
- To keep your connection working: we store an OAuth refresh token so data can be synced daily without you signing in each time.
- We do not use Google user data for advertising, we do not sell it, and we do not use it to train general-purpose AI models.
- DirectoryLens never writes to your Search Console account. The only exceptions are actions you start yourself and confirm, such as submitting a sitemap.
Who can see it
- Data for a property is visible only to members of the DirectoryLens workspace that added it.
- If you create a share link for a report, anyone with that link can see that report until you revoke it.
- DirectoryLens staff do not read your data, except with your permission (for example, to help with a support request), when needed for security, or when required by law.
Who we share it with
We use these service providers to run DirectoryLens. They process data on our behalf and only to provide their service:
- Supabase: database and sign-in (United States).
- Vercel: hosting.
- Anthropic (Claude API): only if you turn on an AI feature. These features are off by default. When on, the data needed for that feature (for example, search queries for classification) is sent to the Claude API.
We do not share Google user data with anyone else, except where required by law.
Google API Services User Data Policy
DirectoryLens's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and security
- Data is stored in a Postgres database hosted by Supabase in the United States, with row-level access rules that keep each workspace's data separate.
- OAuth refresh tokens are encrypted (AES-256-GCM) before they are stored, and are never logged.
- All traffic uses HTTPS.
Retention and deletion
- We keep Search Console data for as long as the property stays in your workspace, because long-term history is what the product is for.
- Disconnecting a Google account in DirectoryLens revokes its token with Google and deletes the stored token immediately. You can also remove access at any time from your Google account permissions.
- Deleting your account or a property's data: email privacy@directorylens.com and we will delete it within 30 days.
Cookies
DirectoryLens uses your browser's local storage to keep you signed in and remember your theme, and a short-lived cookie to protect the Google connection step. We do not use advertising or tracking cookies.
Changes
If we change this policy we will update the date above, and tell signed-in users about material changes before they take effect.
Contact
Questions or requests: privacy@directorylens.com.