To Ford Motor Company Leadership and the FordPass / Connected Vehicle Services Teams
We are Ford owners asking Ford Motor Company to provide a free, official, and secure way for vehicle owners to authorize third-party apps to interact with Ford Connect / FordPass connected-vehicle features, including smart home platforms such as Home Assistant.

 
The Problem
Ford currently restricts third-party integrations under the explanation of “security,” while also offering paid services aimed at enterprise and corporate customers. Security is important, but a blanket ban is not the only answer, and it should not be used to justify pushing everyday owners into paid programs designed for large fleets.

Many of us bought our vehicles as individuals, homeowners, or small business operators. When someone pays tens of thousands of dollars for a vehicle, basic connected-vehicle access should not become an ongoing paywall—especially when the official Ford app can already display the same information.

 
Our Position
This must be free for vehicle owners.

If a Ford owner paid for the vehicle, that owner should be able to access the vehicle’s available connected data and features through:

1. Ford’s own app,
2. and any third-party app the owner chooses to authorize securely

If the Ford app can do it, Ford can provide a safe, official integration path that lets owners do the same through third-party software—without charging extra.

 
What We’re Asking Ford to Do
1) Provide a Free, Owner-Authorized Third-Party API

• Create an official API program for Ford Connect/FordPass that is free for vehicle owners.
• Allow owners to connect third-party apps they trust through explicit consent.
• Provide a clear “Connected Apps” screen where owners can manage access.

2) Use Modern Security Instead of Blanket Prohibitions

• Implement OAuth 2.0 (or equivalent modern authorization).
• Use short-lived tokens and secure refresh mechanisms.
• Require app registration and enforce basic security standards.
• Allow instant revocation by the owner at any time.

3) Offer Granular Permissions

• Separate read-only vehicle information from remote commands.
• Example scopes: Read: lock status, fuel/charge level, odometer, basic health/telemetry, Read: location (explicit opt-in, clearly labeled, easy revocation), Commands: lock/unlock, remote start/stop, horn/lights (separate scopes with added safeguards)

4) Add Safety and Transparency for Owners

• Rate limits and abuse prevention that makes sense.
• Whitelisting of owner approved ip addresses.
• An audit log showing when an app accessed data or issued commands.
• Alerts when a new app is connected or when sensitive permissions are granted.
• Optional step-up verification for sensitive commands.

Why This Is Reasonable

• Owners already see these features in Ford’s own app. This is not “new value” that should be paywalled — it is existing vehicle functionality.
• Blocking third-party access does not automatically create security. Secure integration is possible through proven methods: consent, scopes, auditing, rate limiting, and revocation.
• When no official path exists, owners are pushed toward unofficial workarounds, which can be less secure. An official program improves security by providing a controlled method, and shows your customer base you actually care about what matters to them.
  
  

What Success Looks Like

• Ford publicly commits to a free, owner-authorized third-party API for Ford Connect/FordPass.
• Ford publishes documentation, scope definitions, and security requirements.
• Ford adds an owner-facing “Connected Apps” management page with audit logs and revocation.
• Ford explicitly permits integrations like Home Assistant when owners consent.

Call to Action
If you own a Ford vehicle and want the freedom to securely integrate it with tools like Home Assistant without paying extra, please sign and share this petition.

When commenting, please do not post personal information (VIN, license plate, address). Share only your general use case and vehicle model/year.