Privacy Policy for datarefs

Summary

datarefs creates a local, timestamped history of supported Ahrefs Keywords Explorer results that you load during normal use. The extension handles Ahrefs request and response data on your device so that you can review, organize, export, back up, restore, reprocess, or delete that history.

Captured Ahrefs data is stored locally in your browser. The extension does not send captured data to Grigio Ventures, a developer-controlled server, an analytics service, an advertising service, or a data broker. It does not add Ahrefs requests, schedule refreshes, or automate your actions on Ahrefs.

The extension's single purpose

The single purpose of datarefs is to passively capture supported Ahrefs Keywords Explorer result data that the user loads, save timestamped snapshots locally, and let the user review, organize, export, back up, restore, reprocess, or delete that local history.

datarefs observes only supported, allowlisted Keywords Explorer fetch and XMLHttpRequest traffic already initiated by the Ahrefs page as a result of normal user activity. It does not make additional Ahrefs requests, replay internal APIs, bulk-fetch results, schedule data collection, automate page actions, or collect data from other websites.

Information handled by the extension

Chrome Web Store data categories

Chrome describes the information datarefs handles as Web history, User activity, and Website content. These categories apply because the extension retains applicable Ahrefs page/request context and capture time, observes allowlisted Keywords Explorer network activity, and stores the supported query and response content locally. datarefs does not record clicks, keystrokes, mouse movements, or scrolling.

Ahrefs request, response, and page context

For supported Keywords Explorer result loads, datarefs may handle and store:

• the request method;
• the sanitized Ahrefs origin and path;
• allowlisted query parameters and JSON request-body context needed to identify the result scope;
• the HTTP response status;
• the unnormalized JSON response returned by the supported Ahrefs request;
• the applicable Ahrefs page origin, path, and allowlisted query context;
• whether the response was observed through fetch or XMLHttpRequest;
• request-instance, correlation, start, observation, capture, and storage timestamps.

The raw JSON response is retained because it is the source of truth for reprocessing, validating, and exporting a snapshot. A supported response may contain fields returned by Ahrefs in addition to the metrics displayed in the datarefs history interface.

datarefs does not store request or response headers, cookies, Ahrefs passwords, authentication tokens, keystrokes, mouse movements, or scrolling activity.

Keyword queries, results, and derived fields

Depending on the supported Keywords Explorer surface, datarefs may derive and store:

• seed keywords or the applicable keyword-list view;
• Ahrefs database/country and search-engine context;
• filters, sort settings, and initial-page pagination context;
• keyword rows and metrics supplied by Ahrefs, such as search volume, keyword difficulty, cost per click, clicks, clicks per search, return rate, traffic potential, parent topic, search intent, SERP features, and freshness data;
• supported overview metrics and compatible legacy SERP position data;
• parsed record counts and surface/profile identifiers.

datarefs does not infer metrics that Ahrefs did not supply for the captured surface.

Capture and integrity metadata

Each stored snapshot may include:

• a snapshot identifier;
• capture and storage timestamps;
• extension, capture-rule, parser, parsed-schema, and export-schema versions;
• capture path, result-set keys, surface/profile information, and status;
• parse warnings or other bounded processing warnings;
• a SHA-256 integrity digest and raw byte length.

Local organization data

If you use saved research groups, datarefs stores the group names you create, their local identifiers and timestamps, and the assignment between a group and a snapshot. This organization data does not change the immutable captured snapshot.

Temporary capture-failure state

When a supported load cannot be captured completely, datarefs may keep a small, session-scoped record containing the affected browser tab/document identifier, a failure code, and a timestamp. This lets the toolbar badge and popup explain that the load was not recorded across Manifest V3 service-worker suspension. This state is temporary browser-session data and is not part of snapshot history.

Incomplete capture payloads are discarded and are not stored as snapshots.

How the extension uses information

datarefs uses the information described above only to provide or improve its single purpose, including to:

• identify complete supported Keywords Explorer result loads;
• create and display timestamped local snapshots;
• preserve raw data so parsed fields can be checked or re-derived;
• present current-result and history views;
• organize snapshots into local saved groups;
• generate user-requested CSV and raw JSON exports;
• generate and restore user-requested NDJSON backups;
• validate snapshot identity and integrity;
• display capture failures, parse warnings, storage status, and other local operational feedback;
• maintain incomplete local transfer chunks across service-worker suspension and remove stale incomplete chunks.

Storage and security

Local snapshot storage

Snapshot history, raw response JSON, parsed fields, capture metadata, saved groups, and group assignments are stored in extension-owned IndexedDB within your Chrome/Chromium browser profile. datarefs requests persistent browser storage to reduce the risk of browser quota eviction.

The extension enforces a 30 MiB logical cap on canonical raw snapshot history. If a new capture or import would exceed that cap, datarefs rejects the new write. It does not silently delete older snapshots to make room. Existing over-cap history remains available for export or explicit deletion.

Local data is subject to the security of your device, operating-system account, and browser profile. datarefs does not add application-level encryption to its IndexedDB records or exported files. Anyone with access to your unlocked device, browser profile, or exported files may be able to read them.

Session storage

Small per-tab capture-failure state is stored in chrome.storage.session, which is scoped to the current browser session rather than synchronized to a Google account.

No extension-controlled remote storage

The released extension has no Grigio Ventures backend, account system, cloud database, or cloud-sync service. Captured Ahrefs data is not transmitted to Grigio Ventures or uploaded automatically to any third party.

Exports, backups, and imports

datarefs creates files only after you choose an export or backup action. These may include:

• current-result or saved-snapshot CSV exports;
• individual raw-capture JSON exports;
• full local-history NDJSON backup files.

Exported files are saved through the browser's download system to a location under your control. After export, those files are outside the extension's storage and are governed by how you store, copy, share, or delete them.

When you choose to import a datarefs NDJSON backup, the extension reads and validates the selected local file and merges valid snapshots into local IndexedDB without sending the file to Grigio Ventures.

Saved research-group metadata is local organization data and is not included in the current snapshot backup format.

Sharing and disclosure

datarefs does not sell captured information. It does not share or transfer captured information to advertising platforms, analytics providers, data brokers, information resellers, lenders, or other third parties. It does not use captured information for personalized advertising, retargeting, creditworthiness, or lending decisions.

Because captured information remains on your device, Grigio Ventures personnel cannot read it through the extension. If you voluntarily send specific content or an exported file to Grigio Ventures for support, you are consenting to the review of the specific information you provide for that support request. Do not send a backup or raw capture unless you intend to share its contents.

Grigio Ventures may disclose information that you voluntarily provide directly when required by applicable law or when necessary to protect security and prevent fraud or abuse. The extension itself does not contain an automatic mechanism for such disclosure.

Retention and deletion

Stored snapshots remain in local IndexedDB until you explicitly delete them, clear the extension's browser data, or remove the extension and its data from the browser. datarefs does not silently expire or prune snapshot history.

You can inspect saved snapshots, inspect their raw JSON and capture metadata, export them, and delete individual snapshots from the extension's history interface. Deleting a saved research group removes the group and its assignments but does not delete the snapshots that were in that group.

Session-scoped capture-failure state is temporary and does not become durable history. Incomplete stale transfer chunks are periodically removed as local maintenance and never become snapshots.

Files that you export remain wherever you saved or copied them until you delete them. Grigio Ventures cannot delete files or extension data from your device on your behalf.

If you email Grigio Ventures, the message and information you provide may be retained as reasonably necessary to respond, maintain support records, protect security, or meet legal obligations.

Extension permissions

datarefs uses these Chrome extension permissions only for its disclosed single purpose:

Access to https://app.ahrefs.com/*

This access lets two packaged, top-frame scripts run at page start on the Ahrefs application origin. A main-world observer reads only allowlisted Keywords Explorer fetch/XHR requests and JSON responses already loaded by Ahrefs. An isolated coordinator validates complete captures and passes them to extension-owned local storage. The origin-wide match is needed because Keywords Explorer pages and API routes use the same Ahrefs application origin.

datarefs ignores unrelated Ahrefs traffic, has no access to other websites, and does not issue Ahrefs requests.

storage

Used for small, temporary per-tab capture-failure state in chrome.storage.session, so the popup and toolbar badge can report a failed capture across Manifest V3 service-worker suspension. Snapshot history is stored locally in IndexedDB, not synchronized through chrome.storage.

downloads

Used for user-initiated CSV, JSON, and NDJSON exports and to report whether a requested download completed or was interrupted.

alarms

Used for local maintenance that must survive service-worker suspension: clearing temporary badge attention and periodically removing incomplete, stale IndexedDB transfer chunks. Alarms do not schedule network requests, Ahrefs refreshes, browsing activity, or snapshot deletion.

unlimitedStorage

Used to reduce the risk that the browser evicts the extension's local IndexedDB history. datarefs still enforces its own 30 MiB logical raw-history cap and does not use this permission for cloud storage or synchronization.

Chrome Web Store Limited Use compliance

datarefs's use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. datarefs uses handled information only to provide or improve the extension's disclosed single purpose. It does not use, sell, or transfer handled information for unrelated purposes, personalized advertising, data brokerage, creditworthiness, or lending.

See the Chrome Web Store User Data Policy.

The datarefs website

The public datarefs website is a static site hosted by GitHub Pages. Grigio Ventures does not add analytics, tracking pixels, advertising, cookies, forms, externally hosted fonts, or other third-party embedded resources to the site. The website does not receive or have access to the Ahrefs data stored by the extension.

GitHub necessarily processes ordinary technical request information when it serves the website, such as an IP address, user agent, requested URL, and request time, in accordance with GitHub's own practices. See the GitHub Privacy Statement.

If you select the email link on the website, your email application and mail providers process the message. Grigio Ventures receives the address, content, and other information you choose to include in that email.

Changes to this policy

Grigio Ventures may update this policy when datarefs features, data practices, permissions, hosting, or legal requirements change. The revised page will show an updated “Last updated” date. If extension data handling changes, Grigio Ventures will provide disclosures and obtain consent as required by applicable Chrome Web Store policy and law before applying the new practices.

Contact

For questions or privacy requests concerning datarefs, contact:

datarefs is an independent product and is not affiliated with or endorsed by Ahrefs. Ahrefs is a trademark of its respective owner.