Uni3K
Uni3K (大千) Privacy Policy
Uni3K saves text you choose to clip and notes you write. The extension works locally without a Uni3K account. We do not run analytics, advertising or tracking. Your records reach our server only if you sign in and choose to keep them in the cloud.
Uni3K account and cloud records
Signing in is optional. It opens the sign-in page of the Uni3K web app (app.uni3k.com) in a browser window, where you sign in with Google, Apple or a passkey. The service uses the name, email address and provider account identifier supplied at sign-in to identify your account; the extension stores the account name and email for display. The extension then receives a session token, which stays in the extension's local storage, is sent only to app.uni3k.com, and is never exported, synced or included in backups. While you are signed in, records you set to “Cloud”, the folders they are in and your sealed lock vault are sent to your account to sync with the web app and your other browsers. Locked records are sent only as ciphertext; Uni3K cannot read them. Records kept on this device only or in WebDAV/Google Drive sync are not sent. Signing out removes this browser's copies of cloud records (they stay in your account) and ends the session. Deleting your account on the web app deletes its cloud records.
What the extension accesses
When you save a selection, Uni3K stores the selected text, page URL, domain, page title and timestamps. Notes can include the current page URL when “Attach page” is checked. Saved highlights include their source URL and text positions so they can be restored when you revisit that page. Custom folder names and record assignments are stored locally using the existing spaces data. Folder definitions are included in JSON exports and local snapshots and, when you enable synchronization, sent to your selected cloud service. Existing space assignments and preferences are retained.
The content script accesses page text to capture your selection and restore saved highlights. It does not upload the pages you visit or maintain a separate browsing-history log. Uni3K installs without access to all websites: when you press the capture shortcut or use the context-menu action, it runs only in that tab. Site access for all pages is optional and is requested only when you enable the selection save button, copy history, restore highlights on every page, attach the current page to a note, or connect a sync server; you can turn it off in Settings at any time. You can disable capture and highlights for a domain and its subdomains in Settings, or restrict site access using Chrome’s extension controls.
Optional clipboard history
On first use, or after an upgrade introduces clipboard capture, Uni3K prominently explains this feature and asks you to choose Agree and enable or Not now. No copied text is recorded until you explicitly agree. Dismissing the notice does not give consent. An existing paused preference is retained. After agreeing, auto-save is enabled and can be paused in the Clipboard category. While it is on, Uni3K records text you copy or cut with the browser’s normal copy controls on supported web pages, along with its source URL, domain, title and copy time. It keeps only the latest 99 unique text entries in this browser profile. Copying the same text again moves it to the front. It does not read the system clipboard, monitor other applications, capture password inputs, or save copies from incognito tabs or domains you disabled. Chrome-protected pages and embedded frames are not captured. Website copy buttons that use their own clipboard code may not be captured.
You can pause auto-save, remove an entry or clear this history in the Clipboard category. History is temporary and is excluded from synchronization, JSON exports and local backup snapshots. “Save as note” creates a regular note, then removes that entry from the history; that note follows your normal export, backup and optional sync settings. Clearing local data also removes history and resets preferences to their defaults, including the consent choice; capture stays off until you agree again.
Local storage and credentials
Records, highlights, spaces and preferences are stored in your browser profile using IndexedDB and Chrome storage. Local snapshots also remain in that profile. An unfinished quick note is kept in browser session storage until saved, cleared or the browser session ends. Your versioned clipboard consent choice and decision time remain on this device; they are excluded from synchronization, exported backups and local record snapshots. A backup cannot authorize clipboard recording.
If you configure WebDAV, its address, username and password are stored locally to connect to that server. These credentials are available to trusted extension pages, not content scripts. They are not separately encrypted by Uni3K. Chrome’s native Google authorization tokens are managed through its identity API. The optional Brave/web connection opens Google’s authorization page using the browser identity API and stores only a short-lived access token and expiry in trusted extension session storage. A local preference remembers the selected authorization method. The web connection does not collect your Google password, use a client secret, retain a refresh token or send authorization tokens to an Uni3K server. Web tokens and authorization-method preferences are excluded from exports, synchronization and backup snapshots. Protect access to your device and browser profile.
Locked records
Sign in to set a lock password and encrypt cards. Uni3K derives a key from the password on your device (PBKDF2-SHA256) to protect a versioned vault of random data keys used for AES-GCM encryption. Changing the password creates a new data key for future writes and protects the historical keys with the latest password. Existing cards can be updated to the new key; earlier exported or synchronized files are not rewritten. A locked record keeps no readable text or title on the device, in sync files, in exports or in snapshots, and it is left out of search. Your password is never stored or sent. Uni3K cannot recover a forgotten password or the records locked with it. Locking a record also replaces its earlier copies in local snapshots; copies in files synchronized or exported before you locked it are not changed, so delete those separately if needed.
Optional local MCP for AI agents
Local MCP is off by default. When you turn it on, Uni3K asks for the nativeMessaging permission and connects to a small helper program you install on your own computer. AI agents you add in Settings each get their own token; Uni3K stores only a hash of it. An agent can save, change and delete records only in its own folder. It can search and read your other records only if you allow it for that agent. Locked records are never passed to agents; they see only that a locked record exists. Records go only to the helper on your computer and to the agent you connected to it, which may send them to its AI service under that service’s terms and privacy policy. The extension itself does not upload records as part of MCP. Turn local MCP off or remove an agent in Settings at any time.
Optional synchronization
Synchronization is off by default. When you enable a service and synchronize, Uni3K sends records—including saved text, source information, timestamps and deletion markers—and folder definitions, names, ordering, record assignments and folder deletion markers to that service. Records you keep on this device only, highlights, preferences, temporary clipboard history and local snapshots are not synchronized in this version. Locked records are synchronized only as ciphertext. Automatic sync runs only when you configure it.
- Google Drive: The extension requests the
drive.filescope to access files it creates or that you authorize. It storesUni3K/snippets.json(a folder namediSnipsfrom earlier versions is renamed) in an ordinary folder in your Drive, not a hidden application-data folder. Access is governed by your Google account, folder sharing and Google’s policies. Uni3K does not change sharing permissions. - WebDAV: The extension sends records, folder definitions and authentication credentials to the server you configure. Remote connections require HTTPS; HTTP is allowed for localhost development only. The server operator controls storage and access under its own policies.
We do not sell data, use it for advertising, or transfer it to data brokers or credit services. Data received through Google APIs is used only to provide the synchronization you request and is handled in accordance with the Chrome Web Store User Data Policy and its Limited Use requirements.
Export, deletion and your choices
You can export a JSON file containing records, highlights, spaces and supported preferences. Export files and new local snapshots exclude sync configuration, connection credentials and tokens. Exported records may themselves contain personal information or secrets you saved; keep the file private.
Deleting a folder returns its records to Unfiled and removes the folder from the interface. Its last name and deletion timestamps remain locally and in synchronized files as a deletion marker, preventing old files or offline renames from restoring it. Folder deletion does not remove record text.
Moving a record to Trash is reversible. Emptying Trash removes it from the interface and retains deletion markers to propagate deletion during sync; underlying record content and earlier snapshots can remain in storage. “Clear local data” deletes the extension’s local records, folders and deletion markers, highlights, preferences, credentials, recovery copies, session drafts and snapshots, and stops local synchronization.
Clearing local data or disconnecting a service does not delete files already on Google Drive or a WebDAV server. Delete those remote files and any exported backups separately if you no longer want them. Reconnecting to an existing sync file can download its records again. Disconnecting the web connection clears its credentials on this browser and stops local synchronization; it does not revoke authorizations on other devices. The native Chrome disconnect also attempts Google authorization revocation. You can revoke Uni3K access in your Google account, which may affect other devices using the same Google project.
External links and contact
Source links, feedback and support links open only when you choose them. Those websites receive your visit and apply their own privacy policies. Contact us at support@uni3k.com or through the support page. Please do not send passwords or the contents of locked records.