Privacy Policy

This Privacy Policy explains how Ridewolf, Inc., a Delaware, United States — Corporation (Inc.) company with its principal place of business at 2093 Philadelphia Pike 2255, Claymont, DE 19703-2424, United States (“Ridewolf,” “we,” “us,” or “our”), collects, uses, discloses, stores, transfers, retains, and otherwise processes personal data and related information in connection with our website, software, dashboards, mobile applications, APIs, white-label deployments, support, and related business activities.

This Privacy Policy should be read together with the Ridewolf Terms of Use, any applicable Order Form, Data Processing Addendum (“DPA”), Cookie Notice, and any product-specific or jurisdiction-specific disclosures that may apply.

By accessing or using our website, products, or services, or otherwise interacting with Ridewolf, you acknowledge that you have read and understood this Privacy Policy.

Ridewolf provides business-to-business software, platform, telematics, fleet, mobility, and related technology services. Ridewolf does not generally provide transportation, rental, vehicle-access, or consumer mobility services directly to the public. Where personal data is processed through a Ridewolf-powered service operated by a Customer, Ridewolf typically processes such information on behalf of that Customer, except to the extent Ridewolf separately processes data for its own business purposes as described in this Privacy Policy.

1. Scope of This Privacy Policy

This Privacy Policy applies to personal data and related information that Ridewolf processes when:

• you visit our website or other online properties;
• you request a demo, fill out a form, contact us, or otherwise communicate with us;
• you create, administer, or use an Account;
• you use our Products, Services, Apps, APIs, dashboards, portals, or white-label deployments;
• you purchase, subscribe to, implement, or receive our Products or Services;
• you interact with a customer-branded or co-branded deployment powered by Ridewolf, to the extent this Privacy Policy is presented or made applicable; or
• we otherwise process information in connection with our business, support, operational, legal, compliance, billing, fraud-prevention, analytics, or security activities.

This Privacy Policy does not govern personal data that a Ridewolf customer processes outside of the Ridewolf Products or outside of Ridewolf’s role in providing the Products.

2. Role of Ridewolf: Controller vs. Processor

Ridewolf provides technology Products and Services primarily to business customers. Depending on the context, Ridewolf may act either as:

• a controller (or equivalent concept under applicable law), where we determine the purposes and means of processing for our own business purposes; or
• a processor, service provider, or subprocessor, where we process personal data on behalf of a Customer and under that Customer’s instructions.

2.1 When Ridewolf acts as controller

Ridewolf generally acts as controller with respect to personal data relating to:

• website visitors;
• individuals who submit demo requests, forms, or other inquiries;
• Customer representatives, Administrators, billing contacts, and business contacts;
• reseller, partner, vendor, and service-provider contacts;
• event, webinar, and marketing subscribers;
• support contacts;
• applicants, where applicable;
• security, fraud-prevention, and corporate administration records; and
• legal and compliance-related processing carried out for Ridewolf’s own business purposes.

Ridewolf acts as controller with respect to personal data submitted directly to Ridewolf through the website, demo-request forms, contact forms, sales inquiries, onboarding discussions, vendor or partner communications, webinar or event signups, support requests, and similar direct business interactions.

2.2 When Ridewolf acts as processor or service provider

Ridewolf generally acts as processor or service provider where personal data is processed by or through the Products on behalf of a Customer, including where the Products process or host:

• Authorized User information;
• End User information;
• reservation, booking, and access records;
• Vehicle Data;
• trip, geolocation, or telematics records;
• support or operational records submitted by the Customer;
• customer-configured communications or workflows; and
• other Customer Data processed through the Products on the Customer’s behalf.

Where Ridewolf acts as processor or service provider, the relevant Customer generally determines the purposes of processing, the applicable legal basis, the required end-user notices, and the Customer-facing compliance framework, subject to the applicable agreement and DPA.

If you are an End User, driver, renter, rider, passenger, employee, contractor, or other individual whose data is processed through a Ridewolf-powered service operated by one of our Customers, you should refer first to that Customer’s privacy notice and customer-facing terms.

Customer remains solely responsible for determining whether separate or additional privacy notices, employee-monitoring notices, mobility, transport, rental, geolocation, telematics, workplace, consumer, or other jurisdiction-specific disclosures are required for its End Users, drivers, renters, riders, passengers, employees, contractors, or other individuals, and for ensuring that any such notices or disclosures are provided in accordance with applicable law. Customer also remains solely responsible for determining and implementing any legally required consent, acknowledgment, authorization, or other lawful basis for such processing, except to the extent Ridewolf expressly agrees otherwise in writing.

Except to the extent expressly stated otherwise in a written agreement, Ridewolf does not independently determine the customer-facing operational purposes for which personal data is collected, used, disclosed, retained, or otherwise processed through the Products on behalf of a Customer.

For clarity, where a Customer uses the Products to interact with its riders, renters, drivers, employees, contractors, fleet users, or other End Users, the relevant Customer is generally responsible for providing the primary customer-facing privacy notice, operational disclosures, workforce-monitoring notices where applicable, geolocation disclosures, telematics notices, and any legally required consent or acknowledgment flows.

3. Categories of Information We Collect

Depending on the context, our relationship with you, and the Products or Services involved, we may collect the following categories of information.

3.1 Website and business interaction data

When you visit our website or otherwise interact with Ridewolf in a business context, we may collect:

• your name, employer, title, and role;
• your email address, phone number, and business address;
• contact form submissions;
• demo request details;
• marketing preferences;
• event or webinar registration details;
• communications and correspondence; and
• any other information you voluntarily provide.

3.2 Account and administrative data

When an Account is created or administered, we may collect:

• Account identifiers;
• workspace, tenant, or organizational information;
• Administrator details;
• Authorized User details;
• login and authentication information;
• roles and permissions;
• audit trail information;
• settings and preferences; and
• account-related communications.

3.3 Product, technical, and usage data

When the website, Apps, APIs, or Products are accessed or used, we may collect:

• IP address;
• browser type and version;
• device type and device identifiers;
• operating system;
• app version;
• network and connection information;
• timestamps;
• log data;
• session information;
• crash and diagnostic data;
• authentication logs;
• API usage records;
• performance metrics; and
• Usage Data and Metadata generated through the operation of the Products.

3.4 Platform and operational data

Depending on the Product configuration and Customer’s implementation, Ridewolf may process operational data submitted to, stored in, transmitted through, or generated by the Products, including:

• reservation and booking records;
• access records;
• trip history;
• service usage records;
• communications and support records;
• customer-defined workflows;
• uploaded files, forms, notes, or settings; and
• other Customer Data associated with the Customer’s business operations.

Depending on the Product configuration, users may also submit or upload photographs or other images for operational, support, verification, parking, vehicle-condition, incident-reporting, compliance, or ride-completion purposes.

3.5 Geolocation, telematics, and Vehicle Data

Depending on the Product, hardware, app permissions, and Customer configuration, Ridewolf may process Vehicle Data and related operational information such as:

• precise or approximate geolocation data;
• vehicle location and movement data;
• trip start and end records;
• lock/unlock events;
• access-control events;
• geofence events;
• mileage or utilization records;
• battery and charging data;
• telemetry and diagnostic information;
• hardware, gateway, controller, or firmware events; and
• other data associated with connected vehicles, mobility assets, or fleet operations.

For clarity, geolocation or location-related data processed through the Products may relate either to a connected vehicle or mobility asset, or, where enabled by the Product and permitted by the relevant user, to the mobile device location of an Authorized User or End User for app functionality, operational, security, or location-based service purposes.

3.5A Employee, Contractor, and Workforce Monitoring Context.

Certain Product features may be used by Customers in connection with workforce, fleet, operational, or access-management activities involving employees, contractors, or other personnel. Ridewolf does not determine whether such use is subject to specific workplace-monitoring, employment, labor, union-consultation, or similar legal requirements. The relevant Customer remains solely responsible for assessing and complying with any such requirements and for issuing all legally required notices, disclosures, policies, or acknowledgments.

3.6 Mobile app permissions and device features

Our Apps may request access to certain device permissions or features where relevant to Product functionality, including:

• location services;
• camera;
• photo library or device storage;
• Bluetooth;
• NFC;
• push notifications; and
• biometric authentication or similar local device features.

If certain permissions are denied or disabled, some features of the Products may not function correctly or may be unavailable.

Camera access may be used, where applicable, to scan QR codes, upload verification materials, capture operational images, document vehicle condition or damage, verify parking or ride completion, or support customer service and incident-resolution workflows.

3.7 Cookies and similar technologies

We and our service providers may use cookies, SDKs, pixels, tags, local storage, and similar technologies to collect information relating to use of our website, Apps, and services. These technologies may support authentication, session management, security, preferences, performance, analytics, and permitted marketing or lead-measurement activities.

3.8 Information from third parties

We may receive information from third parties, such as:

• Customers and their Administrators;
• resellers, implementation partners, and Affiliates;
• payment processors;
• identity, verification, fraud-prevention, or compliance providers;
• cloud, hosting, analytics, communications, and customer support vendors;
• app stores and platform providers;
• marketing and lead-generation providers; and
• public or other lawful external sources.

3.9 Aggregated, de-identified, and inferred information

We may generate Aggregated Data, Metadata, Usage Data, and other de-identified, statistical, or inferred information from the use of the Products, to the extent permitted by applicable law.

4. How We Use Information

We may use personal data and related information for the following purposes:

• to provide, host, operate, maintain, support, and improve the Products and Services;
• to authenticate users and administer Accounts;
• to provide dashboards, portals, Apps, APIs, and white-label deployments;
• to operate reservation, booking, access-control, telematics, analytics, or connected-asset functionality where configured by the Customer;
• to provide onboarding, implementation, Professional Services, support, and troubleshooting;
• to communicate with Customers, users, prospects, vendors, partners, and service providers;
• to send transactional, billing, administrative, operational, contractual, legal, or security-related communications;
• to monitor service integrity, performance, security, abuse, fraud, and misuse;
• to investigate incidents, troubleshoot problems, and preserve relevant records;
• to analyze usage, improve functionality, and develop service enhancements;
• to process payments, invoicing, collections, and accounting-related matters;
• to comply with applicable laws, regulations, subpoenas, court orders, tax requirements, audit obligations, or lawful requests from authorities;
• to establish, exercise, or defend legal claims;
• to conduct internal business operations, reporting, due diligence, restructuring, financing, insurance, and corporate administration activities; and
• where permitted by law, to send marketing communications and manage lead-generation or business-development activities.
• where permitted by applicable law, Ridewolf may monitor, review, or record calls, support interactions, or other communications for training, quality assurance, support, security, documentation, compliance, or dispute-resolution purposes.

5. Legal Bases for Processing

Where required by applicable law, Ridewolf relies on one or more of the following legal bases for processing personal data:

• performance of a contract;
• steps taken at your request before entering into a contract;
• compliance with legal obligations;
• legitimate interests, including operating and improving the Products and Services, managing business relationships, protecting the security and integrity of the Products, preventing fraud and abuse, and exercising or defending legal rights;
• consent, where required; and
• any other lawful basis expressly recognized under applicable law and applicable to the relevant processing context.

Where Ridewolf processes personal data solely on behalf of a Customer through the Products, Ridewolf generally does not independently determine the legal basis for the Customer’s processing activities. In such cases, the relevant Customer remains responsible for determining and documenting the applicable lawful basis and for providing required notices to the relevant individuals.

6. How We Disclose Information

We may disclose personal data and related information to the following categories of recipients, as appropriate:

• our Affiliates and group companies;
• hosting, infrastructure, cloud, analytics, security, communications, support, payment, identity, verification, compliance, and other service providers;
• subprocessors engaged to provide or support the Products and Services;
• resellers, implementation partners, distributors, or referral partners involved in the relevant commercial relationship;
• professional advisers, auditors, insurers, lenders, and financing counterparties;
• app stores, integration partners, and third-party platforms used in connection with the Products;
• competent authorities, regulators, courts, law enforcement agencies, tax authorities, or other third parties where disclosure is required or permitted by law;
• counterparties and advisers in connection with an actual or proposed merger, acquisition, restructuring, financing, sale of assets, reorganization, bankruptcy, or other corporate transaction; and
• any other party where disclosure is made at your direction, at the Customer’s direction, or with appropriate consent or legal authorization.

We may also disclose Aggregated Data, Metadata, Usage Data, or other de-identified information that does not identify an individual, except where applicable law provides otherwise.

6.1A Service Providers and Subprocessors.

Ridewolf may use hosting providers, infrastructure providers, communications providers, analytics providers, support tools, verification vendors, cloud-service providers, and other subprocessors or service providers to deliver, secure, support, and improve the Products and related business operations. Where required by applicable law or contract, additional information regarding relevant subprocessors may be made available through a separate subprocessor list, Data Processing Addendum, customer request process, or contractual disclosure mechanism.

7. White-Label and Customer-Branded Deployments

Ridewolf may provide White-Label Services or other customer-branded, embedded, or co-branded deployments.

In those cases:

• the relevant Customer may present the service under its own brand, domain, and customer-facing legal terms;
• Ridewolf may remain the underlying provider of the platform, infrastructure, or technology;
• the Customer generally remains responsible for its own privacy notices, end-user terms, consent flows, and legally required disclosures to its End Users;
• Ridewolf may process personal data on behalf of the Customer as processor or service provider; and
• Ridewolf may independently process limited information for its own security, support, billing, fraud prevention, service integrity, legal compliance, account administration, and protection of the Products, where permitted by law and the applicable contract.

8. Cookies and Similar Technologies

Ridewolf uses cookies and similar technologies for purposes such as:

• maintaining sessions and authentication;
• remembering settings and preferences;
• securing the website and Products;
• measuring performance and functionality;
• understanding website and Product usage;
• improving user experience; and
• supporting permitted analytics, communications, or marketing-related activities.

Depending on the jurisdiction and service, cookies may include:

• strictly necessary cookies, required for core functionality and security;
• functional cookies, used to remember preferences and settings;
• analytics cookies, used to understand usage and performance; and
• advertising or measurement cookies, where permitted and used.

Where required by applicable law, Ridewolf will request consent before placing non-essential cookies or similar technologies on your device.

Additional information may be provided in our Cookie Notice or cookie banner.

Depending on the applicable website, Product, or jurisdiction, users may be able to manage cookie preferences through browser settings, cookie banners, consent-management tools, or other controls made available by Ridewolf or relevant third parties.

9. Restricted or Sensitive Data

Unless expressly supported by the applicable Product and expressly approved by Ridewolf in writing, the Products are not intended for storage or processing of:

• full payment card data or sensitive authentication data;
• protected health information or comparable regulated health data;
• biometric templates;
• special-category or highly sensitive personal data under applicable law;
• personal data relating to children;
• government-issued identification data beyond approved and supported workflows; or
• criminal records or background-check data except through expressly approved and supported workflows.

Customers are responsible for ensuring that they do not submit or instruct Ridewolf to process data categories that are not intended for the Products or that require contractual, technical, or legal controls not expressly provided by Ridewolf.

Ridewolf may delete, restrict, quarantine, or otherwise refuse to process data submitted to the Products where Ridewolf reasonably determines that such data falls outside the intended scope of the Products, creates disproportionate legal, security, or compliance risk, or is inconsistent with the applicable agreement, documentation, or supported Product functionality.

10. Data Retention

Ridewolf retains personal data for as long as reasonably necessary for the purposes described in this Privacy Policy, including to:

• provide and support the Products and Services;
• maintain Accounts and service records;
• complete transactions and manage billing;
• preserve security, diagnostic, audit, and fraud-prevention records;
• enforce contracts and resolve disputes;
• comply with legal, tax, accounting, regulatory, and recordkeeping obligations;
• maintain backup, archival, and disaster-recovery systems; and
• respond to legal holds, investigations, claims, or enforcement matters.

Retention periods may vary depending on factors such as:

• the type of data;
• the Product or Service involved;
• Account status;
• Customer instructions;
• contractual commitments;
• backup cycles;
• legal or regulatory requirements;
• tax and accounting obligations;
• dispute preservation needs; and
• security or fraud-prevention requirements.

Where Ridewolf processes personal data on behalf of a Customer, retention may also depend on the Customer’s instructions, the applicable contract, technical constraints, and applicable law.

Accordingly, deletion of personal data may not occur immediately upon request, account closure, or contract termination where retention is reasonably necessary for backup integrity, fraud prevention, dispute resolution, legal hold obligations, recordkeeping requirements, or other lawful compliance purposes.

11. International Data Transfers

Ridewolf may process, access, or store personal data in the United States and other jurisdictions where Ridewolf or its service providers operate.

As a result, personal data may be transferred to, accessed from, or stored in countries whose data protection laws may differ from those of the jurisdiction in which the data was originally collected.

Where required by applicable law, Ridewolf will implement appropriate safeguards for international data transfers, including contractual safeguards or other lawful transfer mechanisms recognized under applicable law.

Where applicable, such safeguards may include standard contractual clauses, transfer addenda, adequacy-based mechanisms, or other legally recognized transfer solutions appropriate to the nature of the transfer and the jurisdictions involved.

12. Data Security

Ridewolf maintains reasonable and appropriate technical, administrative, and organizational safeguards designed to protect personal data against unauthorized access, misuse, alteration, disclosure, destruction, or loss.

Such measures may include, as appropriate:

• access controls;
• authentication controls;
• logging and monitoring;
• role-based permissions;
• secure hosting measures;
• contractual safeguards with service providers;
• incident investigation processes; and
• measures designed to preserve service integrity and protect against fraud or abuse.

However, no method of transmission, storage, or security control is completely secure, and Ridewolf cannot guarantee absolute security. Accordingly, users and Customers should exercise appropriate care in protecting credentials, devices, access rights, integrations, and other systems connected to the Products.

Customers remain responsible for maintaining appropriate safeguards over their own systems, devices, credentials, integrations, personnel access, and operational use of the Products.

13. Incident Response and Compliance-Related Processing

Ridewolf may log, review, monitor, investigate, preserve, and use relevant information where reasonably necessary to:

• detect or prevent fraud, abuse, misuse, or unlawful conduct;
• investigate suspected compromise, unauthorized access, or security incidents;
• protect the security, availability, or integrity of the Products;
• respond to support incidents or operational failures;
• comply with legal obligations or lawful requests from authorities;
• enforce contractual restrictions or acceptable-use requirements; or
• establish, exercise, or defend legal claims.

Where legally required or reasonably necessary, Ridewolf may notify Customers, affected parties, regulators, law enforcement, service providers, payment processors, or other relevant third parties in connection with such matters.

13.1A Accidents, Injuries, Operational Harm.

To the maximum extent permitted by applicable law, Ridewolf shall have no responsibility or liability whatsoever for any accident, collision, crash, injury, death, personal injury, property damage, theft, vandalism, loss, fine, penalty, towing, immobilization, misuse of any vehicle or asset, or any other direct or indirect harm, damage, or adverse event arising out of or relating to:

(a) the use, operation, maintenance, condition, availability, roadworthiness, legality, parking, charging, access to, or possession of any vehicle, fleet, equipment, or mobility asset;

(b) the acts or omissions of Customer, any End User, driver, renter, passenger, employee, contractor, agent, or any third party; or

(c) Customer’s business operations, transportation services, rental services, fleet activities, access-control activities, or customer-facing offerings, whether or not the Products were used in connection therewith.

Customer acknowledges and agrees that Ridewolf is solely a technology provider and is not a transport carrier, rental provider, fleet operator, vehicle owner, insurer, safety guarantor, or supervisor of vehicle use or user conduct.

Customer assumes full responsibility for all risks, claims, losses, liabilities, and consequences arising from such matters.

14. Your Rights and Choices

Depending on your jurisdiction and subject to applicable law, you may have rights regarding your personal data, including the right to:

• request access to personal data;
• request correction of inaccurate personal data;
• request deletion of personal data;
• request restriction of processing;
• object to certain processing;
• withdraw consent where processing is based on consent;
• request portability of certain personal data; and
• lodge a complaint with a competent supervisory authority or privacy regulator.

If Ridewolf receives a request relating to personal data that we process solely on behalf of a Customer, Ridewolf may redirect the request to the relevant Customer or notify that Customer so that it can respond directly, as appropriate.

Ridewolf may retain limited information necessary to verify identity, document, manage, respond to, or defend the handling of a privacy request. Where permitted by applicable law, Ridewolf may require verification of identity, authority, or account relationship before acting on a request.

We may deny or limit a request where permitted by applicable law.

If you interact primarily with a Ridewolf-powered service operated by one of our Customers, and your request concerns processing carried out on that Customer’s behalf, you should direct your request in the first instance to the relevant Customer. Ridewolf may assist the Customer in responding where required by applicable law, contract, or technical capability.

15. U.S. State Privacy Disclosures

If you are a resident of a U.S. state that provides specific privacy rights, including California or another applicable state, you may have additional rights subject to applicable exceptions and limitations.

Depending on the law that applies, these rights may include the right to know, access, correct, delete, or obtain a copy of personal data, the right to opt out of certain forms of targeted advertising or profiling, and the right not to be discriminated against for exercising applicable privacy rights.

Where required by law, Ridewolf will honor applicable rights and legally recognized preference signals.

Additional state-specific disclosures, rights-request methods, or opt-out mechanisms may be provided separately where required by applicable U.S. state privacy law.

16. Marketing Communications

Where permitted by applicable law, Ridewolf may send marketing, product-update, event, or business-development communications.

You may opt out of marketing emails by using the unsubscribe link in the relevant message or by contacting us using the details below.

Even if you opt out of marketing communications, Ridewolf may still send transactional, security, billing, legal, operational, support, or service-related communications where necessary.

Marketing preferences do not affect Ridewolf’s ability to send non-marketing communications necessary for account administration, service delivery, security, support, legal compliance, or contractual performance.

16.1A Business-to-Business Communications.

Ridewolf’s marketing and business-development communications are generally directed to business representatives, potential enterprise customers, partners, resellers, and other commercial contacts, and not to general consumer audiences seeking transportation, rental, or ride services.

17. Third-Party Services and Links

The website or Products may contain links to, or integrate with, third-party services, platforms, APIs, payment processors, verification providers, mapping providers, cloud services, app stores, or other external systems not owned or controlled by Ridewolf.

Ridewolf is not responsible for the privacy, security, or data-handling practices of such third parties. We encourage you to review their privacy notices and legal terms separately.

Where the Products interoperate with third-party services or integrations selected, enabled, or used by a Customer or user, the relevant Customer or user remains responsible for reviewing and accepting the applicable third-party terms and privacy notices.

17.1A Identity and Eligibility Verification Workflows.

Where identity, license, age, eligibility, insurance, or similar verification workflows are enabled by a Customer, such workflows are generally performed at the Customer’s request and for the Customer’s operational purposes. Ridewolf’s role in such workflows is generally limited to providing the technical means to facilitate the requested workflow, unless otherwise stated in a separate written agreement.

18. Children’s Privacy

Ridewolf’s website, Products, and Services are generally intended for business and commercial use and are not directed to children.

We do not knowingly collect personal data directly from children where prohibited by applicable law. If you believe that a child has provided personal data to Ridewolf in violation of applicable law, please contact us so that appropriate steps may be taken.

19. Changes to This Privacy Policy

Ridewolf may update this Privacy Policy from time to time.

If we make material changes, we may provide notice by posting the updated version on our website, through the Products, by email, or by other appropriate means. The “Last Updated” date at the top indicates when this Privacy Policy was most recently revised.

Your continued access to or use of the relevant website, Products, or Services after the effective date of an updated Privacy Policy constitutes acknowledgment of the revised Privacy Policy to the extent permitted by law.

20. Contact Us

Privacy-related requests, data-protection inquiries, and legal notices may be submitted using the contact details listed below. Ridewolf may require reasonable verification of identity, authority, or business relationship before responding, and may redirect requests to the relevant Customer where Ridewolf acts solely on that Customer’s behalf.

If you have any questions, requests, or concerns regarding this Privacy Policy or Ridewolf’s privacy practices, please contact:

Ridewolf, Inc.
Attn: Ridewolf, Inc. Administration
2093 Philadelphia Pike 2255, Claymont, DE 19703-2424, United States
contact@ridewolf.com
+1 484-298-9791