Gifted Pros Privacy Policy

Last updated: October 29, 2026

Privacy and account/data deletion requests: privacy@giftedpros.com. SMS Terms. Request instructions and retention exceptions.

SMS privacy and optional consent — GIFTED PROS LLC / Gifted Pros

SMS consent and mobile opt-in information are not shared with third parties for marketing purposes. We do not sell this information or use it to enroll you in marketing texts. Messaging infrastructure providers process phone numbers and message content only to operate requested communications; this operational processing is not permission for their own marketing.

If you choose optional SMS on a customer form, we record your phone number, yes/no choice, the exact disclosure and its version, the server-recorded submission time, form path, available account identifier, IP address and browser/user-agent information. This is evidence of your submitted communication choice, not evidence that a booking or payment succeeded. Entering a phone number or accepting general terms alone does not give SMS permission. Booking, inquiries and registration remain available without optional SMS consent.

Currently supported SMS includes responses to inquiries you initiate, inquiry follow-ups within that conversation, specifically requested secure booking/payment links and billing-related assistance. Joe may use a limited recent SMS history associated with the sending number to preserve context and avoid repeating questions; that number-based history is not authentication for viewing or changing a booking. Authenticated providers can separately request a one-time verification code; that request does not enroll them in recurring texts. Automated appointment reminders, confirmation campaigns and proactive service-update texts are not currently enabled. You can review service and appointment status in your account.

Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. We retain opt-out and consent evidence to honor your preference and resolve compliance questions. A checked web form does not override an earlier STOP; reply START from the same number to resume. We may provide a single opt-out confirmation or a requested HELP response. For support, call (845) 444-3833 or email support@giftedpros.com. SMS terms are at https://www.giftedpros.com/terms-of-service#sms.

1. Who we are and what this policy covers

GIFTED PROS LLC / Gifted Pros ("we", "our", or "us") connects customers with independent professionals for real-world home, automotive, technology and other services. This policy covers our website, customer and provider accounts, mobile application and related communications.

The information processed depends on your role, the features you use and the integrations enabled for those features. Browsing public services does not require an account; creating and paying for bookings and accessing private account or provider functions require authentication.

2. Information we collect

We process information you provide and information generated when you use our services, including:

  • Account and profile information: name, username, email, password credentials, account identifiers, role and account activity timestamps. Passwords are stored as hashes, not as readable passwords.
  • Contact and service information: phone number, email, postal code, service address, requested service and schedule, descriptions, vehicle/service preferences, quotes, booking status, approvals and transaction references.
  • Provider information: contact and professional profile details, offered services, rates, date of birth, identity/verification information, document-review results and submitted identification, business or insurance documents and face photographs. Do not submit identity documents through chat.
  • Communications and content: reviews, provider biographies, support or application submissions, Joe chat messages and telephone/SMS conversation content or transcripts where those channels are used.
  • Technical and security information: account/session identifiers, IP addresses, browser/user-agent information, security/audit events, request/error logs and operational records.
  • Payment information: amounts, checkout/payment status and payment-provider identifiers. Payment card and payout details are entered in Stripe-hosted flows; our implemented booking backend does not store raw card numbers or CVV codes.

3. Location, camera, audio and notifications

Addresses and postal codes you enter are sent to our service for requests and bookings. A foreground location feature can ask your device for high-accuracy location and use it locally to display nearby-provider information. The inspected implementation does not establish transmission of actual device GPS coordinates to our backend or Mapbox; other map screens may use fixed or illustrative locations. Permission access alone is not a promise of live tracking.

Provider verification can request camera access to capture a face photograph and upload it with verification documents. Some consultation interfaces request camera or microphone access, but a working remote audio/video connection or video upload has not been established. The current Android manifest does not declare microphone recording permission. Telephone calls to Joe use your phone/telephony service and Twilio, separately from in-app microphone access; speech may be processed into text for the assistant. We do not represent those calls as proof of in-app audio recording.

The implemented opt-in iOS notification-registration flow sends an installation identifier and APNs token to our authenticated backend. Android notification permission is declared, but operational Android push-token registration and notification delivery have not been established. A permission declaration or registration capability does not guarantee delivery.

You can control available location, camera, microphone and notification permissions in device/browser settings. Denying a permission may prevent its associated feature from working; it does not remove information already submitted.

4. How we use information

We use information to create and authenticate accounts, connect customers and professionals, prepare quotes, manage bookings and approvals, process payments through our payment provider, review provider applications and documents, respond to requests and send service or verification communications.

We also use operational and security information to prevent abuse, troubleshoot failures, maintain the service, resolve disputes and meet applicable legal obligations. AI-assisted communications may process the content you supply to answer questions or interpret service requests. Avoid providing passwords, card details, verification codes or unnecessary sensitive information in messages.

5. Recipients and third-party services

Relevant booking and contact details may be disclosed to the assigned professional to fulfill a service. Public provider profiles and reviews can be seen by other users. Do not include private information in public content.

We use third-party infrastructure and service providers for enabled features. These services process information under their applicable terms and privacy practices, which may involve processing in countries other than your own.

The following describes implemented or optional integration paths, not a claim that every integration is operational or that every user supplies data to every provider:

  • Stripe: hosted checkout and provider payout onboarding, payment amounts, customer/booking context and transaction identifiers.
  • Mapbox: map requests and map-view information. The full SDK telemetry/identifier payload has not been independently verified. External image/avatar hosts receive image requests; an avatar fallback can include a provider's name.
  • Twilio: phone numbers, verification or payment-link SMS, and telephone speech/transcription handling for Joe.
  • Email services, including Resend where configured: recipient and message information. Applicant-notification sending depends on configuration and verified sender setup.
  • AI services, including OpenAI-compatible and Replit-managed paths where configured: message text and relevant conversation/service-request context.
  • Hosting, database and object-storage infrastructure, including Replit and configured PostgreSQL/cloud storage services: records and uploaded files needed to operate the platform.
  • Optional identity comparison: code supports submitting identity and face images to AWS Rekognition for comparison. Current live operation has not been verified. We do not claim that every professional has a certified external background check.

6. Cookies, analytics and advertising

We use session cookies and local application storage for authentication and features such as saved request drafts and notification preferences. Operational logs and security events are separate from advertising analytics.

The inspected app does not include a third-party advertising integration. Optional Umami event hooks exist, but an active external analytics script was not identified in the inspected production page. We do not represent optional analytics hooks as verified active tracking. Third-party SDKs may process their own technical information as described in their policies.

7. Security

The public production service uses HTTPS, and the Android application is configured to reject cleartext web traffic. We use password hashing, authenticated access controls and private storage for provider uploads. These measures do not guarantee that every system or third-party connection is risk-free, or that all stored data is encrypted or hashed.

No method of transmission or storage is completely secure. Please protect your account credentials and contact us if you suspect unauthorized access.

8. Retention

We retain account, booking, communication, verification and operational information for as long as reasonably needed for the relevant service, application review, security, dispute resolution or applicable legal/accounting obligations. Retention needs differ by record type; we do not promise a fixed automatic deletion period that is not implemented.

After a deletion request, some payment, booking, fraud-prevention or legal records may need to be retained. Copies held in backups or by external service providers may be subject to their retention and deletion processes. A request is reviewed to determine what can be deleted and what must be retained.

9. Your rights and account/data deletion requests

Depending on applicable law, you may request access, correction, a copy of your information, deletion, or restriction/objection to certain processing. You can also withdraw optional device permissions. Where consent is the basis for processing, you may withdraw it without affecting processing already performed.

To request account deletion and deletion of associated personal data, email privacy@giftedpros.com with the subject 'Gifted Pros account/data deletion request'. Identify your account using its registered email or username and say whether you want to delete the account, particular data, or both. You can use the same address for other privacy requests or ask for help if you cannot access your account. Do not email your password, card number, identity document or verification code.

We may ask for proportionate verification of account ownership before acting. This is an email-request process, not an automated in-app deletion control. Submission of a request does not instantly delete records. Information required for legal, accounting, security or dispute purposes may be retained; ask us about the outcome and applicable exceptions.

You may have a right to complain to your local data-protection authority under applicable law.

10. Age and policy changes

Gifted Pros is intended for people aged 18 and over. Our terms require users to be at least 18. If you believe a child has submitted personal information, contact our privacy address.

We may update this policy as our service changes. The date at the top identifies this version. Material changes should be reviewed before continuing to use affected features.