BlesenaBack to Blesena ↗

Blesena · Connecticut

Privacy policy

How we handle your information when you request a service, work with Blesena, or contact our team.

Updated September 8, 2026

About this policy

This Privacy Policy explains how Blesena collects, uses, shares, and retains information through our mobile app, websites, customer support, and related services. Blesena connects customers in Connecticut with independent mechanics for roadside assistance and pre-purchase vehicle inspections.

This policy covers customers, mechanics, and people who contact us. Please also read our Terms of Service.

Information we collect

Account and verification information

Name, email address, phone number, account identifier, selected role, account creation dates, sign-in credentials handled by our authentication provider, and phone-verification status and timestamps. When you choose Google sign-in on a supported platform, we receive the Google account information needed to sign you in, such as your name, email, and authentication identifier.

Phone verification uses your phone number, verification code, verification result, and short-lived verification identifiers. We also record verification attempts and security rate-limit information, which can include a hashed network address, to limit abuse.

Mechanic qualifications and identity verification

Mechanic applications include a business address, phone number, ASE certificate number and expiration, certificate and insurance documents, equipment confirmation, application status, and review history. These uploaded qualification documents are private and available to the applicant and authorized Blesena administrators.

Stripe Identity collects a government-issued identity document and selfie directly from the mechanic. Stripe may use biometric information to compare the selfie with the identity-document photograph, subject to the consent and disclosures Stripe presents. Blesena compares the verified name returned by Stripe with the legal name in your application and stores the comparison result, verification session reference, status, timestamps, and failure category; this integration does not copy the identity-document images, selfie images, government ID number, or biometric template into Blesena’s database. Stripe identity verification is separate from approval of a mechanic’s qualifications and payout account. Blesena and Stripe each act as independent controllers of personal information for their own processing purposes. Stripe also processes information to provide services to Blesena and uses information to operate and improve its risk and identity-verification services under its own privacy policy. Identity verification helps prevent impersonation and misuse of the platform; it is separate from the review of mechanic qualifications.

Agreements and electronic signatures

We store the complete agreement version presented, document hashes, your typed legal name, typed or drawn electronic signature, affirmative acceptance and electronic-record consent, account identifier, signing email, and server-recorded signing time. You can view your saved agreement in your account. Signed agreements may be retained as needed to establish the terms accepted and handle legal obligations or disputes.

Vehicle and service information

Service type, vehicle make, model and year, vehicle identifiers such as a VIN when supplied, vehicle condition, service choices, address, seller details, appointment time, instructions, notes, request and assignment identifiers, service status and timestamps, inspection answers and recommendations when provided, and cancellation or refund reasons. Please only provide another person's information when you have permission or another valid basis to do so.

Location

Customers confirm the vehicle’s precise location and address for roadside and inspection requests. With explicit permission, Blesena collects mechanics’ precise location while they are online and during active services, including in the background and while the screen is locked. These readings enable nearby offers, customer tracking, and arrival checks. Availability sharing stops when the mechanic goes offline; active-service sharing ends with the service. Customers receive only their assigned mechanic’s service location. We store coordinates, accuracy, device sample time, server receipt time, reported mock-location indicators, and arrival-verification evidence. GPS is evidence of proximity, not an absolute guarantee of physical presence. Addresses and map searches also reveal location. Address search sends the text you enter and a temporary search-session identifier to Google Maps through our authenticated server. We keep private usage counters to limit abuse; these counters contain no searched addresses and expire within 48 hours, with hourly cleanup.

Messages, support, and content

In-app chat messages, participant names and identifiers, message timestamps, unread/read markers, message retry identifiers, notification delivery receipts, support descriptions, categories, urgency, preferred contact methods, and support review notes. If you choose to provide photos, videos, or other files through an available support channel, we receive those files and associated metadata, such as filenames and media types. Selected media may also include embedded location information. Do not include unrelated personal information.

Chat is screened for contact-sharing and off-platform arrangements. We record moderation events, masked excerpts, warnings, account restrictions, and review decisions. Authorized personnel may review messages and reports to investigate safety, fraud, disputes, or policy violations.

Payments, agreements, and mechanic onboarding

Order amounts, payment and transaction identifiers, payment-method references, authorization and expiry status, consent to save a payment method for an appointment, captured amounts, refunds, fees, payout records, and dispute information. Stripe processes payment details; Blesena does not store full payment-card numbers. Billing contact details you provide may be sent to Stripe. Mechanics provide payout, identity, business, and bank information to Stripe during onboarding; Blesena receives the connected-account identifier, verification requirements, onboarding status, and payout eligibility.

We also collect service-agreement signatures, acceptance status, acceptance time and agreement version; mechanic application information such as experience, certifications and service area when supplied; and approval status, tier, availability, job totals, earnings, ratings, and account-standing records.

Device, notification, and technical information

Push-notification tokens if enabled (service alerts use generic text without message bodies or phone numbers), app and device information needed by our service providers, IP addresses, request times, error and security logs, and authentication/session information. The app stores session information on your device to keep you signed in. Hosting and infrastructure providers process technical access logs when you visit a page or use the service.

Our sign-in and payment providers also process device and account identifiers, approximate location, and information about interactions with sign-in and payment features for service operation, fraud prevention, and analytics. Provider disclosures identify some of this information as linked to account or payment identifiers. See Google Sign-In privacy details and Stripe mobile SDK privacy details.

How we use information

  • Create and secure accounts, verify phone numbers, and manage customer and mechanic access.
  • Match, schedule, dispatch, coordinate, and document vehicle services.
  • Process payments, refunds, transfers, payouts, and disputes.
  • Deliver service communications and permitted notifications.
  • Respond to support and privacy requests, investigate misconduct, enforce agreements, and prevent abuse.
  • Maintain service reliability and meet accounting, security, and legal obligations.

Who receives information

  • Service participants: customers and eligible mechanics receive information needed to coordinate work, including names, request details, vehicle details, messages, service addresses, and relevant location updates. Before assignment, the mechanic receiving a private offer sees service type, approximate area, distance, offered earnings and appointment time. Other mechanics cannot read that offer. Exact customer details, personal notes and the full request are restricted to the customer, assigned mechanic and authorized administrators.
  • Google / Firebase: authentication, database, hosting, infrastructure, maps, address search and related technical processing. A map or address search sends the relevant location or search text to the map provider.
  • Stripe: payment processing, fraud prevention, refunds, identity-document and selfie verification, and mechanic payouts.
  • Telnyx and delivery carriers: phone-verification messages, delivery and verification processing.
  • Expo, Apple, and Google notification services: app delivery/update services and notification processing where enabled.
  • Authorized support and administrators: account, transaction, service and moderation information needed for their work.
  • Legal and business needs: disclosure when required by law, to protect safety or legal rights, or as part of a business transfer subject to applicable protections.

We do not sell personal information or use it for targeted advertising. Third-party services also process information under their own policies: Google, Stripe, Telnyx, and Expo.

Retention and deletion

Raw mechanic location samples expire after 24 hours and arrival evidence after 90 days, unless a documented dispute hold requires retention. An hourly cleanup removes expired records. Service addresses, signed agreements, and transaction evidence may have separate retention needs described below. Notification-delivery receipts expire after seven days. Booking, inspection, and message drafts are stored on your device to recover interrupted work and are cleared after successful submission or account cleanup.

We keep account and service information while needed to provide the service. We may retain payment and refund records, agreements, service records relevant to a dispute, fraud or security records, and correspondence where needed for accounting, legal obligations, safety, or resolving disputes. Retention depends on the record and the reason it is needed; there is no single retention period for all data.

When processing a verified deletion request, we delete or de-identify account information that is no longer needed and explain any applicable retention exceptions. We remove mechanic qualification uploads during account deletion and request redaction of applicable Stripe Identity sessions. Stripe completes redaction asynchronously under its policies. Signed agreements and associated acceptance evidence may be retained for legal obligations and disputes. Daily database backups are retained for 14 days and weekly backups for eight weeks. Point-in-time recovery history is retained for up to seven days. Deleted records may remain in these restricted recovery copies until expiration; recovery procedures require deletion requests to be reapplied before restored data is made available. Service-provider records may remain for their own retention cycles. Removing the app from your phone does not delete your account.

See Account & data deletion for an accessible way to request deletion without reinstalling the app. Requests may require identity verification and resolution of active services, payments, or disputes. We will communicate the expected completion time and any retained categories when handling your request.

Your choices and requests

  • Change location and notification permissions in your device settings. Denying location can prevent roadside dispatch from identifying where to send assistance.
  • Use your device's photo picker to control what you share; avoid sharing unrelated media.
  • Contact us to request access, correction, deletion, or information about how we use your data. Rights available to you depend on applicable law.
  • You may request account deletion from your profile in the app or use the web deletion instructions.

Send privacy requests to developer@blesena.com. We may request enough information to verify that you control the relevant account. Do not send passwords, verification codes, full card numbers, or identity documents in an initial email.

Security and processing locations

We use technical and organizational safeguards, including authenticated access, encrypted connections to service providers, and role-based access rules. No system is completely secure. Our providers may process information in the United States and other locations where they operate.

Age eligibility

Blesena is intended for adults aged 18 and over, consistent with our Terms. It is not directed to children, and we do not knowingly collect personal information from children under 13. Contact us if you believe a child has provided personal information so we can investigate and address it.

Policy updates and contact

We may update this policy as our service changes. The updated date appears at the top of this page. Where required, we will provide additional notice or obtain consent.

Privacy, support, and deletion requests: developer@blesena.com.