Privacy Policy
Effective November 15, 2026.
The data controller is DenyaDev LLC, doing business as Miatafy, 102 Bergeron Way, Cary, NC 27519, United States. Privacy requests can be sent to support@miatafy.com or by post to the address above.
Miatafy does not sell personal information for money and does not rent it. It does share limited information with Google and Meta so they can measure and deliver Miatafy’s ads, as described under Google and Meta tags and cookies and Checkout and purchase events sent to Meta. Some US state privacy laws call this “selling” or “sharing” personal information for targeted advertising.
To opt out, select Decline under cookie choices or send a Global Privacy Control signal. Either one stops the Google and Meta tags and the checkout and purchase events Miatafy’s server sends to Meta.
What is collected and why
Section titled “What is collected and why”| Activity | Data | Purpose and legal basis |
|---|---|---|
| ScreenTune car setup | VIN, original vehicle market, model year, vehicle details decoded or confirmed from the VIN, firmware confirmation, vehicle authorization and its server timestamp, selected features, the order’s email, name, delivery method and order reference, and IP address | Link the paid order to the authorized vehicle, build and sign the ordered configuration for the correct vehicle, prevent abuse and disputes, and fulfill the order. The bases are performance of a contract and legitimate interests in security and reliable order handling. |
| Car setup before payment | Name, email, VIN, original vehicle market, vehicle details, firmware confirmation, selected features, delivery choice, form timestamps, intake reference, IP address, and the details completed at each form step | A visitor who chooses Set up your car first enters these details before checkout. They are saved when the visitor leaves the vehicle step and when they continue to checkout, so the paid order can use them. An unfinished setup can trigger one reminder email about an hour after the last activity, with an unsubscribe link, except for vehicles first sold in the EU, EEA, UK, or Switzerland. The bases are requested pre-contract steps, performance of a contract for setups that become orders, and legitimate interests; a person can ask for deletion at any time. |
| Payment and order | Stripe checkout/session identifiers, payment status, amount, tax, currency, billing country, email, and limited billing/contact details returned by Stripe | Take payment, send confirmation, sign the buyer in to car setup after payment, keep accounting records, prevent fraud, and handle refunds or disputes. The bases are contract performance, legal obligations, and legitimate interests. Miatafy does not receive the full card number. |
| License records | An opaque ScreenTune license ID, VIN, linked order and intake references, vehicle description, policy version, release and configuration IDs, signed-configuration identifier, entitlement dates, and transfer, reissue, or refund status | Tie the license to the ordered vehicle, sign and verify the ordered configuration, provide updates and re-downloads, process transfers and replacement-unit reissues, and maintain order evidence. The bases are contract performance, legal obligations, and legitimate interests in reliable fulfillment and fraud prevention. The signed configuration contains the opaque license ID, normalized licensed VIN, and install plan so the installer can show the customer which vehicle it is for and enforce the license offline. Names, emails, addresses, Stripe IDs, dates, and private signing keys are not embedded. |
| Support and contact | Name, email, message, product, attachments supplied later, and IP address | Reply, troubleshoot, provide support, and establish or defend claims. The bases are contract performance and legitimate interests. |
| Beta and reservation forms | Email, vehicle details, requested product, and IP address | Manage the requested reservation or invitation. The bases are requested pre-contract steps and legitimate interests. |
| Newsletter | Email address and subscription status | Send the emails requested. The basis is consent, which can be withdrawn using the unsubscribe link. |
| Security and delivery logs | IP address, request time, browser/device metadata, and requested URL in ordinary server, CDN, and email-delivery logs | Operate and secure the site, diagnose errors, and limit abuse. The basis is legitimate interests. |
When a complete 17-character VIN fails validation, has an unmapped model code, or has a checksum error in the VIN decoder or ScreenTune car setup, the browser sends the VIN, failure reason, and source tool to Miatafy. We store first and last report times and a report count to diagnose and improve VIN coverage. These diagnostic records do not include your name or email.
The standalone VIN decoder and the Check your car box on the ScreenTune page run locally in the browser; the box sends nothing. A VIN goes to the U.S. NHTSA vPIC service only when the user actively selects the official NHTSA decode; it does not pass through Miatafy’s API. ScreenTune car setup also decodes the VIN locally, then sends it to Miatafy with the rest of the car setup when the buyer submits it to build the package.
Basic cookieless analytics
Section titled “Basic cookieless analytics”Miatafy uses a self-hosted instance of Umami for first-party traffic and website funnel analytics. The tracker sends page views and selected actions to Miatafy’s analytics server:
- clicks on calls to action and buy buttons, recorded with fixed labels;
- the result class of the Check your car box (for example, compatible or not supported);
- landing-page sections reached and how long the page stayed open;
- steps reached in car setup before payment, and fixed labels for why a step was blocked;
- car setup opened and submitted, the package ready, and the package downloaded;
- the fixed reason the page shown after payment could not open car setup;
- newsletter signups and support-form submissions.
It does not set analytics cookies or store visitor identifiers in browser storage.
Analytics records include page paths, referring site origins, timestamps, browser and device information, language, approximate location, and event names and placement labels. Page titles and URL fragments are excluded. URL query strings are excluded except for standard campaign tags (utm_source, utm_medium, utm_campaign, utm_content, and utm_term) that Miatafy adds to its own posts, ads, and emails to see which ones bring visitors. Umami processes the request’s IP address and user agent to derive location and generate a hashed visitor identifier for counting visits and connecting steps in a funnel; it does not store the raw IP address in its analytics database. Ordinary server logs are separate and may contain IP addresses as described above.
Miatafy uses these records to understand which pages visitors use and where they leave a website flow, relying on its legitimate interest in measuring and operating the site. Umami records are not used for advertising or cross-site profiles. Form answers, VINs, email addresses, order IDs, and payment details are not included in analytics events. Car setup events carry no VIN. This is Miatafy’s own installation, so Umami records are not sent to Umami’s hosted service or to Google.
Strictly necessary local storage used to preserve an in-progress ScreenTune car setup or retry a requested form submission is not used for advertising.
Google and Meta tags and cookies
Section titled “Google and Meta tags and cookies”Public pages on miatafy.com also load Google Tag Manager, which runs the Google tags Miatafy configures: Google Analytics to measure visits, and Google Ads to measure which ads lead to visits and purchases. These tags set Google cookies (for example _ga and _gcl_au) and send Google the page address, referring page, browser and device information, IP address, cookie identifiers, and ad click identifiers such as gclid. Google may combine this with other data it holds, as described in how Google uses information from sites that use its services.
The same Tag Manager container loads the Meta pixel, which Miatafy uses to measure which Facebook and Instagram ads lead to visits. The pixel records page views only. It sets the _fbp cookie and, for a visitor who arrived from a Meta ad, the _fbc cookie holding that ad’s click identifier. It sends Meta the page address, referring page, browser and device information, IP address, and those cookie identifiers.
Consent. Where the browser’s time zone is in the EU, EEA, UK, or Switzerland, nothing from Google or Meta loads until the visitor selects Allow, and the basis is consent. Elsewhere the tags load by default, relying on Miatafy’s legitimate interest in measuring its site and advertising. A browser that sends a Global Privacy Control or Do Not Track signal never loads them.
Changing the choice. Change your cookie choice at any time, in any country. Decline stops the Google and Meta tags in that browser and removes their cookies set on miatafy.com. The choice is stored in the browser’s local storage, so it applies per browser.
What Google and Meta’s pixel do not receive from Miatafy. The tags do not load on account pages (/car/, /login/), in paid car setup, or on any address that carries an order, license, checkout session, or search text. Alongside page visits Google’s tags receive the same fixed event labels listed above, and after payment a purchase event with the product name and list price. They do not receive form answers, VINs, email addresses, names, order IDs, or Stripe session IDs.
To price that purchase event, a buy click stores the delivery method chosen (download or USB) in the browser tab’s session storage while the Google tags are running.
Checkout and purchase events sent to Meta
Section titled “Checkout and purchase events sent to Meta”Miatafy’s server, not the browser, tells Meta when a ScreenTune checkout starts and when an order is paid. Miatafy uses these events to measure which Meta ads lead to purchases, and so that Meta can show Miatafy’s ads to people more likely to buy.
- Checkout started. Sent when a buyer leaves for payment, from a buy button or from car setup. It carries the
_fbcand_fbpcookie values when the pixel set them, the IP address, the browser user agent, the address of the page the buyer left without its query string, and a hashed order reference. It may also carry the price shown at checkout. - Purchase. Sent after payment is confirmed. It carries the same details plus the order value and currency and the buyer’s email address as a SHA-256 hash.
Meta does not receive the buyer’s name, postal address, phone number, VIN, or the email address in readable form.
These events follow the same choices as the tags, and the choice that applies is the one in effect when the buyer leaves for payment. Neither event is sent for a browser that sends a Global Privacy Control or Do Not Track signal, for a buyer whose choice is Decline, or for a buyer whose browser time zone is in the EU, EEA, UK, or Switzerland and who has not selected Allow. In addition, a purchase with a billing country in the EU, EEA, UK, or Switzerland is not sent unless the buyer selected Allow. The bases are consent in those regions and Miatafy’s legitimate interest in measuring its advertising elsewhere.
Email measurement
Section titled “Email measurement”Promotional and product-update emails from Miatafy may include a small invisible image and tracked links served by the same self-hosted Umami instance. When an email app loads the image, Umami counts an open; when someone clicks a tracked link, Umami counts the click and then forwards to the normal Miatafy page. These records include the campaign name and email version label carried in the image or link address, the timestamp, browser and device information, and approximate location, processed the same way as website analytics. They are counted in aggregate and do not contain or link to the recipient’s email address, name, or other identity.
Miatafy uses these counts to learn whether its emails are useful, relying on its legitimate interest in measuring its own communications. Some email apps load images automatically, and others block them. To avoid open counting, turn off automatic image loading in the email app; clicking a link is always optional, and every promotional email includes an unsubscribe link.
Service providers and international processing
Section titled “Service providers and international processing”- Stripe processes checkout, payment, fraud, billing-address, and tax information, and the shipping address for a mailed USB. Its role and independent obligations are described in Stripe’s privacy policy.
- Amazon Web Services hosts the public site and database, provides CDN and security logs, and sends transactional and promotional email through SES.
- Miatafy’s hosting infrastructure runs the self-hosted Umami analytics application and its database, including email open and click counts.
- Google provides Tag Manager, Google Analytics, and Google Ads measurement for visitors whose browsers load the Google tags. Google acts as a processor for Analytics and has its own obligations for advertising, described in Google’s privacy policy.
- Meta provides ad measurement for Facebook and Instagram ads, through the pixel for visitors whose browsers load it and through the checkout and purchase events Miatafy’s server sends. Meta’s own obligations are described in Meta’s privacy policy.
Miatafy is based in the United States, so information submitted to Miatafy is processed in the United States. Providers may also process data in other countries. Where data-protection law requires transfer safeguards, Miatafy and its providers rely on the provider’s applicable contractual safeguards or another lawful transfer mechanism. Contact Miatafy to request information about the safeguard relevant to a particular transfer.
Retention
Section titled “Retention”- Ordinary support/contact messages are deleted after 3 years, unless an active dispute or legal duty requires longer retention.
- Completed order, payment, tax, license, and package evidence is normally kept for 7 years. Minimal license and package identifiers may be retained longer when needed to honor a perpetual license, re-download, transfer, or replacement-unit reissue.
- Reservation and beta records are reviewed at least annually and removed when the program closes or the request is no longer active.
- Newsletter records remain until unsubscribe, plus the minimal suppression record needed to honor that choice.
- CDN, server, security, and email-provider logs use the provider’s configured operational retention and are not kept longer than reasonably needed for security and delivery diagnostics.
- Self-hosted analytics records, including email open and click counts, remain until Miatafy deletes them; automatic expiry is not currently configured.
- Google Analytics keeps event data tied to cookie identifiers for the retention period set in Miatafy’s Analytics property, at most 14 months. Google’s cookies last up to 2 years unless cleared or declined.
- Meta’s
_fbpand_fbccookies last up to 90 days unless cleared or declined. Meta keeps the events it receives under its own retention rules. - For a checkout reported to Meta, Miatafy’s server keeps the browser details it will send with the purchase (the
_fbcand_fbpcookie values, IP address, browser user agent, and page address) against the order reference until the order is paid, and deletes them after 3 days if it is not. - VIN decoder failure records remain until Miatafy deletes them; automatic expiry is not currently configured.
Data may be kept longer when reasonably necessary for an active claim, chargeback, fraud investigation, or legal preservation duty, then deleted when that reason ends.
Rights and choices
Section titled “Rights and choices”Depending on location, a person may have rights to access, correct, delete, restrict, or object to processing; receive portable data; withdraw consent; and complain to a data-protection authority. Withdrawing consent does not undo processing that was lawful before withdrawal.
Consent to Google’s and Meta’s tags can be withdrawn with Change your cookie choice.
Send a request from the relevant email address to support@miatafy.com. Miatafy may ask for proportionate verification before disclosing or deleting order information. EEA residents may complain to the supervisory authority where they live or work, including Norway’s Datatilsynet.
Changes
Section titled “Changes”If this policy changes materially, the effective date above changes and the current version remains available at this URL.