Data Driver Privacy Policy

Effective version: DD-PP-2026-10-21-1 — October 21, 2026

This version applies prospectively when presented by Data Driver. Earlier agreement records remain unchanged.

1. Who we are and how to contact us

Pipeline Lite LLC dba Data Driver, 4950 Gulf Blvd, St Pete Beach, FL 33706, operates Data Driver. Email keith@pipelinelite.com for support, privacy questions, requests concerning your information or an appeal of a privacy response. You can also write to the business address above.

This Policy covers account holders, prospective users and people represented in contact records supplied through the service. It distinguishes information needed to run an account from contact records made available to customers. A feature described below is available only when enabled for your account and plan. A platform-access payment is not permission to contact people and does not waive their privacy rights.

2. Information we handle and where it comes from

Accounts and authentication. You provide an email login, password and any account or business details you submit. We maintain account and user identifiers, roles, account status, selected coverage, referral attribution and membership relationships. Passwords are stored as salted hashes. The account store maintains session and API-key hashes rather than their reusable secrets. Network requests also convey technical information needed to communicate with the service, such as an IP address and request headers; the account-record descriptions here do not promise that infrastructure providers keep no request logs.

Required customer setup. When customer onboarding is enabled, current and new customer and wholesaler users provide first and last name, mobile number, ideal industry and market segment, a public business website, and a confirmed United States business street address. These profile preferences do not change purchased data coverage. Setup status is separate from payment status. We retain profile, verification identity, challenge status, attempt counters, timestamps and limited provider outcome records with the account. We do not store verification codes. Twilio receives the mobile number to send and check a verification text. Standard message and data rates may apply.

Address lookup sends search text and selected place identifiers to Google Maps. Suggestions and raw lookup responses are temporary; we retain only the street address the user confirms for their account transaction and, if selected, its place identifier. Coordinates are not retained by this setup feature. Users may correct their address or enter it manually if lookup is unavailable. Google’s Terms of Service and Privacy Policy describe Google’s services and data handling. A public website address is sent to the Firecrawl cloud service to read the public home page. We retain a bounded text excerpt, its fingerprint, source website address and reading status as untrusted reference information. This content is not an instruction and does not change access, billing or data permissions. Website reading may fail independently of a completed profile and may be retried within operational limits. Do not submit private website links or credentials. These providers may process technical request information under their own policies. Request correction, deletion or help through the contact above; removal of required setup information can prevent account access. Historical payment and agreement records remain unchanged.

Payments and referral accounting. Stripe hosts payment entry when checkout is available. We send Stripe your login email, the relevant customer and account or membership identifiers, selected price, checkout return addresses and transaction-attempt metadata. Our payment records include customer, checkout, subscription, invoice, payment and refund identifiers; amounts and currency; plan and payment status; service periods; accounting adjustments; and event fingerprints or processing receipts. The platform's checkout form does not itself collect full payment-card numbers. Stripe handles the payment details submitted on its pages.

A personal referral link associates a signup with its direct referrer. We record that attribution, the member's paid status and qualifying collections and adjustments used to calculate commissions. A referral alone does not give the referrer access to a self-service customer's login, keys, private account or contact records. Member-facing accounting includes aggregate commission amounts and counts of attributable invoices and accounts. An administrator authorized to manage an account may see information within that account's permitted scope.

Selections, requests, agreements and downloads. We process topics, filters, requested quantities, selected coverage and accepted query proposals. We keep account-scoped request and delivery history, daily request reservations, source and query fingerprints, preparation status, counts, checkpoints, record or identity fingerprints and download-part information needed to prepare data and prevent duplicate or unauthorized delivery. Agreement records include a hashed account-login identifier, action and account references, the presented document and acknowledgment fingerprints, affirmative acceptance, timestamps and associated authorization references. An agreement receipt documents that action; it does not prove a contact-record subject consented to marketing. Source preparation also stores original supplier records and their provenance in the service's data storage.

Optional AI-assisted data guide. If you use the enabled guide, your request description and relevant topic, filter and catalog choices can be sent to Typesafe AI and, when its configured fallback is used, OpenAI to interpret the requested selection. The guide is designed around request descriptions and catalog metadata, rather than sending the contact rows being prepared for delivery. It applies input checks, but you should not put passwords, API keys, payment-card information, Social Security numbers or other sensitive personal details in a guide message. We keep account-scoped fingerprints, accepted draft selections and advisory result, status, usage and cost records. Automated suggestions require your acceptance and do not by themselves authorize a data request or download.

Supplier contact records. Available business and consumer records come from AudienceLab exports and existing inventory retained with source references. We preserve original supplier fields and provenance when preparing those records in our service. Fields available for a particular source or customer view vary. Categories can include names; personal and business email addresses and telephone numbers; postal addresses and locations; employer, role, education and employment history; business size, revenue and industry; online and social-profile identifiers; demographic, household, property, interest and economic attributes or estimates; suppression, validation and source-quality indicators; and record identifiers and timestamps. Original source schemas can also include inferred ethnicity or religion codes and credit-related attributes. Inclusion in a source does not establish that an inference is accurate or that its use is permitted for your purpose. We do not describe these records as consumer reports or authorize credit, insurance, employment, housing or other regulated eligibility decisions.

Support and privacy messages. We handle the contact details, description and supporting information you choose to send us to address the request. Start with the minimum information needed. Do not email passwords, reusable API keys, full payment-card details or unnecessary sensitive documents; we can discuss an appropriate verification method if one is needed.

3. Why information is used and who receives it

We use account and authentication information to sign users in, enforce account permissions and current coverage, and administer access. Payment and referral records associate verified collections, refunds and membership with the correct account, calculate the disclosed direct commission and reconcile duplicate or uncertain transactions. Request, source and agreement records support the selection you accept, daily limits, source validation, preparation, delivery and the evidence of authorization. Support information is used to investigate your question, correct errors and handle privacy requests. We also use relevant records to investigate security incidents or misuse, resolve disputes and meet applicable legal obligations.

The service uses Railway for application hosting, Supabase for native data storage and processing, AudienceLab for source data and exports, and Stripe for enabled billing and payment functions. Typesafe AI and OpenAI receive the limited guide context described above when those guide functions are used. Hosting and communications providers necessarily handle the information used to provide their services. These statements do not mean every provider receives every category of information.

Authorized customers receive the contact records their permitted requests return. Their own personnel and contracted processors may handle those records only within the own-use, security and no-resale restrictions in the Terms and Responsible Use Agreement. That contractual restriction does not remove a person's privacy rights. We may disclose information reasonably needed to professional advisers, in response to a lawful request or legal obligation, to address fraud or security incidents, or in connection with a lawful business transfer, subject to applicable protections. Those are permitted purposes, not a claim that such a transfer has occurred.

Making contact records available to customers for paid platform access may constitute a sale or another regulated disclosure under applicable privacy law. The price being described as platform access does not determine that legal treatment. We do not promise that information is never sold or shared. Section 6 explains how to submit a request concerning information about you; accepting an agreement is not consent on behalf of a person in a record.

4. Cookies, choices and security

The account page uses the `__Host-ddnew_session` authentication cookie, marked Secure, HTTP-only and SameSite=Strict, with an eight-hour browser lifetime. Signing out invalidates that session and clears the cookie. Blocking that cookie can prevent account sign-in. The account page does not embed an advertising pixel or an analytics script and makes its application requests to the platform's own origin. Payment actions can navigate to Stripe-hosted pages, which have their own browser behavior. These statements about the account page do not describe every log or page operated by a service provider.

The current account software does not provide an automated Global Privacy Control or Do Not Track preference-processing feature. You can send a privacy request to the contact in Section 1 without creating an account. This description does not limit any obligation to provide or honor a legally required privacy control; a policy statement is not a substitute for that control.

Safeguards in the account and data paths include account-scoped permissions, origin and request checks, salted password hashing, token hashing and encryption of private export-coordination values. They do not establish that every stored record, log or backup is encrypted. No system can guarantee absolute security. Keep your credentials private and report suspected unauthorized access to keith@pipelinelite.com.

5. Retention and deletion

Our retention policy is to keep information only while needed for its disclosed lawful purpose, assessed by record category rather than one automatic deletion period. Relevant criteria are whether the account or requested service is still active; whether a source record is still needed for the authorized inventory and delivery purpose; whether a payment, refund, commission, dispute or legal obligation remains open; whether a record is needed to demonstrate an agreement, investigate misuse or maintain a lawful suppression choice; and whether a support or privacy matter has been resolved. Records must not be kept merely because storage is available. We will delete or de-identify information when no disclosed lawful purpose or applicable preservation duty remains. These are current policy commitments, not a statement that every historical record has already been reviewed or deleted.

The account and agreement software does not currently run a general age-based deletion schedule. An eight-hour session expiry, an expired agreement challenge, a guide-cache expiry, a logout or a subscription cancellation is not deletion of the associated account, payment, agreement, source or request history. Expiring authorization or reuse does not by itself erase a stored record. Existing source and coordination records may remain after a request or download finishes. This Policy promises no automatic 30-day or 45-day purge.

Submit deletion and correction requests through the contact in Section 1 for individual review. This request channel does not promise automated processing or represent a history of completed requests. A request can require review of source copies, affected service providers, records needed for an applicable exception and any backup or preservation obligations; the account software does not automatically delete every downstream copy when you send an email. We will explain an applicable limitation or exception in responding to your request. An accounting or legal exception does not justify indefinite retention of unrelated personal information.

6. Privacy rights and communications

Depending on applicable law and your circumstances, rights can include access or knowledge, correction, deletion, portability, objection or restriction, opting out of sale or certain sharing or targeted advertising, limiting certain uses of sensitive information, and an appeal. You do not have to buy access or create an account to contact us about a record concerning you. A contract or privacy acknowledgment cannot waive a mandatory right.

For access, correction, deletion, or Do Not Sell or Share My Personal Information requests, email keith@pipelinelite.com or write to the address in Section 1. Describe the right you want to exercise and enough information to locate the relevant account or record. We may ask for information reasonably needed to verify a request or an authorized agent, taking account of the kind of request and the risk of disclosing someone else's information. Do not send unnecessary sensitive documents in the initial message. Verification must not be used to obstruct a request that applicable law does not require us to verify. We will address requests within applicable legal requirements, without unlawful discrimination for exercising rights, and explain a refusal or necessary extension. To seek an available appeal, reply to the response or contact the same address with the subject “Privacy appeal” and identify the earlier request. You may also complain to the appropriate privacy regulator.

Account closure, subscription cancellation, marketing unsubscribe and a request to delete personal information are different actions. Tell us which action you need. We may need to preserve minimum suppression or request records to respect an opt-out and avoid contacting you again. Acknowledging this Policy is not consent to optional marketing. Customers remain responsible for outreach they conduct or authorize, and Data Driver remains responsible for its own communications and legal duties.

7. United States coverage, intended users and changes

Data coverage is limited to the United States. This is a limit on the records and service coverage, not a promise that every provider, processor, log, backup or authorized access location is within the United States. The service does not provide a country-by-country guarantee for all processing. Contact us about a particular processing or recipient question.

The platform is intended for adults and is not directed to children under 13. Do not create an account if you are under 18, submit children's information to the guide or use the service to seek information about children. The software does not automatically verify a user's age; these restrictions are service-use rules, not a claim that an age check has occurred. Report a concern about a child or an inaccurate sensitive attribute to the contact in Section 1.

We will identify the version and effective date of the Policy made current and provide material-change notices and additional choices as applicable law requires. Changes do not silently rewrite earlier agreement receipts or remove rights concerning earlier processing.