Whizz Repondly Chrome extension
Privacy policy
This policy explains what information the extension handles, why it is needed, who can access it, and the choices available to you.
Effective and last updated:
1. Purpose and scope
Whizz Repondly is a private workspace for authorized employees to record customer reviews and DoorDash promo subscriptions and view their personal tracking totals. The Chrome extension provides these features in a toolbar popup and links to the full workspace. It requires an account authorized by your workspace owner.
This policy covers the extension and its connection to the Whizz workspace backend. The publisher's privacy contact is [email protected].
2. Information we handle
- Account and authentication
- Your work email and password are sent to the workspace's Supabase authentication service when you sign in. The extension uses your account ID, authorized role, profile name and session tokens to provide account-specific access. Passwords are not stored in local drafts.
- Work records and tracking totals
- Store selections, work dates, review notes, DoorDash subscription numbers and the DD proof declaration are processed when you enter and save records. The extension retrieves permitted profiles, stores, record counts and monetary bonus totals. Bonus totals are work-tracking information, not payment-card collection or payment processing.
- Screenshots and submitted content
- The extension processes the image you explicitly select for a review, including its filename, image contents and any personal information visible in it. Images are prepared and previewed locally before submission. Include only information needed for the review and redact unrelated personal or sensitive content before selecting a file.
- Local preferences and drafts
- The extension stores your appearance preference, last selected entry type, account-specific draft fields, selected screenshot and stable save reference on your Chrome profile. These allow you to resume work after closing the popup and retry an interrupted save safely.
The extension does not include browsing-history collection, page-content scraping, click or keystroke analytics, device-location requests, advertising trackers, or access to your private messages. A screenshot can contain information you choose to include; the extension does not independently access the source website or messaging service.
3. Use and sharing
Information is used to authenticate your account, enforce workspace access, save records and supporting evidence, display tracking totals, and preserve or reconcile your unfinished submissions.
Supabase processes authentication, database records and private screenshot storage for the configured workspace. Authorized workspace managers can review employee records and evidence through the existing manager dashboard. Work records are therefore not private from authorized workspace management. Service requests necessarily disclose connection information, such as an IP address, to the receiving infrastructure; infrastructure logging is governed by the service configuration and provider practices.
The extension does not sell user information, use it for advertising, or use it to determine creditworthiness or for lending. Data use and transfers are limited to the disclosed work-tracking purpose and related operations. Our use of extension user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
For information about the backend provider, see Supabase's privacy policy.
4. Storage and retention
Your extension sign-in session and drafts are stored on the current Chrome profile. Local drafts are not an encrypted vault and are not synchronized between devices by the extension. Use a trusted device and browser profile.
A confirmed save clears the draft's note, subscription number, proof declaration and selected screenshot. Store and date selections and a save receipt remain to support continued entry. Explicit extension sign-out clears local draft records and the local authentication session. Pending or uncertain saves must be resolved first to preserve their retry identity. Appearance and entry-type preferences may remain.
Saved records and evidence remain in the workspace backend after sign-out or removal of the extension. Their retention and deletion are managed by the workspace owner. The extension does not apply an automatic server-side deletion schedule. Contact us about access or deletion requests, including applicable recordkeeping needs and any available backups; no fixed deletion deadline or backup-expiry period is promised by this notice.
5. Permissions and security
The extension requests host access only to its configured Supabase backend for authentication, authorized reads and user-requested saves. It does not request permission to read arbitrary tabs, browsing history, camera, microphone or device location, and it does not capture screenshots of tabs.
Backend connections use HTTPS. Access to records and private evidence is enforced by backend authentication and authorization rules. Executable extension code is included in the package; the extension does not download and execute remotely hosted scripts. These safeguards reduce risk but do not guarantee that any device, account or service is completely secure.
6. Your choices
- Choose which screenshot to attach, replace or remove it before saving, and omit optional review notes.
- Resolve pending saves and sign out when you finish using a shared device.
- Remove the extension to stop using it and clear its extension-local storage. This does not delete submissions already saved to the workspace.
- Request information about your records, corrections, account access or deletion by contacting the publisher. Requests will be handled with the workspace owner and subject to identity verification, applicable requirements and existing record-management permissions.
7. Contact and updates
For privacy questions or requests, email [email protected]. Identify your workspace and work account, but do not email passwords, session tokens or unnecessary customer screenshots.
Changes to this policy will be published on this page with an updated date. The policy, extension behavior and Chrome Web Store disclosures should remain consistent as features change.