Account information
Your name, email address, account timestamps, and verification state identify the account. Passwords are stored as one-way hashes rather than readable text.
Privacy
This notice describes the information the current ReWorth website handles, why it is used, and the boundaries built around customer and payment-related data.
This notice applies to information handled through ReWorth account, profile, buy-application, and sell-application features. It reflects how the website works as of the date above.
Your name, email address, account timestamps, and verification state identify the account. Passwords are stored as one-way hashes rather than readable text.
Contact preferences, phone numbers, shipping and billing addresses, and delivery instructions can be saved to your profile. Request-specific card details remain with the applicable application.
Buy and sell requests include applicant details, device or catalog information, address details, the reviewed amount, status, timestamps, and processing references generated for the request.
A purchase request stores the Telegram username or WhatsApp phone number selected for order-review and identity-verification updates.
Authentication records may include a session token, expiration time, IP address, user agent, and the account ID needed to keep signed-in requests associated with the correct customer.
ReWorth uses account and session information to sign customers in; profile information to save contact and address preferences; and application information to validate, price, review, and display purchase requests. Application prices are resolved from the website's current catalog rules before a request is stored.
Status and processing references allow an application to move through the review workflow and appear in the signed-in customer's account. Authorized staff can use the administrative workspace to review customer and application records.
ReWorth uses the selected Telegram username or WhatsApp phone number to notify the purchaser when an order review is approved and to coordinate any identity-verification steps. The contact is stored with the applicable request and is not included in advertising-event data.
The current purchase application does not ask for identity-document images. Identity images attached to earlier requests, if any, remain under their original restricted access controls and are not exposed as ordinary application files.
The profile and application interfaces require an authenticated session. Customer requests are associated with the signed-in account, and customer-facing APIs return the profile or application history for that account. Administrative access uses a separate staff-only check.
The request form collects the cardholder name, full card number, expiration, security code, and complete billing address. These details are saved with the application and displayed only inside the access-controlled administrative workspace. Customer-facing pages show a masked summary (card brand and last four digits).
An application stores the card summary, consent timestamp, billing details, and identity verification status alongside the card record. Ordinary ReWorth forms and APIs reject raw card numbers, CVV or CVC, PINs, payment-card passwords, and similar secrets sent outside the request flow.
Signed-in customers can review their account email, edit saved contact and address details, view masked payment and authorization details for their applications, view their history, change their password, and sign out. Customers can also close their account, which removes the sign-in credential and sessions only; contact, application, card, and identity-document records remain on file for their permitted review. The current website does not provide a self-service data-export or identity-document deletion control.