OkeWork Privacy Policy

Last updated: 21 October 2026.

OkeWork is operated by Thao Duong, an individual. Privacy, data and support contact: [email protected]. This policy covers the OkeWork extension and related account services on okework.com, app.okework.com and server.okework.com. Third-party services have their own policies.

1. Information handled

• Account and profile: verified Google account identifier, email, name and profile picture at sign-in; your chosen display name, biography and replacement avatar. Authentication requests openid email profile, not access to Gmail messages, Google Drive or Google Contacts.
• Workspace: notes and images you add, tasks, calendar entries, tables, learning cards, exercise answers, learning/focus history, saved tab sets, links, snippets and settings. Data needed for synchronization is sent to the OkeWork backend under your account.
• Feature-specific personal information: expenses, budgets, names, amounts and linking information entered in the debt ledger; hydration logs and health reminder settings. These are user records, not medical, payment processing or credit-scoring services.
• Authentication information: account sessions, application codes and Credential vault content. Saved Gemini API keys and Cloudflare tokens are synchronized settings in the current version. Do not supply credentials or company information without the required authorization.
• Browsing activity: with the required website access, Time records domains and daily durations. Tab sets and saved items can contain URLs and page titles. SEO/inspection tools process relevant DOM, headers or URLs. This information is not used for advertising profiles.
• Chosen website content: text/tables saved or translated, screenshots and Maps photos selected for processing. Page tools process the content/interactions needed for their functions, such as text selections and snippet expansion.
• Location: places and coordinates selected for weather forecasts. The reviewed manifest has no fixed Chrome geolocation permission; this is not a claim of continuous GPS tracking.
• Collaboration and communications: posts, comments, replies, friendship requests, group membership, check-ins and content you share. Direct chat processes content on participant devices; connection/session metadata is handled as described below.
• Technical information: VPS infrastructure, aaPanel/Nginx and Cloudflare can process IP addresses, request times/URLs, errors and technical information needed for operation and security. These logs support operation, not advertising profiles. OkeWork does not currently publish one automatic deletion period covering every infrastructure log.

2. Purposes

We use information to provide the browser workspace, identify the correct account, synchronize saved items, perform requested tools, deliver configured reminders and operate the disclosed collaboration features. Reporting and blocking support safety and abuse prevention.

We do not sell personal data, use or transfer it for personalized advertising, or use it to determine creditworthiness or for lending. Human access is limited to permitted circumstances, including your consent for specific support, security investigations or legal requirements. Administrators can moderate reported posts; the reporting tools do not provide access to direct-chat content.

3. Services and recipients

An integration may be unavailable when not configured. Providers can process network information and supplied data under their terms. We do not promise that AI providers never retain or otherwise process submitted data under their policies.

4. Storage and protection

Production backend connections use HTTPS/WSS. Ordinary workspace data is stored under your account on the server, with device caching for faster access; it is not represented as end-to-end encrypted. Cache does not replace backend access controls. A VPS operator with storage access can read ordinary database content; UI locking does not encrypt the entire server. OkeWork’s official backup tool produces AES-GCM encrypted archives; schema-upgrade snapshots and manual copies can have different protections.

The Credential vault encrypts content on the client with AES-GCM and a key derived from the unlocking code. A separate PIN is not sent to the server. Shared-PASSKEY mode includes server verification of the current application code during changes/removal, so it is not a promise that the server can never receive an unlocking secret in every mode. Short PINs have a smaller guessing space. OkeWork PASSKEY is a numeric application code, not a FIDO/WebAuthn passkey.

New direct chat sends message content over WebRTC between friends who accept a connection. OkeWork relays connection setup information. Participants can compare connection codes through another channel. History may remain in memory or an encrypted local cache depending on the selected mode. Ending a session cannot force deletion of screenshots, separate copies or offline recipient devices. Legacy chat data and old backups can have separate retention.

The personal image compressor processes images on the device; opening/editing an image does not automatically upload it. Avatar uploads or images deliberately saved in Notes/Document are different flows. Uploaded avatars are kept in 64 and 512 sizes; replacement overwrites the current server avatar, although backups can retain earlier versions.

5. Retention

• Ordinary account data is retained to provide the account until removed or a deletion request is implemented as described below. Uninstalling or signing out does not automatically delete the server account.
• Community posts expire after seven days along with related comments/views in active storage. Earlier backups can retain prior versions.
• Website-time logs use a 60-day window when logging/cleanup runs. Hydration logs retain up to 60 recorded days when updated. These are not guarantees that every backup or cached copy is simultaneously erased at that time.
• Refresh sessions have an absolute 14-day lifetime; access tokens last 15 minutes. Session expiry/revocation does not itself delete every account record or log.
• The backup template uses seven-day retention when the backup job and pruning step actually run. This is not an automatic deletion schedule for every snapshot, manual copy or aaPanel/Nginx/Cloudflare log. We do not promise that all such records are erased after seven days. When handling deletion requests, we identify retained copies and communicate the applicable handling schedule; deleted data is not deliberately restored for further use outside permitted purposes.
• Downloaded files and recipient-held copies outside the service are controlled by their holders.

6. Your choices and requests

You can change your profile/language, select modules, disable reminders/backgrounds and revoke website access through Chrome. Items can be edited/deleted using available controls. Signing out clears session/account caches in Chrome storage; local clearing is not server account deletion. A separate IndexedDB buffer holds the most recent screenshot, its URL and title; a new capture replaces it, and it can currently remain after sign-out. Downloaded files and images already open in editor tabs are not automatically recalled.

For a copy of your data or deletion of the server account/data, email [email protected] from the account’s email address, specifying the request and its scope. We verify ownership, confirm the scope and handling timeline by email, and explain any information that must be retained for security or legal requirements. We do not ask you to email a Google password, PASSKEY or vault PIN. This policy does not promise a complete-data Export/Import button in Profile.

Do not submit confidential company information or other people’s information without authorization. Shared content creates information available to its recipients, who may have already read or copied it before deletion.

7. Limited Use and changes

OkeWork’s use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information received from Google APIs is used and transferred only within the restrictions permitted by that policy.

If data practices change, we update this policy and prominently notify users in the product, obtaining consent where needed before the new handling begins. Contact Thao Duong at [email protected] with questions.