viewusd.com · USDT
Data and privacy
How ViewUSD uses account, task and payment data. Updated November 10, 2026.
The service uses USDT for campaigns and tasks. FaucetPay processes deposits and withdrawals. Telegram sign-in is disabled.
Account and service activity data
Accounts use your name, email, verification status and password hash. Stored records include campaigns, URLs and terms, tasks, USDT entries, FaucetPay payment statuses and IDs, payout recipient email, support requests and staff decisions.
These data support sign-in, task verification, USDT accounting, payment processing, support and prevention of duplicate or unauthorized actions. Email support also processes your address, message and technical headers.
BitcoTasks partner tasks
When you open the PTC page, the available BitcoTasks list loads automatically. ViewUSD sends your IP address, browser information and a separate user identifier to BitcoTasks to select offers and prevent fraud. Your email address and password are not sent. Completion data is stored for reward history. When you visit a task on BitcoTasks, the partner’s own privacy rules apply.
OfferwallApi partner tasks
On PTC and Partners pages, ViewUSD requests available OfferwallApi tasks using your IP address, browser information, selected country and a separate user identifier. Your email and password are not sent. Proof is sent to the partner only when you submit it; confirmations are stored in reward history. When you open a task, OfferwallApi privacy rules apply.
Partner tasks
When you open the PTC page, the available partner task list loads automatically. ViewUSD shares your IP address, profile country and a separate user identifier with the partner to select tasks and prevent abuse. Your email and password are not sent. Our server signs the identifier with a temporary signature. Completion confirmations are stored in reward history. When you open a task, the partner receives browser information and its privacy rules apply.
Cookies and technical information
The website uses essential cookies for sessions and form submission protection. Selecting Remember me stores information in your browser for future sign-in. Restricting cookies may prevent sign-in and forms from working.
For the Online now count, the site uses a separate luch_presence cookie containing a random browser identifier. It lasts 120 minutes and is renewed when pages are opened. The server stores only a hash of the identifier and the last activity time for this counter. Records with no updates for more than 24 hours are removed during regular cleanup. IP addresses and accounts are not linked to this record.
The server receives the IP address and technical HTTP request information, including browser details. These may be logged and used to limit request frequency and investigate errors.
Visitor statistics
The providers listed below are enabled on public pages. When a page loads, the browser contacts the corresponding provider — Yandex and/or Google. The provider receives network and technical information and may use cookies for visitor statistics.
When conversion tracking is enabled, Yandex Metrica also loads on sign-in, registration, email verification notice, account overview, wallet and campaign list pages. Google Analytics runs on public pages only. Password recovery pages, verification links and administration are excluded. ViewUSD sends the page address without fragments or unrelated parameters; Metrica also receives valid advertising UTM tags. Only the referring site’s origin is sent. To measure advertising, ViewUSD retains the first advertising source in a first-party cookie for up to 90 days before registration, then in the account record. The Metrica visitor identifier and a separate random user ID associate visits with registration, email verification, confirmed real deposit and first advertising funding events. Only deposit events include the credited amount, represented for reporting as 1 USDT = 1 USD. Names, email addresses, wallet addresses, balances and form contents are not included in analytics parameters. Session Replay, click maps, link tracking, e-commerce and Google advertising personalization are disabled.
reCAPTCHA security check
Google reCAPTCHA v3 protects sign-in and registration. When you submit these forms, your browser connects to Google and sends technical information needed to assess the risk of automated requests. The service may use essential cookies. Our server sends Google a verification token; this verification request does not include your email or password.
Related-account checks
The ViewUSD pilot compares browser characteristics and FaucetPay payout recipients. A shared IP address alone does not flag an account. Staff review device and recipient matches; these signals do not automatically block an account or reject a payout during the pilot.
When Fingerprint is enabled, verified members’ account pages send the provider their IP address and technical browser and device information for identification. Collection does not run on advertising task pages. ViewUSD does not add names, email addresses, passwords, balances or payout addresses to this request; a random one-use value links the result.
The ViewUSD server verifies the Fingerprint response and stores a protected device identifier, confidence score, available VPN, proxy and network signals, time and account association. For FaucetPay, it stores a protected recipient identifier confirmed by the payment provider, the observation source and operation association. Full Fingerprint responses are not stored in the ViewUSD database. The identifiers support matching and are not anonymous data.
The report uses observations from the current assessment period within the last 30 days. This is a reporting window, not an erasure deadline: a retention period for the new observations has not yet been set. Account deletion removes that account’s new pilot observations and technical checks from the working database; it does not clear old backups or provider-held data.
ViewUSD extension data
The ViewUSD extension supports voluntary participation in rewarded advertising tasks and separately enabled autosurfing. A separate account access key is used to connect the extension.
The browser's local storage holds the access key, interface language and information about unfinished actions, including stop and cancellation requests. Temporary session storage holds autosurf consent and information about the managed task tab: its URL, tab, window and document identifiers, and loading state. This information is used to manage the task and stop autosurfing when the user navigates manually. Chrome Sync is not used.
To record a view, the extension checks whether the managed advertising tab is loaded and active, whether its window has focus, and whether the device is locked. It sends the access key, task, attempt and run identifiers, activity and loading states, and technical values for request processing and event ordering to the ViewUSD API over HTTPS. The server receives the IP address and technical HTTP request information.
The API provides the extension with the account identifier and name, connection information, task title and URL, viewing duration, reward amount and currency, and completion result. The server links confirmed activity to the account and reward records.
The extension does not read Chrome's stored browsing history or the contents of advertising pages. Tab events are filtered for the current task tab. The managed tab URL and document identifier are used locally and are not included in activity confirmation requests. These requests also exclude page contents, screenshots, keystrokes and mouse coordinates.
The access key can be revoked in the account settings. Revocation ends its access to the API. The extension can be disabled or uninstalled through the browser; these actions do not delete server-side task and reward history.
Hosting, retention and access
The application and email are hosted on the project's server in Finland. Backups are used for recovery, and technical logs are used to operate the service and investigate failures. Staff access is restricted by assigned permissions; extension data is also subject to the restrictions in the Limited Use section.
Fixed retention periods have not yet been established for task history, financial and partner transactions, contests, support requests, technical logs or backups. Account deletion does not initiate deletion of this history or cleanup of old backups.
Administrators receive Telegram notifications about tasks, deposits, withdrawals and moderation. Depending on the event, notifications may contain internal identifiers for the user, task, campaign or payment operation, the amount, status, event time and a link to the relevant administration page.
Account deletion
An account can be deleted in the settings after confirmation with the current password. Deletion is blocked while funds remain or obligations are unfinished.
Deletion clears the name and country, removes linked sign-in methods and replaces the email address with a technical address. The previous password stops working. Sessions and extension keys lose access.
Task, financial, partner, contest and support history is retained together with the internal account identifier. Account deletion does not mean that all associated data is deleted. This function does not clean up old backups or delete any Telegram messages that may have been sent previously.
Requests about access to, correction of or deletion of data can be submitted through support: https://viewusd.com/en/contacts. Do not send passwords or access keys.
Limited Use of extension data
ViewUSD complies with the Chrome Web Store User Data Policy, including Limited Use, when handling data obtained through the extension.
Data is used only for the extension's disclosed features and their improvement. It is not sold or used for personalized advertising, unrelated profiling, creditworthiness assessment or lending. Transfers are limited to supporting those features, security and legal requirements.
Human access is limited to explicit user consent for specific data, security needs, legal requirements or internal use of aggregated, anonymized data.
Third-party websites and integrations
Opening an advertising task sends your browser to a third-party website. That website receives visitor network information and may use its own cookies and data policies. Campaign moderation does not mean all actions of the external website are controlled.
For deposits, the server sends FaucetPay the amount and payment identifier. For payouts, it sends the amount and recipient email linked to FaucetPay. The server receives confirmations, statuses and operation IDs. FaucetPay applies its own data policies on its website.
Contact the project
The project name is viewusd.com. The current email and dashboard contact method are listed on the Contacts. Contact support with questions about data processing.