Skip to content
AuditFetch

Privacy Policy

Last updated: October 11, 2026

This policy explains how AuditFetch, LLC (“AuditFetch,” “we,” “us,” or “our”) handles personal information through this website, our subscription and fulfillment services, and the limited cloud services used by AuditFetch Local. It does not govern data that a customer processes entirely within its own Local deployment.

Our local-first boundary

AuditFetch Local runs in the customer's environment. Evidence payloads, integration credentials, screenshots, browser traces, mappings, hashes, and local audit history stay there by default. AuditFetch does not receive that content unless the customer deliberately sends it to us, such as in a support request. Release downloads and subscription fulfillment use AuditFetch services. Signed update checks are optional. Cloud license activation and optional telemetry are separate features; their data use is described below when enabled.

Information we collect

  • Contact and inquiry information: email address and anything you include in a message, evaluation request, or subscription-interest form.
  • Purchase and fulfillment information: name, email, organization, plan, subscription identifiers, payment status, and operational details needed to issue a license and deliver a signed package. Stripe processes payment-card data; AuditFetch does not store full card numbers.
  • Service metadata: the limited licensing, update, and optional telemetry fields documented in the product. Optional telemetry is off by default.
  • Website and security data: ordinary request, device, IP-address, user-agent, referral, error, and security logs produced by our hosting and infrastructure providers.

How we use information

We use information to provide and secure the website and services; process subscriptions; fulfill licenses and releases; respond to requests; maintain product integrity; diagnose failures; comply with law; and protect AuditFetch, our customers, and others. We do not sell personal information or use customer evidence to train AI models.

Evaluation requests

If the evaluation form is available, we store the contact and company details, selected workflow, setup readiness, timing, and discovery source you submit. We record a request reference, the privacy notice version, and the time of submission. Our team uses the record to handle your inquiry and record evaluation progress. Activation is recorded from your confirmation or an assisted session, not hidden Local product tracking. Resend sends request notifications and confirmations. An evaluation request does not subscribe you to promotional email. Do not submit credentials or audit evidence.

If you allow campaign attribution, browser session storage remembers limited campaign labels and landing paths for the current tab for up to 24 hours. It can include the first and latest permitted source when you submit a request. You can stop and clear this source using the campaign preference shown on the site. We do not collect advertising click IDs through this form or send contact and company details to advertising platforms. If you separately allow Google Ads measurement, a successful new evaluation request can send a conversion event with an opaque identifier to prevent duplicate counts. That identifier does not contain your request reference or contact details. If you decline, the form still works without stored campaign attribution. A request reference and your preference can be stored for this tab to support confirmation and remember your choice.

We use a keyed hash of the request IP address for temporary abuse limits. The lead record does not include the raw IP address. Hosting providers can retain ordinary security logs. We review unconverted lead records after 12 months without activity and remove them through our retention process. Related email and backups follow the applicable retention process. Purchase records follow the billing retention policy below.

Cookies and analytics

If you allow website measurement, AuditFetch records key page visits, selected button clicks, evaluation-form starts and server-confirmed new submissions. We store only an event identifier, event time, permitted page and action labels, and limited campaign source and creative labels in our existing database. We do not store form contents, raw IP addresses, referrer URLs, query strings or advertising click IDs in measurement events. A temporary keyed IP hash limits abuse and expires after an hour. Reports cover the last 90 days; expired events are removed when new events are accepted. Your choice and source labels remain in this tab for up to 24 hours. You can stop future events with the website measurement preference. This does not delete past records. Declining does not affect the evaluation form. Preview deployments, marked QA tabs and browsers that signal Do Not Track or Global Privacy Control are excluded. Reports are approximate counts of consenting activity, not unique people.

The AuditFetch marketing website loads the Google Ads tag only if you allow Google Ads measurement. Before you allow it, the tag does not load and sends no measurement requests to Google. If you allow it, Google can receive browser and connection information, including your IP address, and use advertising cookies and ad click identifiers to measure our ads. We do not enable personalized advertising or enhanced conversions. We do not send your evaluation form details, request reference, payment details, or Local evidence to the tag. Your choice is stored in this tab for up to 24 hours. Use the advertising measurement preference at the bottom of the page to stop measurement. This clears accessible Google Ads cookies and reloads the page without the tag. It does not remove information already received by Google. See Google's Privacy Policyfor its data practices. This choice is separate from campaign-source attribution. Stripe may use cookies and similar technologies on its hosted checkout and customer-portal pages under its own privacy policy.

Service providers and disclosures

We disclose information only as needed to providers that support our operations, including Vercel (website hosting), Neon (evaluation-request database hosting), Stripe (payments and subscriptions), Resend (transactional email), Google Workspace (business email), Google Ads (optional advertising measurement), Amazon Web Services (licensing APIs and release-package storage and delivery), and GitHub Container Registry (delivery of product container images). Those providers process information under their own terms and privacy commitments. We may also disclose information when required by law, to protect rights or safety, or as part of a merger, financing, acquisition, or transfer of assets with appropriate safeguards.

Update checks

Signed release checks are available in AuditFetch Local 0.1.53 and are off by default. They work with an offline license and do not require cloud license activation. When enabled, a product page or the host update command can request update status. An administrator can select Check now to request a fresh result.

This option requests a signed announcement from releases.auditfetch.com. The service sees the selected release channel and source IP. The request does not send the installed version, an installation identity, a license identifier, credentials or evidence. AuditFetch checks the signature and expiry before using the result. Successful results are cached for up to six hours by default, within the signed expiry. No background schedule performs an update check on its own. Update checks do not download or install a software release.

If the signed-release option is disabled and legacy cloud licensing is enabled, update checks instead use the configured licensing service. That request carries the selected release channel, the installed version, and the source IP visible to the service. It does not carry an installation fingerprint or license identifier. If both options are enabled, the signed-release option takes precedence for update checks. If both are disabled, the installation makes no update-check requests.

License activation and renewal

Cloud licensing is optional and separate from signed release checks. The following describes installations explicitly configured to use a cloud licensing service; it does not imply that public Local purchases require that service. An installation that never activates uses a signed license file, and none of the following activation or renewal behavior applies to it.

Activation is an administrator action. The request carries the license key, an installation fingerprint, an install-salt identifier, the runtime version, the deployment mode, and a request identifier. Where the installation has generated an installation key, it also carries that key's public half and a signature proving possession of the private half, so that later requests can prove continuity with the same installation identity, and a signed license snapshot bound to one installation cannot be reused by another. It may also carry the license formats the installation understands and, when an installation we already know is re-registering, the activation credential it holds.

That signature is not access control, and we do not present it as one. The binding is on the issued snapshot, not on the license key: anyone holding a license key can generate an installation key of their own, produce a valid signature, and register another installation. What limits how many installations one license may register is the installation allowance on the license itself.

The installation fingerprint is a one-way hash of a randomly generated installation identifier and a secret held on that installation. It is not derived from hardware, network address, hostname, or user account, and it cannot be reversed to any of them. It distinguishes one installation from another; it does not describe the machine.

Renewal is automatic and scheduled. While cloud licensing is enabled, the installation checks hourly whether its cached license is due for renewal and contacts the licensing service when it is — about once a day under the current renewal window, and without an administrator present. An administrator can also request a renewal immediately. The request carries the activation identifier and credential, the key identifier of the license the installation currently holds, the runtime version, and the license formats it understands.

What we keep for an activated installation

  • The license grant: plan, status, Stripe customer and subscription identifiers, whether the grant is for a production or non-production installation, and how many installations it allows. We store a hash of the license key, never the key itself.
  • The activation record: hashes of the installation fingerprint, the installation public key, and the activation credential; the runtime version last reported and when; and the times the installation activated, was last seen, and was deactivated.
  • The signed licenses issued to that installation, which are the same documents the installation itself holds.
  • Which installation was seen running under which issued license, with first and last seen times, so a license period can be reconciled against the installations that used it.

We use these to confirm a license is valid and renew it, to enforce the number of installations a license allows, and to know which runtime versions are deployed — the last because a license field can only be relied on once the installations that would receive it are able to honour it.

Activation is not a product-usage telemetry channel. These requests do not report customer content or how the product is used: no evidence, connector credentials, control mappings, audit-log content, file names, host names, or user accounts. The one measurement they do support is the runtime-version count described above, which tells us which license formats the installed base can honour. Optional product telemetry is a separate mechanism, remains off by default, and is controlled separately. Intentionally air-gapped installations can keep both cloud licensing and signed release checks disabled, follow the documented offline update process, and receive notices and signed bundles through the approved offline delivery channel.

Retention

We retain personal information only as long as reasonably necessary for the purposes above, including fulfillment, support, security, and dispute resolution. We generally retain subscription, invoice, refund, and related transaction records for seven years to meet legal, tax, and accounting obligations. Customer-controlled Local data follows the customer's configured retention and deletion settings. You may request deletion of eligible information by contacting us.

Security and international processing

We use reasonable administrative, technical, and organizational safeguards, but no system is completely secure. Our providers may process information in the United States and other countries where they operate, subject to applicable safeguards.

Your choices and rights

You may ask to access, correct, or delete personal information, or object to certain processing. Rights vary by location and may be subject to legal exceptions. You can disable optional product telemetry in the product and unsubscribe from non-transactional messages using the method provided in the message.

Children

AuditFetch is a business service and is not directed to children under 13. We do not knowingly collect their personal information.

Changes and contact

We may update this policy and will change the date above when we do. For privacy questions or requests, email info@auditfetch.com.