Privacy Policy

Information Yuda Uses

• Account details such as name, username, profile photo, email, and account status.
• Contact preferences, including phone number and SMS opt-in or opt-out state.
• Job details such as title, description, approximate location, exact private address for confirmed jobs, photos, proof photos, status, and cancellation/completion history.
• Payment and payout references from Stripe, including customer IDs, connected-account IDs, PaymentIntent IDs, charge IDs, transfer IDs, refund IDs, and transaction ledger fields.
• Claim, review, notification, and support records needed to resolve marketplace issues.

How Data Is Used

Yuda uses data to create and display jobs, confirm helpers, process card authorizations and captures, support Connect payouts, send email/SMS/app notices, handle account security, resolve serious-problem claims, prevent fraud, and keep financial records accurate.

Location And Media

To find nearby jobs, Yuda asks for location through your browser's native permission prompt. If you allow it, the browser briefly supplies your device coordinates to Yuda's code in that page, which immediately rounds them to 0.1 degrees before storage or transport. Only the coarse record { v, lat, lng, expiresAt }is saved in that browser and is eligible for reuse for up to 24 hours. The unrounded coordinates are not stored, transmitted to Yuda's server, or placed in URLs. Nearby results use the rounded location and an approximate 15-mile straight-line radius.

You can deny location access or clear Yuda's site storage and location permission in your browser. The record is not deleted by a background timer. On the next Yuda application read, an expired or invalid record is discarded; Yuda then follows its normal location-resolution flow, which may request a current position from the browser. Browser or operating-system storage controls, including a private-browsing session ending, may clear the record sooner. If location access is denied, unavailable, or outside the supported area, Yuda shows general Puerto Rico job recommendations instead.

Exact job address details are kept in private job records and are used for confirmed work and support needs. Job images, proof photos, and claim evidence are treated as sensitive marketplace records.

Recently Viewed

When you open a valid job, Yuda keeps up to 20 valid, unique numeric job IDs in that browser's site storage so you can return to recently viewed jobs. As new jobs are viewed, older entries are evicted when the 20-ID limit is reached. This history has no fixed expiration, but browser or operating-system storage controls, including the end of a private-browsing session, may clear it; you can also remove it by clearing Yuda's site data. The IDs are sent only in a private, non-cached request and are never placed in URLs. Yuda matches them only to jobs that are still available in the Puerto Rico marketplace; unavailable IDs are ignored.

Account Deletion

Account deletion is scheduled with a grace period and may be blocked while there are active jobs, pending payments, pending payouts, active claims, disputed transactions, or unresolved claim follow-through.

When deletion is finalized, Yuda deletes or anonymizes profile details, contact records, exact job addresses for retained terminal jobs, job photos, proof photos, claim evidence, review text, personal notifications, and requester-authored job text. Yuda may retain minimal job, claim outcome, review rating, transaction, deletion audit, payment, tax, fraud-prevention, chargeback, and reconciliation records.

Payments And Third Parties

Yuda uses Stripe for saved payment methods, manual authorizations, captures, refunds, Connect accounts, transfers, and payout readiness. Yuda does not store raw card or bank account numbers in the app database.

Yuda may also use providers for email, SMS, maps, storage, hosting, and monitoring. Those providers receive only the information needed for their role in the service.

Security

Yuda uses authentication checks, rate limits, private storage access, signed webhook validation, security headers, and internal/staff-only claim tooling to reduce exposure of sensitive data.