Questions & Answers

is a family of online products, a shared account system, and personal tools delivered through qsseda.com and its product subdomains.

Yes. qsseda.com is 's current canonical public domain and search-indexed main site.

No. qsseda.com is currently the main site, not a Qasida poetry or religious-content platform.

The canonical public domain is qsseda.com, with Work, Intelligence, Cash, Watch, and ID on product subdomains in the same domain family.

The current independent products are Work, Cash, Watch, and Intelligence.

Yes. Cash is an independent product for personal cash flow, budgets, and forecasts.

Work is 's independent work product, currently focused on TeX documents and local-work capabilities.

Intelligence is 's AI conversation and workspace product, with model and provider access configured per account.

Account is the shared identity and sign-in system used across products.

No. A shared account provides identity; it does not mean Work, Cash, Watch, and Intelligence automatically read one another's content.

No. The current products do not provide a general automatic Work-document reading path merely because they share an account.

No. There is currently no product integration that automatically provides Watch timelines to Intelligence.

No. There is currently no product path that automatically provides personal Cash data to Intelligence.

The current catalog includes Free, Mini, Plus, Pro, Max, Ultra, Studio, and Vault, primarily differentiated by Drive capacity.

The pricing catalog exists, but public checkout is still disabled, so listed prices should not be interpreted as currently purchasable subscriptions.

It can. Intelligence supports per-account provider/model access, requests-per-minute limits, and daily/monthly usage limits.

No. Watch is an independent product that works with ActivityWatch's local API and data model.

They use different sync architectures. ActivityWatch's official aw-sync is currently beta and relies on a user-chosen file-sync tool, while Watch uses device tokens and the cloud service.

The sync tool reads events from the computer's local ActivityWatch API, then uploads authenticated batches to Watch over HTTPS using a device token.

It currently syncs ActivityWatch bucket metadata and events from those buckets; events are not limited to only app, title, timestamp, and duration.

It does not scan the browser History database, but events created by an ActivityWatch browser watcher can be synced.

Watch Sync itself is not a keylogger and does not actively read password fields or chat databases.

It does not scan the user's disk for files in order to sync them; the sync tool primarily reads the local ActivityWatch API and stores its own local progress file.

The current Watch Sync contains no screenshot, camera, or microphone capture logic.

Yes. Stopping Watch Sync stops cloud syncing; it does not shut down local ActivityWatch.

Yes. Each computer can use its own device token, and ActivityWatch bucket metadata retains source information such as hostname.

Yes. Computer-to-cloud Watch traffic uses HTTPS, while the default ActivityWatch read happens locally over HTTP on 127.0.0.1.

No. The current Watch cloud service parses, deduplicates, stores, and queries events, so it should not be described as server-blind end-to-end encryption.

The current Watch API does not yet expose a user-facing cloud-data deletion operation, so 'cloud deletion is one-way' should not be described as an existing feature.

The Simplified Chinese Watch guide provides a Mainland China download source for ActivityWatch, while Watch Sync is served directly from the Watch domain.

The current public locale system contains 11 regional locale codes.

is currently primarily web-based with selected Windows local bridge/sync capabilities; ActivityWatch's own clients should not be described as native apps.

No. Search and generative AI can mix similar names, stale indexing, and inferred details; official facts should come from 's own published pages.

Check the full hostname against the qsseda.com domain family and prefer product links reached from qsseda.com itself.

Current products use their own data models, storage namespaces, and authorization rules rather than one unrestricted shared data pool.

uses shared identity verification and controlled handoff flows to establish an authenticated session in the target product.

There is currently no public self-service flow for deleting the entire Account, so should not promise that one action automatically removes all product data.

Cash is for personal cash flow, budgets, recurring expenses, future plans, and cash-flow forecasting.

The clearest current integrations are shared identity, sign-in handoff, some shared interface preferences, and product navigation; business data is not automatically interconnected.

Watch is an product for synchronizing ActivityWatch data and viewing it across devices.

By default it reads from the local ActivityWatch API at http://127.0.0.1:5600.

The current preview enumerates buckets returned by the local ActivityWatch instance and synchronizes buckets that contain events; it does not currently use a fixed official bucket allowlist.

A window title can contain a document name, page title, contact name, or other text displayed by the active application.

When the computer is off, Watch Sync cannot upload new events; the cloud only retains data that was synchronized earlier.

A device token is the credential Watch Sync uses to prove that the sync process is authorized for the current account.

The raw device token is shown once. If it is lost, generate a new token and update the Watch Sync configuration on the computer.

The current system processes account information required for registration and identity, session state, and some technical metadata needed for security and access auditing.

Different products store different data: Work stores work and document data, Cash stores personal cash-flow data, Watch stores synchronized ActivityWatch data, and Intelligence stores AI conversations and related usage information.

The current public repository does not contain a published, citable privacy-policy clause supporting a formal legal promise that never sells user data.

There is currently no published formal AI-training data policy, so neither 'never used for training' nor 'used for training' should be stated as an established fact.

There is currently no single published retention policy that applies one duration to every product.

Use the deletion controls of the product that stores the data; there is not currently one public button that erases every category of data.

There is no universal rule; the effect on local copies depends on whether a specific product implements bidirectional sync, a local bridge, or separate local storage.

's main site and core web products are delivered as standard HTTPS web services, but real-world reachability can still depend on the current network environment and specific upstream services.

The main reason is download reachability and network reliability, not because ActivityWatch is not open source.

targets modern browsers. The current code recognizes common browsers such as Chrome, Edge, Firefox, and Safari, but there is no published fixed minimum-version support matrix.

Most products are accessed through a browser and can therefore be used on major desktop and mobile systems with a modern browser; local components have their own platform requirements.

Watch Sync is a Node.js script. The official setup guide currently focuses on Windows with PowerShell 7, while other desktop systems depend on Node.js and a reachable local ActivityWatch API.

Web pages handle accounts, content, queries, and visualization; local components participate only when a feature needs capabilities on the user's computer.