Boomkop3 Thanks for the response, I'm glad to hear that you didn't take my comments as an attack. I do want this to work, but was quite confused hearing Vlad shrug-off the questions.
The trick is to ensure European users that you do not store or trade their information, in a codified and structured way. Or if you do, then being ceratin about where it goes. A sentence such as "We value your privacy, and whenever possible we will choose not to require or save any user data." is not sufficient in the privacy policy.
I can share Cursor's approach, since it is publicly available and covers both their b2b and b2c customers. Are their answers "good" in terms of data sharing? Not really, they collect a buttload of info. I believe Kagi collects a lot less. And they are overly verbose. However, the important part is that they have ready answers and clear breakdowns, showing that they took the issue seriously. They made it easy to consume and decide what level of risk we are willing to take.
It is all about the presentation and UX. Kagi can be even better at this. Looking at your Privacy page you could totally do the same with just a bit of rewording and some additional pieces of info. In the case of asking for DPA, they direct you to 3 pages:
- https://trust.cursor.com - where you can see their SOC2 self-assesment, which answers some of the questions about data storage and subprocessor list that makes it easy to trace back the jurisdiction of different vendors that get access to your data, it also shows a lineage of their controls, answers about infrastructure in China and Russia, lays out encryption practices.
- https://www.cursor.com/security - details data residence choices, stability assurances, deletion practices with examples, known limitations
- https://www.cursor.com/privacy - similar to yours, a general-purpose breakdown, goes into detail about their no-store no-train policy, declares data sharing practices, reminds the user about their choices, declares jurisdiction exceptions, defines cases when PII is transferred outside EEA and ensures that an "adequate level of data protection" is used when transferring PII outside EEA.
- https://www.cursor.com/terms-of-service - classic legal word wall, lays out the details regarding judicial arbitrage, fair use, and auditing requests (this last one is a big subject in DPAs).
Again, they are being too verbose, you can do all of this in a much smaller format. As long as you have answers (good or bad) that is a green flag.
Keep in mind - my comment isn't about what is legally required of you. This is an often misunderstood part of Europeans asking about EU data residency. It is about what assurances do you willingly give. Its about your vibe. Can you make me feel I'm in safe hands. If you can do that by displaying sanity, conciousness and good architecture practices, then you're golden. You just need to communicate it properly.
--
All these combined (especially 1&2) basically answer all the questions that DPA would answer and can replace a DPA easily.
Basically there are not that many question permutations - over time they gathered all the questions coming from EU, and codified easy answers into their pages. So, when you reach out asking for a DPA or legal entity residency, they have canned responses on their public pages already.
Common questions are:
- What PII is being gathered and when.
- What circumstances is PII shared with subprocessors and which ones.
- What circumstances is PII sent outside of EEA and what protections does it fall under. (basically, "how likely is it that JD Vance can read my name and search history" 😃 )
- What pieces of PII (or intellectual property) fall outside of EEA jurisdiction.
- Proving (through architecture practices, encryption etc) that a breach will not compromise Europeans PII to the best of your ability.
- Proving (through architecture practices) the intended stability of the system if some usage paths are critical (to describe it better, with Cursor its basically "if a war starts tomorrow, will i still have access to my code", im not kidding with the war part).
- General Location (jurisdiction, continent or country) of teams that get access to PII or critical systems. (hard to explain - usually asked for if the customer falls under one of the laws about critical infrastructure, where everyone that touches critical parts must be "within a NATO-aligned country")
- Explicit assurance that PII is not used for training LLMs, options for opting out, listing LLM providers in question.
- Same, but about intellectual property (queries, code, translation text, history, preferences etc)
- Bonus points if you explain your general ownership structure or unionization practices thats a big win.