Privacy notice & SMS terms

What we collect

When you create an account we collect: your name, your mobile phone number, your state and city, your preferred language, and which kind of participant you said you are (driver/professional, employer, or service provider).

We also keep consent records — which disclosure text you agreed to, in which language, when, and from which device — and standard session cookies that keep you signed in. Sign-in attempts and security-code deliveries are logged.

If you're a driver/professional, once you're verified you can build a talent profile: your general location, whether you're in a driving or non-driving role and your category, years of experience, any federal endorsements, a safety self-report, your equipment, your credentials and their expiration dates, your route preference, and a headline and short "about" section you write yourself. We don't collect detailed work history yet; when that feature launches, this page will describe it before it applies to you. If you choose identity verification, we also collect images of your government-issued ID, the details printed on it, and images from a live face check. That is described in full under Biometric data & identity verification below.

If you set up a Company or Recruiting Company Workspace, we collect the organization facts you provide, including its legal name, optional DBA, business type, industry, description, selected contact details and hours, location facts, and optional USDOT and MC numbers. We do not ask you to type an EIN. If you submit business proof, we collect protected images of the IRS letter assigning the EIN and the state formation document; if company vehicles apply, we may also collect a certificate of insurance. Independent Recruiter setup creates a person-role profile, not a Business or company team.

If you invite someone to join your company's team, we store the email address you invited — even if that person never creates a Lerabase account or never accepts the invitation.

How we use it

To create and secure your account (email and password, or Google or Microsoft, for everyday sign in, with email codes as a fallback), to show the site in your language, and to prepare local job and business matching. If you sign in with Google or Microsoft, they send us your name and email address. We use them only to sign you in.

We don't sell your personal information.

If you're a driver/professional, once your profile is live it has a public card that anyone with its link can see: your first name and last initial, your general role and category, your general area (state/region, not your exact city), the verified shield if you're verified, your years of experience, and your headline. That public card is discoverable by search engines by default — you can turn that off any time from your profile, and the card stays reachable by direct link either way. Nothing else on your profile (your endorsements, equipment, credentials, seeking status, or your full "about" text) is shown at that level. If someone views your profile while signed in to their own account, we may show YOU their display name as part of a simple view count on your dashboard — this never works the other way around.

Biometric data & identity verification

If you choose to get verified, you photograph your government ID and complete a short live face check with your camera. This is optional — you decide to start it, and you can stop at any time.

Your ID text is read by Google (Gemini) to pull the printed details, and the live face check is run by Amazon Web Services (AWS) to confirm you are a real, live person who matches the photo on your ID. The camera streams directly to AWS. We instruct these providers to process your images solely to perform the check, and we do not permit them to use your images for any other purpose. Google's paid tier is used deliberately: its terms exclude customer data from model training, which is a requirement for government-ID information. Images sent for verification may be briefly retained by these providers for abuse monitoring — no longer than 30 days — before deletion.

We do NOT create or store facial-recognition templates or 'faceprints'. We keep only the plain result (verified or not) and the details printed on your document, such as license class and expiration date.

Your ID and face-check photos are automatically and permanently deleted 30 days after a decision. If a submitted ID shows the person is under 18, the check stops and those images are deleted immediately.

You give explicit consent before the camera opens, and every step is recorded so we can show the check was done properly.

Retention schedule and destruction guidelines: your ID images and face-check images are permanently destroyed 30 days after a verification decision, or when the purpose for collecting them has been satisfied, or within three years of your last interaction with Lerabase — whichever comes first. Destruction runs automatically every day. We do not sell, lease, trade, or otherwise profit from your biometric identifiers or biometric information. This paragraph is our public written policy for biometric retention and destruction.

Breach response: if this biometric data is ever involved in a security breach, we notify the people affected and any authorities the law requires without unreasonable delay. This paragraph is that response protocol, published here as part of our written biometric policy, as Colorado and other states require.

Texas residents: your consent above is given before any photograph or face scan is captured, as the Texas Capture or Use of Biometric Identifier Act requires.

Who processes it

Lerabase runs on a small set of service providers: Supabase (database and authentication, U.S. region), DigitalOcean (hosting, U.S.), Telnyx (text-message delivery), and Cloudflare (domain and security checks). Identity verification additionally uses Google (reading the text on your ID) and Amazon Web Services (the live face check). If you're verifying a company, Google also reads the business documents you submit — your EIN letter, formation certificate, and certificate of insurance. Each receives only what its job requires, and images sent for verification may be briefly retained by these providers for abuse monitoring before deletion.

No mobile information is shared with third parties or affiliates for marketing or promotional purposes. Text-messaging opt-in data and consent are never shared with any third party. Sharing with subcontractors who provide support services, such as customer service and message delivery, is permitted.

How long we keep it

Account data lives as long as your account does. Security and sign-in logs are kept for a limited operational window.

Consent records are kept even after account deletion, because U.S. texting rules require us to be able to prove consent existed.

Identity-verification photos (your ID and the live face check) are automatically deleted 30 days after a decision — sooner for anyone found to be under 18. We never keep facial-recognition data.

Business documents you submit for company verification — your EIN letter, formation certificate, and certificate of insurance — are kept while your company account is active, and deleted if the company is dissolved or its owner deletes their Lerabase account.

Deleting your account

You can delete your account any time from Account settings. It requires a final text code, and it permanently removes your account and profile data.

We never keep your government-ID images or the contents of your identity documents.

For legal compliance, as described above, we keep three things: your consent history, a final account snapshot, and a log of verification activity (timestamps, IP address, and reviewer actions).

SMS program terms

DriverJobz Inc. sends one-time security codes by SMS when you request them for signup, recovery, or a sensitive account action. Message frequency varies with your use. Message and data rates may apply.

Marketing texts are separate and strictly opt-in — you'll only get them if you turn them on, and you can turn them off in Account settings or by replying STOP.

Reply HELP for help or STOP to stop at any time. Carriers are not liable for delayed or undelivered messages.

Consent to receive text messages is not a condition of using Lerabase or of any purchase.

Self-reported information

Everything users enter on Lerabase is self-reported by them. Lerabase is not a staffing agency and does not guarantee any user's information; verification features, where offered, check specific documents and signals, but responsibility for accuracy stays with the person who provided the information.

Contact

Questions, requests, or corrections: [email protected]. We answer as fast as a small team honestly can.