Update Privacy Policy - 12.2025.tsx#14091
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hector-r-759
requested review from
BrianAtPosthog,
charlescook-ph,
fraserhopper and
joethreepwood
|
Updating our Privacy Policy does have an effect on the Data Privacy Framework. I think last time we made changes they got in touch to say the changes needed to be approved by them so we should do that in parallel. |
|
This all looks fine to me - do any of the James tweet-style messages higher up on the page need updating too? |
Fixed some typos in the prior version.
|
Is there a way to change this: Last Updated: December __, 2025 to just auto-populate with the date? Or is the best way for me to just update this and hard code a data once we know the timing? |
|
It's possible Cory or Eli could create something like that, but the surest way will be to just update it when you make edits. |
|
@hector-r-759 are you still needing a review here? |
|
@fraserhopper nope we're good here |
|
Is this good to merge @hector-r-759 @fraserhopper? It's not currently live on the site but it looks like everyone is happy with it at this time? |
|
We are still sorting things out on the notice side, but I can merge once that is done |
|
For approval: https://github.com/PostHog/company-internal/issues/2612 |
* Update privacy.tsx * Update privacy.tsx * Update Privacy Policy - 12.2025 * Update Privacy Policy - 12.2025 Fixed some typos in the prior version. * Notice going out January 19, so updated date.
* Update privacy.tsx * Update privacy.tsx * Update Privacy Policy - 12.2025 * Update Privacy Policy - 12.2025 Fixed some typos in the prior version. * Notice going out January 19, so updated date.
5 participants
Trying this again:
Relevant thread: https://posthog.slack.com/archives/C08MYQX74KH/p1763652891589359
I'm updating the privacy policy to clean things up a bit with respect to (1) making it explicit what we can use customer data for, (2) that the list of vendors included is not meant to be exhaustive, and (3) that we have explicit consent to send data to third parties for marketing purposes (this is the main motivator for this update) and provide an opt-out.
I'm open to comments on the changes - I didn't feel like we needed to reinvent the wheel here so we're not talking about a major reworking of the language in the privacy policy, but this can actually be seen as a a pretty material change in PostHog's position when it comes to what we do with customer's emails for marketing purposes.
I think the comms piece and being able to respond to customer questions justifying this change is probably going to be more important than the actual changes to the privacy policy itself.