Dushi360 Privacy Policy

Translation status: English draft for convenience. Human legal review is pending. Until completed, the Chinese version is the controlling version to the extent permitted by applicable law.

Version: 2026.10.08-1　Effective: October 8, 2026

This Policy applies to the Dushi360 website, mobile website, iOS and Android apps, and related services. It explains how we access, collect, use, share, retain, and delete personal information.

1. Provider and contact

Dushi360 (Dushi360.com) · Privacy email: Dushi3600@gmail.com · https://www.dushi360.com

2. Information we process

• Account and contact data: username, display name, phone, email, password hash, and avatar.
• User content: listings, community posts, comments, images, messages, reports, support requests, favorites, and browsing history.
• Transaction and app-store purchase data: prices, wages, housing, vehicles, businesses, rideshares, and deals, plus the store platform, product ID, order or transaction identifier, purchase-token hash or signed-verification result, purchase status, credited or reversed Points, and relevant timestamps needed for a Points purchase. Apple App Store or Google Play processes payment. The Dushi360 app does not receive, read, or store complete payment-card numbers or complete bank-account details.
• Verification data: names, credential or qualification images, industry, region, and contact information voluntarily submitted for review.
• Device and logs: device type, OS, app version, IP address, request time, error type, security records, and activity records. The app may submit a short error summary, code, and fingerprint after client-side and server-side redaction. Raw logs, chats, post text, passwords, tokens, full phone numbers, email addresses, IPs, coordinates, and local file paths are not submitted in diagnostic reports.
• Location: with permission and an active request, the device briefly obtains precise coordinates. Coordinates may be sent to device geocoding and Photon/Komoot reverse-geocoding services, which may automatically receive IP addresses. Dushi360 currently does not save raw precise coordinates to your account, continuously track location, or use it for cross-context behavioral advertising. Selected city and weather are cached on the device.
• AI inputs, files, images, candidate summaries, and recordings: only after you actively choose an AI feature and consent, submitted text, temporary voice recordings, matching requirements, poster details, communication-assistant details, selected files or images, or selected content for translation may be processed. File and image reading can recognize and translate visible text and extract key points, dates, amounts, and warnings from leases, bills, menus, quotes, government letters, and photos of them. AI explanations are general information, not legal, tax, medical, immigration, or financial advice. Matching sends necessary summaries of up to 160 approved listings and businesses and returns only real in-app IDs. AI drafts never publish or send automatically.
• On-demand translations: selected listings, businesses, comments, rideshares, deals, private messages, or support messages are processed only after a translation request. Originals remain unchanged. Translations and source hashes may be cached only within the same account for up to 90 days; withdrawing AI consent or deleting the account removes that account's cache. Voice translation handles one segment of up to 60 seconds and deletes temporary audio after processing or failure.
• AI usage records: account ID, feature, provider, model, token or audio/file size, latency, status, content hash, and points. Usage logs do not store original text, full transcripts, audio, uploaded files, or complete model output.
• Permissions and tokens: push tokens after permission; camera and photos only for scanning, capture, or selection; microphone only after the user starts AI voice publishing or translation; no contact-list reading and no continuous background location.

Review appeals: when a rejected submission is appealed, we process the user's appeal reason and the reviewer's response. These records may be retained for the reasonable period needed for re-review, disputes, fraud prevention, audit, or law. Accepting an appeal only returns content to human review and never publishes it automatically.

Reports, account restrictions, blocks, and safety controls: we process report status; the scope, duration or lifting condition, and broad reason category of an account restriction; a report-appeal statement and up to three images selected by the appellant; reviewer decisions; block relationships; and recipient, time, and irreversible content-fingerprint signals needed to detect identical bulk messaging. Immediately before sending, text may be checked for patterns associated with phone numbers, home addresses, identity documents, deposits, training fees, gift cards, or off-platform links solely to decide whether to show a confirmation warning; we do not create a separate copy of the message solely because the warning is shown.

Notification preferences and phone-number access: we process the push token, platform, language, time zone, and notification preferences needed to apply local quiet hours. Phone numbers shown to other users are masked by default. When a user requests the complete number, we process the viewer account, the related content or person, time, result, and necessary device/IP security information to authorize the request, prevent abuse, investigate incidents, and maintain an audit record. That audit record is not displayed in ordinary user interfaces.

Private resumes and job applications: We process desired roles, work and education history, skills, certifications, languages, preferred location, availability, contact-sharing choices, and voluntary self-declarations about U.S. work authorization and sponsorship needs. A resume is not public or searchable. After the user confirms an application, the job's currently verified employer can view the immutable resume snapshot submitted at that time, the cover message, and status. Employer verification only means submitted materials were reviewed; it is not a guarantee of the job, compensation, or hiring outcome. Do not submit Social Security numbers, identity or immigration documents, birth date, marital status, race, religion, disability, or other information unrelated to job qualifications.

Classified-listing engagement aggregates: to give a listing publisher performance feedback, we count category impressions, detail-page views, private-message inquiries started from the listing, and taps on the “Call” button. An impression, detail view, or call tap for the same listing and action is counted only once per user—or per server-keyed anonymous pseudonym—within a 30-minute window. A listing-based message inquiry is counted only once for the same account and listing. Publishers see aggregate numbers only and cannot identify viewers, inquirers, or callers. The metrics tables do not store raw IP addresses or raw User-Agent strings. For anonymous deduplication, network and browser information is used only momentarily on the server to create an irreversible keyed pseudonym.

3. Purposes

We use information to provide accounts, authentication, support, posting, browsing, search, messages, favorites, city selection, weather, notifications, private resume storage, user-confirmed application snapshots, application processing and in-app communication, content screening, report progress, restriction notices and appeal review, cross-feature blocking, sensitive-information confirmation warnings, local-time quiet hours, bulk-message rate limiting, generic lock-screen notices, authorization and audit of complete phone-number viewing, publisher-only aggregate listing engagement feedback, short-window deduplication that does not reveal visitor identity, fraud prevention, security, requested AI transcription, drafts, document reading, communication assistance, matching, posters and translation, verification, business applications, points, promotion records, debugging, performance, and legal compliance.

4. Public content and sensitive-data warning

Published titles, text, images, region, prices, and selected contact information are visible to others. Phone numbers shown to other users are masked by default and are returned in complete form only after the viewer taps to request access and passes login, visibility, and block checks; the request creates a necessary security-audit record. A private resume is not public or searchable. Once an application is submitted, only the corresponding currently verified employer and personnel whose access is necessary for safety, support, or law can view that application's resume snapshot. Verification only means submitted materials were reviewed; it is not a guarantee, so review the job and account before sharing. Do not place Social Security numbers, identity-document images, payment-card data, unnecessary precise home addresses, or other unnecessary sensitive information in public content or a resume. Messages are not end-to-end encrypted and may be accessed by authorized personnel when needed for delivery, reports, security, or law. The app may perform an immediate pattern check and show a confirmation warning before a message that may contain a phone number, home address, identity document, deposit, training fee, gift card, or off-platform link is sent; the warning does not verify the recipient or transaction for you.

5. Service providers and sharing

We do not sell personal information or use it for cross-context behavioral advertising. Necessary information may be processed by Twilio for phone verification; Resend for email registration, verification, password recovery, delivery, bounce, and complaint handling; Expo and Apple/Google push services for push tokens, device platform, and generic notification content; Photon/Komoot; U.S. Census geocoding; Apple/Google device geocoding; Open-Meteo; ExchangeRate-API; Groq; and OpenAI. Private-message lock-screen content sent through push services omits message text, phone numbers, addresses, and resume information by default. Apple App Store and Google Play process digital-Points payments, taxes, payment credentials, refunds, and chargebacks and return the product and transaction status needed for server verification, crediting, purchase restoration, and reversal of invalid Points; Dushi360 does not obtain complete card numbers from those stores. AI requests do not separately include your Dushi360 account ID, but submitted text, audio, files, or images may contain contact or address information. OpenAI may process user-selected files or images for file and image reading, visible-text translation, and extraction of dates, amounts, key points, and warnings. Temporary server copies are deleted after processing or failure. When an administrator requests error and feedback analysis, only redacted fingerprint-level aggregates and redacted inbound support-feedback excerpts are sent, not account IDs or raw logs. OpenAI Responses requests use store:false, subject to provider security, abuse-prevention, and legal obligations. We may also share information with consent, for a business transaction, to protect users and the Platform, or to comply with law.

6. Permissions and alternatives

• Location suggests local content; select a city manually if denied.
• Photos/camera support avatars, posts, verification, and scanning; text-only features remain available where applicable.
• Notifications support messages and service alerts; denial does not prevent browsing or posting.
• Microphone is only for user-started AI voice publishing or turn-by-turn translation; use text or manual entry if denied.

7. Retention

Account data and content generally remain until deletion or account closure. SMS and email verification codes expire after 10 minutes; expired verification records are retained only for the limited period needed for abuse prevention and troubleshooting, and plaintext codes are not returned in production API responses or ordinary logs. Temporary AI audio and uploaded file- or image-reader files are deleted after processing or failure. Translations, source hashes, and language information are cached only within the same account for up to 90 days. Withdrawing AI consent or deleting the account removes its cache. Legacy cache without account ownership is no longer used and remains in restricted, recoverable storage; it is not deleted. Original messages, posts, and backups follow their respective retention rules. Redacted diagnostic summaries may be retained up to 180 days; AI error-analysis reports contain only redacted aggregates. Verification, consent, safety, reports, report and content-review appeals, appeal images, review responses, account restrictions, blocks, rate limits, phone-number access, and audit records may be retained, or de-identified where appropriate, for the reasonable period needed for review, disputes, fraud prevention, safety, or law. Appeal images are available to authorized personnel only for the period needed for review, dispute, safety, or legal purposes. App-store orders, server-verification results, Points-ledger entries, refunds, revocations, and chargebacks are retained for the period required for tax, accounting, store compliance, dispute handling, and fraud prevention. Records retained after account deletion are access-restricted and de-identified where feasible. Backups are overwritten in the normal cycle and effective deletion requests are re-applied after restoration.

Short-term AI result recovery: To prevent duplicate charges after a connection loss or timeout, complete AI results are retained in encrypted form for recovery by the same account for 60 minutes after success. Results may include submitted text, transcripts, file summaries, or communication drafts. Keys are kept outside publicly accessible website directories, and recovery requires the account’s current AI consent. Access stops at expiry; a scheduled task normally deletes expired ciphertext every five minutes. Withdrawing AI consent or deleting the account removes its recovery copies and prevents unfinished requests from charging or finalizing a successful result. These copies are handled separately from AI usage logs, original temporary audio and files, and the account-scoped translation cache described above; original temporary files, usage records, and backups follow their respective retention terms.

Resume and application retention: A private resume remains until the user edits, replaces, or closes the account. Each application retains its submitted resume snapshot, cover message, status, and necessary events so both parties can review history, resolve disputes, and prevent duplicates; withdrawal does not immediately delete that history. These records generally remain until the applicant or job publisher closes the account, or until Dushi360 deletes or restricts them as required for applicable law, safety, or dispute handling.

Engagement-metric retention: deduplication events for category impressions, detail views, and call-button taps are removed 48 hours after creation. After the 30-minute deduplication window ends, they remain only until that cleanup to prevent unsafe or duplicate counting. The listing-message deduplication record is used to ensure that the same account contributes only one inquiry to the same listing; it is not removed by the 48-hour cleanup and is deleted when the related account is deleted. Publisher-visible totals contain no visitor identity. If the publisher deletes the account, the aggregates and deduplication events for that publisher's listings are also deleted.

8. Security

We use HTTPS, password hashing, access controls, least privilege, cross-feature block checks, phone-number masking, and security logs. No internet service is absolutely secure. We assess, remediate, and notify qualifying security incidents as required by law.

9. Choices and rights

You may access and correct profile data, delete your content, delete your account in the app, withdraw system permissions, and withdraw AI consent in Settings. Where applicable, you may request access, correction, deletion, a copy, information about processing, or limits on sensitive-data processing, without discrimination. Contact Dushi3600@gmail.com; reasonable identity verification may be required.

10. Account deletion

A Points balance does not prevent an account-deletion request or completion. Deletion removes or de-identifies account data, posts, community content, chat, favorites, verification materials, push tokens, and listing-engagement deduplication records associated with that account. Historical aggregate counts that contain no identity may remain, but aggregates for the publisher's own listings are deleted when that publisher closes the account. Unused Points are forfeited when the account closes and are not converted to cash or moved to another account unless applicable law or store rules require otherwise. Minimum transaction records may remain where required for tax, accounting, store compliance, security, fraud prevention, refunds, chargebacks, or unresolved disputes, with restricted access. Deletion does not remove rights available under applicable law or the original app store's refund and dispute rules.

11. Cookies and local storage

The website uses cookies for sessions and preferences. The app uses secure or local storage for login tokens, city, weather cache, selected currency, language, required preferences, and unsubmitted resume drafts. Native-app resume drafts expire after up to 30 days. Only the local development web build may retain them for up to 7 days; production web does not retain resume drafts. Logging out clears that account's local resume drafts.

12. Children

Dushi360 accounts and posting, messaging, transaction, and transportation features are only for people age 18 or older. We take reasonable steps to delete information confirmed to have been collected from a minor in error.

13. Cross-border users

The service is primarily for U.S. users and information is mainly processed in the United States. Users elsewhere should understand that information may be transferred to the United States, subject to reasonable safeguards required by applicable law.

14. Updates

We publish a new version and date for changes. Material changes to purposes, sensitive information, recipients, or rights receive prominent notice and renewed consent when required.

15. Contact

Privacy requests or complaints: Dushi3600@gmail.com. Do not email passwords, complete identification numbers, or payment-card information.

16. Optional third-party sign-in

Only when a sign-in option is available in your platform and app version and you choose it, Dushi360 processes the provider account identifier returned by Apple, Google, or WeChat, plus a name or email if you authorize the provider to supply it. This data is used to verify identity, create or sign in to the requested Dushi360 account, prevent abuse, and protect account security. We do not merge an existing account automatically merely because an email matches.

Dushi360 stores a server-keyed hash mapping of the provider identifier rather than the raw identifier in the ordinary account record. One-time login challenges expire promptly, and provider codes or tokens are processed only as long as needed to complete verification; they are not retained as ordinary profile data. The identity mapping generally remains until account deletion or unlinking of that provider. Limited audit records may be retained with restricted access for security, fraud prevention, disputes, or law.

If the relevant option is available and you choose it, Apple Inc. (Sign in with Apple), Google LLC (Google Sign-In), or Tencent/WeChat (WeChat Login) may process the sign-in request, provider account identifier, one-time code or token, and any name or email you authorize them to provide under their own privacy terms. This disclosure does not mean every provider is enabled on every platform, region, or app version.