Privacy Policy

Effective 1 September 2026 · Version 1.0

1. Who we are

Yield is made and published by Viacheslav Krivonosov, an individual developer established in Spain. For the purposes of the EU General Data Protection Regulation (GDPR), I am the data controller for the processing described here.

Contact for any privacy question or request: viacheslav.krivonosov@gmail.com. Our full trader details, including a postal address, are published with the app's listing on the App Store and Google Play, and are available on request by email.

In this policy, "Yield", "the app" or "the game" means the Yield mobile application on iOS and Android and any browser version of it; "this site" means yieldtodrive.com; and "we", "us" and "our" mean the developer named above.

2. This website sets no cookies

yieldtodrive.com is a static page. It has no analytics, no tracking pixels, no embedded video and no third-party requests of any kind — the fonts and images are served from this domain. It sets no cookies and stores nothing in your browser. That is why you are not being asked to accept anything.

Our hosting provider may keep short-lived server logs, including IP addresses, as an ordinary part of serving and securing a website.

3. What the app keeps on your device, and never sends

The following is written to your own device's app storage (or, in a browser version, to that browser's local storage). It is not transmitted to us or to anyone else, and we have no way to read it:

• Your progress — lifetime miles driven, which practice-yard rooms you have passed, which one-time instructions you have already seen, and whether sound is on.
• Your fault history — the driving mistakes recorded during your runs, so you can review them.
• Fault photos — the square snapshot shown with each fault is taken by a second in-game camera and held in memory only. It is never written to disk and never uploaded.

Deleting the app deletes all of it. There is no cloud backup and no sync.

4. What the app does send: anonymous usage analytics

Yield uses PostHog to understand how the game is played — where new players get stuck, which lessons work and which rules are broken most often. This is the only network connection the game makes. The game plays exactly the same if it fails.

4.1 Events we send

Alongside these we store four running figures against your anonymous identifier: lifetime miles, practice-yard rooms completed, whether the yard is finished, and whether sound is on.

4.2 Technical information the analytics SDK adds automatically

PostHog's SDK attaches standard technical context to each event, without us writing any code to gather it:

• app version, build number and package name, and whether the build came from TestFlight or was sideloaded;
• device manufacturer, model and type, and whether it is a simulator;
• operating system name and version, screen dimensions;
• device language and time zone;
• whether the connection is wi-fi or cellular;
• your IP address, which reaches PostHog's servers as part of any internet request and from which an approximate city and country is derived. We use it only at that coarse level.

4.3 How you are identified

On first launch the SDK generates a random identifier (a UUID) and stores it on your device. It is not derived from your device, your account or anything about you, and it is not shared with any other app. Reinstalling the app produces a new one.

There is no advertising identifier in Yield. The app does not use the iOS IDFA or Android Advertising ID, does not link to Apple's AdSupport framework, and does not ask for App Tracking Transparency permission — because it does nothing that would require it. We do not track you across other apps or websites.

4.4 The browser version

If you play Yield in a web browser, the same analytics apply, and the PostHog script additionally stores its identifier in a first-party cookie named ph_<project token>_posthog, which lasts up to 365 days, together with data in your browser's local storage. Session recording, screen replay, heatmaps, surveys, automatic click capture and automatic error capture are all switched off. We do not and cannot watch a recording of your screen.

5. The Dispute box — please do not put personal details in it

When Yield calls a fault you disagree with, you can tap Dispute and type what you saw. That text is sent to us, along with the rule, the junction, the maneuver and your speed, so that we can go and check the rule.

We read these. But because the box accepts free text, it is the one place in Yield where you could put personal information about yourself or someone else. Please do not. We do not ask for it, we do not need it, and nothing about answering you depends on it. If you send us personal details anyway, we will delete them when we notice.

6. What we never collect

• Your name, email address, postal address or phone number — there is no account and no sign-up.
• Your real location. Yield never requests location permission; the roads you drive are generated, not real places.
• Your contacts, photos, camera, microphone, calendar, health or motion data.
• Advertising identifiers, or any cross-app or cross-site tracking.
• Payment information — Yield is free and has no in-app purchases. If a purchase is ever added, it would be handled entirely by Apple or Google and we would never see your card details.

7. Why we are allowed to do this (legal basis)

Under Article 6(1)(f) GDPR we rely on our legitimate interests: understanding how a driving game is actually played is the only practical way to find out which lessons fail and which traffic rules are being graded wrongly, and getting the rules right is the entire purpose of the product. We have weighed that against your privacy by keeping the data anonymous, by collecting no identifiers that reach beyond this app, and by leaving everything personal to you on your own device.

You can object. Under Article 21 GDPR you have the right to object to processing based on legitimate interests. The remedy that works immediately and completely is to uninstall the app: that ends all further collection at once and deletes the identifier along with it. You can also write to us — but to suppress or delete events we have already received, we need the anonymous identifier they were sent under, for the reason explained in section 11.

8. Who else sees the data

PostHog, Inc., 2261 Market St. #4008, San Francisco, CA 94114, USA, acting as our processor and hosting the analytics on its US infrastructure. PostHog processes the data only on our instructions under a data processing agreement. Its own privacy policy is at posthog.com/privacy.

Apple and Google operate the stores that distribute Yield and give us aggregate statistics about downloads, crashes and reviews under their own privacy policies. That is their processing, not ours, and it happens whether or not you ever open the app.

Nobody else. We do not sell your personal information, we do not share it for cross-context behavioral advertising, and we do not give it to advertising networks or data brokers. We would only disclose data if a valid legal obligation required it.

9. Sending data outside the EEA

Analytics data is processed in the United States by PostHog. PostHog participates in the EU–US Data Privacy Framework and its UK and Swiss extensions, and our agreement with it also incorporates the European Commission's Standard Contractual Clauses as a further safeguard for that transfer.

10. How long we keep it

Analytics events are held by PostHog and age out under the retention policy of the plan we use — one year on PostHog's free plan, longer on its paid plans. We do not copy that data anywhere else, and we delete it sooner where it is no longer useful. Dispute messages are kept until the rule they concern has been reviewed and any fix shipped. Data stored on your own device lasts until you delete the app.

11. Your rights

If the GDPR applies to you, you have the right to access your data, to have it corrected or erased, to restrict or object to its processing, and to receive it in a portable form. To exercise any of them, email viacheslav.krivonosov@gmail.com.

One honest limitation, required by Article 11 GDPR: because the analytics identifier is a random number and we hold nothing that connects it to you, we usually cannot find your records from an email address alone. If you want us to locate or erase a specific record, tell us roughly when you played and on what device, and we will do what we can. The complete and immediate remedy is always available to you directly: delete the app, and every trace of you on your device and every future event goes with it.

You also have the right to complain to a supervisory authority. In Spain that is the Agencia Española de Protección de Datos (aepd.es); if you live elsewhere in the EEA you may complain to your own national authority.

12. Children

Yield is intended for people aged 13 and over. It is not directed to children under 13, and we do not knowingly collect any information from them. In Spain and some other EEA countries the age for a child to consent to online services is higher — 14 in Spain — and where a higher age applies locally, it applies. If you believe a child under 13 has used the app and sent us data, email us and we will delete it.

13. California residents

We do not sell or share personal information as those terms are defined by the California Consumer Privacy Act, and we have never done so. California residents may exercise their rights to know, delete and correct by writing to the address in section 11; the same practical limitation described there applies. We do not use your data for cross-context behavioral advertising or profiling with legal effects, and we do not discriminate against anyone who exercises a privacy right.

14. Changes to this policy

If what Yield collects changes — for example if advertising or purchases are ever added — this policy will be updated before that version ships, with a new effective date at the top, and the store listing's privacy declarations will be updated to match. Material changes will be noted on this page.

15. Contact

Viacheslav Krivonosov · viacheslav.krivonosov@gmail.com
A real person reads this address, and privacy requests are answered within 30 days.