Privacy Notice

1. Who is responsible

Abrar Imdad Kanekar, an individual sole proprietor trading as SiteAirbag, is the controller/business for account, product, security, support and website data. The notice address is Khed, Maharashtra, India 415709. For rescue requests and customer-site observations processed for a customer, that customer generally determines the purpose and acts as controller/business; SiteAirbag acts as processor/service provider under the DPA. The Founder / Proprietor is the Privacy and Grievance Contact at privacy@siteairbag.com.

2. Account and commercial data

We process name, email, authentication identifiers, workspace membership, plan and entitlement state, acceptance records, support communications and Paddle customer, subscription and transaction identifiers. Paddle independently processes checkout and payment information as merchant of record; SiteAirbag does not receive complete payment-card details. Where advertising measurement is permitted for your region and your choice, the email address you enter at checkout is also converted to a one-way SHA-256 hash that is sent, with the event details, to Meta and, for YouTube ads, to Google to measure SiteAirbag's own advertising (see section 5 and the Storage and Cookie Notice); the readable address is never sent to them.

• Purposes: create and secure accounts, provide the contract, administer billing, prevent abuse, support customers and comply with law.
• Legal bases where applicable: contract, legitimate interests in service security and administration, and legal obligations.

3. Customer-site runtime data

The runtime sends configured site/action identifiers, anonymous per-session identifiers, device class, runtime version, timestamps, summarized timing, normalized outcome/failure evidence, and rescue outcomes. It does not intentionally send keystrokes, original form fields or bodies, authorization values, page HTML, session replay, advertising identifiers, or full query strings. Setup may temporarily use a minimized pathname and expected fragment to complete an authorized connection. When a browser attributes a Content Security Policy (CSP) violation to SiteAirbag, the runtime may send only the directive, report-or-block state, normalized SiteAirbag origin or fixed keyword, and runtime version; the resource category is derived from the directive and the report time is recorded by the server. It never sends the policy, page URL, blocked path, query, fragment or sample.

During a controlled beta, SiteAirbag also stores the minimized detection category, confidence, evidence-domain names, rule version and production-or-shadow mode. A workspace owner may explicitly label an incident as correct or not an issue, or report a missed issue. These records do not add raw form fields, page URLs, error text or inferred revenue.

• Purpose: learn healthy behavior, assess configured actions, detect conservative failure evidence, operate rescue, secure the runtime, evaluate detection quality and test rule changes safely in shadow mode.
• SiteAirbag does not use customer runtime data for advertising or infer revenue.

4. Deliberate rescue requests

A visitor may choose a SiteAirbag backup form and deliberately submit name, email, phone and approved business-safe details such as company, service needed, preferred time, postcode, reference or a short message. The form warns visitors not to submit passwords, payment details, government IDs, health data or secrets. Controls screen prohibited patterns, but customers must not configure or request prohibited data.

• The owning workspace can view the request and its delivery state.
• Ordinary notification email contains contact and reference information but not arbitrary structured payload; additional details remain behind authentication.
• Legacy custom-field records that cannot be proven safe are quarantined from the ordinary inbox.

5. Website, support, research and analytics

The SiteAirbag website and app use necessary browser storage for theme, authentication and setup continuity. Optional product analytics is disabled until the applicable consent or lawful trigger is satisfied. The Protection Scan reads a public page address you submit once from SiteAirbag's server to find forms, booking steps and calls to action; the address and the page are not stored, abuse prevention keeps a one-way hash of the host name and a rate-limit count for your IP address, and the result is shown only to you. If you ask for the result by email, SiteAirbag reads the page again, sends the report to the address you enter through Resend and does not keep the address; only if you tick the separate, unticked box for occasional tips does SiteAirbag store that address with the wording version you saw and the time, to send those tips until you unsubscribe through the link in each email. Optional advertising measurement with Meta, and with Google for YouTube ads, lets them measure whether SiteAirbag ads led to visits, checkouts, free trials, account setup or purchases. It follows your region: never in markets SiteAirbag does not serve (including the EEA and United Kingdom), on unless you opt out in the United States, and off unless you allow it everywhere else. A Global Privacy Control signal keeps it off. Opting out, or deleting your account, also deletes the advertising identifiers SiteAirbag holds for your checkouts and cancels those events not yet sent. Blog articles are written in Sanity, a hosted content editor, and read by SiteAirbag's server; that read sends Sanity nothing about you. When an article includes pictures, your browser loads them from Sanity's image network (cdn.sanity.io), so Sanity receives your IP address and browser information as the image host. The Storage and Cookie Notice describes exactly what is collected and sent. The customer-site runtime does not load SiteAirbag marketing analytics or advertising measurement. Support messages contain what you choose to provide; do not send secrets.

Account users may separately volunteer for product and pricing research. We record the participation choice and, if an interview occurs, controlled theme codes, audience, value-driver and pricing-response categories rather than a transcript or free-form notes. Withdrawing deletes linked interview codes. Funnel evidence is stored only as consented aggregate cohort cells with at least five participants; it contains no user or workspace identifier.

• See the Storage and Cookie Notice for the current key-by-key inventory.
• Use Privacy choices in the site footer, the Storage and Cookie Notice or Settings to change optional analytics or advertising measurement without affecting necessary service storage; withdraw research participation independently in Settings.
• Research participation is voluntary and is not used as a testimonial, entitlement, price assignment or automated decision.

6. Recipients and subprocessors

We disclose only what is necessary to subprocessors providing hosting/database/authentication, billing, transactional email, error monitoring and consented product analytics. Where advertising measurement runs under the rule for your region and your choice, we also disclose to Meta Platforms, and for YouTube ads to Google, the website identifiers, the Google ad-click identifier, the hashed checkout email address and the events described in the Storage and Cookie Notice. The current list, purpose and location information appears on the Subprocessors page. We may also disclose data where required by law, to protect rights and security, or in a business transfer subject to appropriate safeguards.

7. International transfers

Providers may process data outside your country. Where a restricted transfer requires a safeguard, SiteAirbag must put an appropriate mechanism and assessment in place for the actual parties, regions and data flow before making that transfer. Potential mechanisms include an adequacy decision, the European Commission Standard Contractual Clauses or a UK transfer instrument. The applicable entities, regions and executed mechanisms are being verified; contact privacy@siteairbag.com before deploying a flow that depends on a particular transfer mechanism.

8. Retention

Rescue-request personal content is scheduled for deletion or anonymization after 30 days unless a documented legal hold applies. Action-run history follows the purchased plan (30–365 days); inactive workspaces use a 30-day grace period. Minimized versioned detection decisions are retained for up to 180 days and explicit owner quality labels for up to 365 days. A withdrawn research choice and coded interview records are retained for no more than 365 days; linked interview codes are deleted immediately on withdrawal. Privacy-thresholded aggregate funnel cells may be retained for up to 730 days because they contain no user or workspace identifier. Short-lived credentials expire automatically and are removed after a short cleanup window; operational delivery and job records are normally retained for 30–90 days. Runtime-reported CSP diagnostics are stored with internal runtime errors and normally deleted after 30 days unless a legal hold applies. Security/audit records are normally retained for up to 365 days. Account configuration is retained while the account is active and enters the controlled deletion workflow after a verified deletion request. Minimized lifecycle evidence may be retained for up to two years, and Paddle or legally required transaction records may be kept for up to seven years where tax, accounting, fraud or dispute law requires it.

• At this policy date, the production Supabase Free plan does not include managed backups. SiteAirbag plans to move to a backup-enabled plan with a seven-day managed-backup window and add periodic external logical backups where practical. Do not treat the planned configuration as a current recovery guarantee.
• Aggregated statistics that no longer identify a person or customer may be retained.
• Visitors can use the verified privacy-request form to access or delete the personal details attached to a SiteAirbag request reference.
• See the Retention Schedule for a readable category-by-category summary.

9. Security

Controls include scoped origin-bound runtime authorization, short-lived credentials, Row Level Security, server-side ownership checks, signature-verified billing webhooks, data minimization, rate limits, audit records and monitored delivery queues. No control eliminates every risk. Report incidents to security@siteairbag.com.

10. Rights and requests

Depending on location and role, you may have rights to access, correct, delete, restrict or object to processing, receive portable data, withdraw consent, and complain to a regulator. SiteAirbag does not sell personal information for money. When advertising measurement runs, SiteAirbag discloses the website identifiers, the Google ad-click identifier, the hashed checkout email address and the events described in the Storage and Cookie Notice to Meta and, for YouTube ads, to Google to measure its own advertising; some US state privacy laws may treat that disclosure as a sale or as sharing for cross-context behavioral advertising. United States visitors can opt out at any time through Privacy choices, and SiteAirbag treats a Global Privacy Control signal as an opt-out. Elsewhere it runs only with your permission, and never in markets SiteAirbag does not serve. Customer-site runtime and customer personal data are never used for advertising. Use the verified privacy-request form or email privacy@siteairbag.com. We verify authority before acting and handle statutory requests within applicable legal deadlines.

• Visitors should identify the customer website and request reference where available; the self-service flow sends a single-use link only to the email recorded on that request.
• Authorized agents must provide evidence of authority. Appeals or regulator complaints can be submitted through the same channel.

11. Children and sensitive data

SiteAirbag is for users aged 18 or older and is not directed to children. It is not designed to collect sensitive personal information through rescue forms. Do not use SiteAirbag to solicit protected health, financial-account, precise location, biometric, government-identity, authentication or secret data.

12. Availability and regional scope

SiteAirbag is not currently accepting customers located in the European Economic Area or United Kingdom, or purchases for establishments there. This sales restriction does not remove privacy rights that apply to a visitor or prevent an authorized customer elsewhere from having visitors in those regions. Customers must obtain written approval before a deployment requires EEA or UK customer terms, transfer arrangements or regulatory support.

13. Changes and contact

Material changes will be dated, published and, where appropriate, notified through the account or email. Privacy and grievance requests: privacy@siteairbag.com. Legal notices: legal@siteairbag.com. Support: support@siteairbag.com. Security reports: security@siteairbag.com.