このページは英語と韓国語で提供しています。英語版が適用されます。
Privacy Policy
Applies to the Pebblery Authenticator Chrome extension and this website. Effective date: [to be filled in before publishing]
1. In short
- The extension never sends your OTP secrets, account names, codes, QR images or screenshots to any server. It has no permission to access the network (content security policy
connect-src 'none'). - We cannot see your OTP data and cannot recover it if you lose it.
2. What the extension processes on your PC
- Authentication data (OTP secrets, account names, order): stored only if you add them, in Chrome's local storage, encrypted with AES-256-GCM. Your vault password is not stored.
- Camera, QR images and the current tab's screen: used in memory only to find a QR code when you start an import; never saved or sent. The current tab is read once when you click the toolbar icon and press +.
- One-click fill: when you click an account in the popup, a script examines input fields, their attributes and visibility in the current tab to fill a code. It does not store that page content or send it to our server. The website can receive the code you enter.
- Current tab address: the host name is used to prioritize matching accounts and decide whether to fill. It is not stored for ordinary matching; if you explicitly link a site, its host name is stored in the encrypted vault.
- Clipboard: clicking an account card copies its code to the clipboard, which other software on your computer may be able to read.
- Imported files: the extension reads selected authenticator exports on your device and stores supported accounts after your confirmation. It does not delete the original file.
- Linked sites: host names you link with “Link & fill” are stored with that account inside the encrypted vault.
- Windows Hello: face, fingerprint and PIN are handled by Windows. The extension never receives biometric data. It uses a standard passkey on this PC: after you verify, Windows returns a secret that unlocks the vault key, and only the vault key wrapped with that secret is stored locally.
- License key, installation time and settings: stored locally. The key contains a random license ID, issue and expiry dates and a signature — no email.
- Backups: created only where you choose (manual) or, if you turn on automatic backup, in Downloads\Pebblery Authenticator Backups (latest 5). Backups are always encrypted.
3. What the website processes
- Logs: IP addresses are kept in memory for up to one hour for rate limiting. Request bodies, emails and license keys are not logged.
- This website uses no advertising or analytics trackers and sets no cookies other than your language choice.
4. Retention
Removing the extension deletes its local vault. Manually exported files and automatic backup files remain on disk and must be deleted separately.
5. Sharing
We do not sell extension user data or use it for advertising. we do not share it with third parties, except where required by law.
6. Chrome Web Store User Data Policy
The use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
7. Your rights and contact
Contact: support@pebblery.com
Seller: Pebblery · [business address and registration number]