Privacy Policy
Last updated:
AutoComplaint is a Chrome browser extension that helps you file consumer complaints by extracting order details from e-commerce order pages and auto-filling the complaint form on consumerhelpline.gov.in.
Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We also follow the Chrome Web Store User Data Policy.
What data we collect and how we use it
1. Google account information
When you sign in with Google, we receive your name, email address, profile picture, and Google account identifier from Google's OAuth service. The extension displays your profile and sends the OAuth access token to our backend when authentication is required. Our backend validates the token with Google and uses the account identifier to associate payments and successful filings with the correct user.
2. Order page content
When you click "Extract Order Details" on an Amazon or Shopify order page, the extension reads the HTML of that page. The extension processes the selected page locally before sending it for extraction:
Local filtering is designed to remove contact and delivery details, including names, phone numbers, email addresses, street addresses and pincodes, from the page content sent for extraction. Automated filtering may not identify every personal detail on every page.
The filtered HTML, platform information and, for page classification, the selected page URL are sent to our backend. The backend uses Anthropic’s Claude API to identify order pages, extract structured order information and suggest grievance fields. Order identifiers, product and seller information, prices and dates may be included. Filtered content is not guaranteed to be anonymous.
Contact details entered for complaint-form completion are not intended as input to the AI extraction service. Do not include unnecessary sensitive information in order or grievance fields.
3. Extracted order data
The structured order and grievance data returned by Claude is stored encrypted in Chrome's session memory using AES-GCM-256 encryption and is cleared when the browser session ends. The backend processes this data to provide extraction and grievance suggestions. Separately, the reporting records described below are retained in our database.
4. Payments
Payment checkout and confirmation are handled by Dodo Payments. We retain the payment identifier, checkout-session identifier, filing-session identifier, Google account identifier, buyer email, amount, currency, product identifier, payment status, and confirmation time to verify that payment applies to the correct filing session and to prevent payment bypass or reuse.
5. Successful filing records
Only after the National Consumer Helpline displays its post-lodging feedback confirmation or an explicit successful-filing message with a docket number, AutoComplaint records that the filing was completed. We retain the product name, company, seller name, order value, filing category, nature of complaint, filing-session identifier, associated payment identifier, Google account identifier, and filing timestamp. We do not retain the NCH docket number, full complaint narrative, order ID, contact details, uploaded documents, or a copy of the NCH page.
6. Complaint reporting records
When the extension sends a complaint report, we store the seller name, shopping platform, complaint category, order amount and order date for service reporting. This record is separate from optional Google Analytics and does not contain the full complaint narrative or contact details.
7. Optional product analytics
Unless you opt out, the extension sends predefined usage events and verified service-payment events to Google Analytics through our backend. Analytics is on by default for users without a saved preference. Existing explicit opt-outs are preserved. The setting can be changed on the welcome screen or in the signed-in panel. Events use a random browser-installation identifier, session number, and a pseudonymous account identifier generated on the backend. They exclude your name, email, phone, addresses, page content, order details, and complaint narrative. Purchase events include the payment transaction identifier, service fee, and currency. Analytics choice at checkout applies to that payment, including a later payment confirmation. Turning off analytics stops new usage collection and removes the local analytics identifier; it does not delete previously collected events. We deny advertising data use and personalization in these requests.
8. Service owner notifications
After Google sign-in, the extension notifies our backend of first recorded sign-in and, for new installations, activation. We send the service owner an email containing the event type, timestamp and your verified Google account email through Resend. These operational notifications are separate from optional Google Analytics.
The private delivery queue stores hashed account/installation event identifiers, delivery timestamps and your verified email address to prevent duplicates and retry failed delivery. The email address is cleared from the queue after Resend accepts the email, but remains in the service owner’s mailbox and Resend delivery records. It does not include your name, order data or complaint content.
New installations keep a random activation identifier locally until it is queued after sign-in. Installation notifications do not occur before sign-in.
What data we do not collect
The extension does not use tracking pixels or analytics cookies; optional analytics uses Chrome storage identifiers. Website analytics is configured separately.
We do not mark a complaint as filed merely because a user clicked Submit; tracking requires the NCH success confirmation.
We do not sell your data. The services listed below receive data needed for their stated purposes; Google Analytics receives optional product events unless you opt out; extension collection starts only after sign-in.
Our application is designed to avoid logging contact details or raw order-page HTML in production. Operational error logs and hosting/service providers may process technical information, such as request metadata, IP addresses and diagnostic information, to operate and secure the service.
Third-party services
| Service | Purpose | Their privacy policy |
|---|---|---|
| Google OAuth | Sign-in authentication | https://policies.google.com/privacy |
| Google Analytics | Optional usage and service-payment analytics | https://policies.google.com/privacy |
| Anthropic Claude API | Order-page classification, extraction and grievance suggestions from filtered content | https://www.anthropic.com/privacy |
| Render (hosting) | Backend server hosting | https://render.com/privacy |
| Dodo Payments | Payment processing | https://dodopayments.com/privacy-policy |
| Supabase | Database hosting for payment, complaint-report, successful-filing and analytics-delivery records | https://supabase.com/privacy |
| Resend | Operational event notifications to the service owner | https://resend.com/privacy-policy |
Data retention
In your browser: Auth tokens, order data, and grievance data are stored in Chrome session storage and cleared when the browser session ends. Analytics consent/identifiers and payment-session metadata use separate local storage.
On our server: Payment verification, complaint-report and successful-filing records are retained for operational, fraud-prevention, support, and aggregate reporting purposes. Request logs are operational and are not used for advertising.
Optional analytics: Analytics consent and the random client identifier persist in Chrome local storage until analytics is disabled or the extension is removed. Pending purchase events are stored in a private delivery queue; GA4 event retention is controlled by the property's retention settings. You can request deletion of associated analytics records by contacting us. Previously queued payment events follow the analytics choice saved when checkout began.
Your rights
Turn off Usage analytics on the welcome screen or in Analytics settings to stop new optional usage events. This does not delete previously collected events or operational payment/filing records.
Signing out clears the extension’s stored authentication/profile information. Chrome manages its Google sign-in token cache separately.
Closing the browser clears Chrome session-storage data, including the extension’s session order/grievance data. Local analytics preferences and payment-session metadata can persist.
Uninstalling the extension removes its local browser storage; this does not delete server-side records.
To request access to or deletion of server-side payment, complaint-report, filing or associated analytics records, email support@autocomplaint.in from the Google account used with AutoComplaint. We may need to verify account ownership. Some records may need to be retained for payment reconciliation, fraud prevention or other applicable obligations; we will explain any such limitation when responding.
Contact
If you have questions about this privacy policy or wish to make a data request, contact us at: support@autocomplaint.in
Changes to this policy
We will update this document if our data practices change and note the updated date at the top. We will make the revised policy available through our published privacy-policy page. Your analytics preference can be changed independently of policy updates.