01What we collect
Dealership and staff data: name, email, phone and each person's role at the store.
Data the dealership enters to run its business: customers, vehicles, deals, credit applications, contracts and payments.
Conversations on connected channels, including WhatsApp, Instagram and Messenger, with the media sent in them.
Technical usage data: IP address, browser type and access logs, used for security and troubleshooting.
02Why we use it
To run the product: show inventory, move the pipeline, send and receive messages, issue receipts and collect installments.
To answer the dealership's own customers through the AI assistant, when the store turns that on.
To provide support, investigate errors and protect against misuse.
We do not sell personal data, and we do not use one dealership's data to train a model that serves another.
03Isolation between dealerships
Each dealership sees only its own data. The separation is enforced in the database, by row-level access policy, not only in the interface.
Our team may enter a dealership's panel for support. That access is read-only by default, expires on its own, and is logged: the store owner can see when we entered.
04Who we share with
Vendors required for the product to work: hosting and database, WhatsApp provider, Meta platforms, email delivery and the AI model provider.
Each receives only what their function requires, under contract.
Public authorities, when required by law.
05Meta platforms
When a dealership connects Instagram, Facebook or WhatsApp, we receive the messages and profile data a person sends us through those channels, in order to reply and record the conversation in the deal's history.
We follow Meta's platform policies. Data received through those channels is used to serve that conversation, and not for any other purpose.
06Google platforms
When a dealership connects its Google Business Profile, DealerDocket accesses, through Google OAuth (scope business.manage), only the data needed to run the features the dealership uses: its accounts and locations, location details (name, address, phone, hours, website), reviews and review replies, local posts, and daily performance metrics.
We use this data only to show it to the dealership inside DealerDocket, to publish review replies and local posts that a person at the dealership approved (or that the owner set to publish automatically), and to build the dealership's reports. We do not sell it, do not use it for advertising, and do not share it with other dealerships or third parties, except service providers that process it on our behalf under confidentiality.
OAuth tokens are stored encrypted, per dealership. The dealership can disconnect Google at any time in Settings; we then revoke the tokens and delete them, and stop accessing its Google data.
DealerDocket's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
07How long we keep it
While the dealership is a customer, and afterwards for the period required by tax and contractual obligations.
Technical debug logs are deleted automatically after 14 days.
08Your rights
You may request access, correction or deletion of your personal data, and withdraw consent to communications at any time.
To exercise them, write to contact@beyow.com or use the data deletion page.
09Security
Authenticated access, data encrypted in transit and at rest by our provider, and role-based permissions inside the dealership.
No system is immune. If an incident carries meaningful risk, we notify the affected dealerships.
10Minors
The product is for professional use and is not directed at anyone under 18.
11Changes
If we change this policy in a meaningful way, we notify you inside the product before it takes effect.
12Contact
DealerDocket, by Beyow · Orlando, FL · contact@beyow.com