Privacy Policy

1. Who we are

AuditIt is a software service for template-based before/after condition records. For privacy questions, contact support@auditit.app.

2. What we collect

Depending on how you use the service, we may process:

• account data (name, email, authentication identifiers);
• organization and team membership data;
• asset and customer display information you enter;
• photos, videos, notes, and checklist values uploaded as audit evidence;
• sound captured as part of uploaded video evidence;
• signer name and contact details (or hashed contact data) where provided;
• server timestamps and audit/event metadata;
• optional location evidence when your organization enables it;
• device/browser metadata used for security and rate-limiting (often hashed);
• billing and subscription metadata when payment providers are connected;
• billing identity confirmed by an organization owner or admin, such as legal name, billing email, billing address, and an optional tax-registration identifier; earlier confirmed versions are retained with their confirmation time for billing records;
• transactional email delivery metadata (e.g. invitation or signing notifications);
• with your permission, limited information about how you first reached AuditIt, which may be attached once when you create a workspace;
• an installation identifier, current notification token, app version, and last-seen time when you explicitly enable mobile assignment alerts.

We design for data minimization: collect what is needed to produce and verify an audit record. We do not use your audit evidence to train third-party AI models for general purposes in the current product scope.

On the mobile app, Google Firebase Crashlytics and Performance Monitoring may process crash stack traces, app and device details, installation or session identifiers, and selected timing measurements so we can diagnose stability and performance. Automatic network tracing is disabled. AuditIt's custom diagnostic reporting never sends audit evidence, signed upload URLs, or precise location.

If you enable assignment alerts, Firebase Installations and Cloud Messaging route a generic alert to this phone. The notification contains only internal organization and audit routing identifiers—never customer, evidence, signer, assignee, email, phone, or location details. You can turn assignment alerts off in Workspace.

On the web app, Sentry receives error events so faults can be diagnosed. Before an event is sent, AuditIt removes request bodies, cookies, private headers, and direct user details. It retains selected safe request metadata and sanitized diagnostic paths from the standard request, framework context, transaction, stack-frame, and navigation/fetch breadcrumb fields handled by this integration. In those fields, query data, fragments, referrers, URL credentials, and recognizable bearer-link token segments are removed. Token-bearing public pages and authentication handoff pages also instruct browsers not to send a referrer. Google sign-in keeps its validated return destination in temporary per-tab browser storage rather than adding it to the callback URL. An internal user identifier may remain. This filtering is designed to reduce the risk of sending audit content, signed upload links, contact details, or precise location, but no automated filter can guarantee that unexpected error data will never contain sensitive information.

The web app offers Allow and Declinechoices before it stores first-touch marketing measurement. Only after you choose Allow, your browser may keep a short campaign label, the referring site's host, a safe public landing-page path, and whether a supported advertising click identifier was present. Full referring addresses, query strings, click-identifier values, token-bearing paths, and account or workspace paths are not included in this browser record.

The choice and any pending first-touch record use browser local storage. Choosing Decline, or leaving the choice unset, means no acquisition record is attached when a workspace is created. Choosing Decline later removes any pending record from that browser. After a permitted record is attached to a workspace, the browser copy is cleared; contact support about access or deletion rights that may apply to data already held by AuditIt. Google Ads measurement has its own versioned browser choice. An older Allow for first-party measurement does not enable Google Ads until you choose Allow under the updated disclosure. The current mobile app does not infer or send an app-store acquisition source from the device operating system.

AuditIt sets a small number of first-party cookies needed to run the service, such as keeping you signed in and remembering which organization is active. With your separate, updated marketing choice, Google Ads may also set advertising cookies to associate an ad click with a new workspace. Leaving the choice unset or choosing Decline keeps the Google tag off. You can withdraw this choice below; this removes pending advertising cookies from this browser.

After you allow Google Ads measurement, Google may receive an advertising click identifier, a limited public landing address, browser or device information, and an opaque event identifier indicating that a first workspace was created or its user confirmed a relevant business workflow. We use this to measure ads across our segment landing pages. We do not supply names, email addresses, phone numbers, workspace names or identifiers, audit evidence, signatures, or precise locations for this measurement. Enhanced conversions and personalized advertising are disabled for this integration. The Google tag runs on eligible public segment offers and a brief completion transition; authenticated workspace screens, authentication handoffs, and token-bearing public records do not load it. Advertising cookies and blocked requests can limit measurement.

Facebook and Instagram measurement has a separate, versioned Meta choice. An Allow for first-party or Google measurement does not enable Meta. After you allow Meta, its Pixel may use advertising cookies and receive ad-click identifiers, browser and network information (including IP address), a limited public landing address, and an opaque event identifying completed first-workspace registration or a separate qualified business signup. Meta may use this information for ad measurement and targeting under its policies. We do not provide contact details, workspace names or identifiers, audit evidence, signatures, or precise locations for this measurement. Automatic matching and automatic event/page-detail collection are disabled. The Pixel runs on registered public segment offers and a minimal registration transition; it does not run on signup forms, authentication handoffs, private workspaces, demos, or token-bearing records. Decline removes Meta advertising cookies and stops future Meta measurement in this browser. A short-lived local record of opaque event attempts prevents normal refresh duplication; it contains no customer or workspace identifier. Browser restrictions and blocked requests can limit delivery. Advertising SDKs do not run in the native mobile app. AuditIt internally records the first server-accepted mobile audit for an organization after business-workflow confirmation. This internal record does not send audit content or identifiers to advertising platforms.

During onboarding, we save your suggested segment separately from the business workflow you explicitly confirm. These functional preferences help your team choose an editable starter even when optional advertising measurement is declined. Choosing Just exploring does not count as a qualified business signup.

Public demonstration videos use YouTube's privacy-enhanced mode and connect to YouTube only after you press Play. YouTube may then process network and device information, including your IP address, and playback activity under Google's policies. The player receives only our public site origin as its referrer, without campaign query values. Playing a video does not change your Google Ads or Meta measurement choices. You can also choose Watch on YouTube to open the video directly under YouTube's policies.

3. How we use data

• to provide templates, audits, signatures, reports, and verification;
• to secure the service (auth, rate limits, abuse prevention);
• to send transactional messages you or your organization trigger;
• to enforce plan limits, process billing events, and prepare billing records;
• to respond to support, export, and deletion requests.
• with your permission, to measure which first-touch sources and advertisements lead to workspace creation.

4. Sharing

We use infrastructure processors such as hosting and web delivery (Google Firebase Hosting and Cloud Run), database/auth/storage (e.g. Supabase), mobile diagnostics and opt-in assignment notifications (Google Firebase), web error reporting (Sentry), email delivery (e.g. Resend), and payment providers (when you enable billing). With your marketing permission, Google Ads also processes the limited measurement information described above. See Google'sPrivacy Policy andpartner-site data information. With your separate Meta permission, Meta also receives the limited information above. See Meta's Privacy Policy. We do not sell personal data. Public verification and share links only show what your organization and product privacy settings allow.

5. Retention

Default retention and holds are described in the Data Retention Policy. Signed/refused reports are not silently deleted. Billing failure does not delete evidence.

6. Optional rewarded ads

The mobile app may offer optional rewarded ads. Where available, you can review or change consent and privacy choices through the in-app Ad privacy choices entry point. Our initial posture is to request contextual or non-personalized ads rather than personalized advertising.

Google Mobile Ads may process device and ad interaction data to request, deliver, measure, secure, and prevent abuse of rewarded ads. Audit, customer, asset, evidence, signature, and report content is never supplied for ad targeting.

On iOS, AuditIt presents Google's applicable consent choices before requesting Apple's App Tracking Transparency permission. If you decline ATT, rewarded ads remain available as non-personalized requests.

7. Export and deletion

Organization owners/admins may request an organization export via support. A signed-in user can directly request account deletion from Workspace → Delete account in the mobile app. AuditIt records the request immediately and completes it within 30 days. We may need to preserve some audit history where legally or contractually required.

8. Security

We apply access controls, tenant isolation, hashed tokens for public links, and server-side hashing of media. No method of transmission or storage is perfectly secure; report issues to support@auditit.app.

9. Your choices

Depending on your location, you may have rights to access, correct, or request deletion of personal data. Use the direct in-app flow for account deletion; support remains available for other privacy questions. Staff of a customer organization should also contact that organization's admin for data the organization controls.

10. Changes

We may update this policy; the date above will change when we do.