SRM Insider
SRM INSIDER

Privacy Policy

Privacy Policy

Last Updated: November 14, 2026

SIC Authenticator Privacy Policy

This policy covers the SIC Authenticator browser extension. It is separate from the policies for the other products listed above. Visiting this website does not provide access to your saved extension accounts.

Publisher: SRM INSIDER COMMUNITY
Contact:admin@srminsider.in

SIC Authenticator generates time-based verification codes for accounts you add. Your account data is processed on your device. We do not operate a server that receives your setup keys, codes, images, or browsing information.

Information handled and why

  • Account and authentication data: service names, account labels (which may include an email address or username), TOTP setup keys, algorithm/digit/interval settings, and generated verification codes. These are used to generate and display the codes you requested.
  • QR images and camera frames: images you select and video frames captured after you choose camera scanning. They are decoded locally to add an authenticator account. SIC does not save the original image or video and does not upload it. Camera access is requested through Chrome only when scanning, and the stream stops after scanning, cancellation, or closing the page.
  • Website information: with temporary or optional access, SIC uses the active tab’s URL and tab ID to find the website you are using; samples computed colors and visible element styles to theme its own interface; and inspects verification-field attributes, labels, nearby text, focus, and existing field values to locate a code input and avoid overwriting unrelated data. This processing stays in your browser. Page text and field values are not stored by SIC.
  • User-requested form filling: double-clicking an account card passes only that account’s current verification code to the selected website and attempts to submit its verification form. The receiving website then handles the code under its own privacy practices. Setup keys are never passed to a webpage. Autofill requires HTTPS, apart from loopback addresses used for local testing.
  • Preferences and device time: SIC stores your selected interval and appearance preference, and reads the device clock/time zone to generate codes and show the clock. Sync refreshes from your device and does not contact an internet time server or change your system clock.

Storage, security, retention, and deletion

Setup keys, labels, and preferences are stored locally in your Chrome profile using chrome.storage.local. There is no vault password or application-level encryption for these saved keys. Anyone who can use your browser profile can view your codes. Access to extension storage is restricted to trusted extension contexts; SIC does not expose saved keys through content scripts or web-accessible resources.

A source tab ID may be held in Chrome’s in-memory session storage so the floating window can find its website. It is not a browsing-history log. Chrome also retains optional website permission grants until you revoke them. QR image data, camera frames, generated codes, and inspected page information are transient. Generated codes may remain on your clipboard after you choose Copy; your operating system and other applications with clipboard access control that clipboard.

Saved accounts remain until you remove them, delete extension data, or uninstall SIC. Use an account’s remove button, or open SIC → Privacy & permissions → Delete all saved accounts. Chrome settings also let you remove website permissions or uninstall the extension. Older encrypted vault data, if present from a previous version, remains local until the deletion control or uninstall removes it. We cannot recover deleted keys.

Sharing and other processing

We do not sell, rent, advertise against, analyze, or remotely collect extension data. The extension contains no analytics, advertising, tracking pixels, remote executable code, or cloud synchronization. Its only intentional sharing is your chosen code with the clipboard or the website you ask it to fill. Chrome and your operating system provide storage, permission, camera, and clipboard services under their own policies.

If you email support, your email provider and our email service process your message. Include only the details needed for help. Do not send setup keys, recovery codes, current verification codes, or screenshots containing them. Support correspondence is separate from extension data and is used to respond to your request; request its deletion by emailing the contact above, subject to necessary legal retention.

Permissions

  • storage: local accounts/preferences and a temporary source-tab identifier.
  • clipboardWrite: copy a verification code when you click it.
  • activeTab: temporary access to the website where you open SIC’s toolbar popup.
  • scripting: locally packaged color-detection and user-requested verification-field filling.
  • Optional HTTP/HTTPS website access: keep these features working on sites you allow, including while SIC is in its own window. It is not required to generate codes.

Limited use and changes

SIC Authenticator’s use of information obtained through Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the disclosed authentication features and their interface; it is not used for unrelated purposes.

We will update this policy when the product’s practices change. Material changes to data use will be disclosed in the extension and store listing as appropriate. The date above identifies this version. Contact admin@srminsider.in for questions or deletion requests.