element-hq / policies Goto Github PK

From email to Modular Support:

Please see Section 2.8 and find the following text "or by yourself. In future we may." I believe that there should be the word "the" between the words "In" and "future."

"Elementy" on this page: https://element.io/privacy#:~:text=What%20happens%20if-,Elementy,-is%20sold%3F

I was wondering if there was any thoughts on making a child-parent account concept like Facebook's https://messengerkids.com/

In any case the smaller issue I'm reporting is that in targeting educational instituions my quick read is that you need to update your terms and conditions, namely the 16 year age limit.

matrix-org/matrix.org#166

From email to Modular support:

tonight I set aside some time to read your ToS after having met you at
FOSDEM earlier this year. I believe I found a typo in 5.1.1 of your ToS:

For example, on a 50-users server, if there are 10 Reserved Users, the
40 other users will be able to use the Service, but the 41^st
one will be locked out. Meanwhile any Reserved User will be able to
continue using the service, even if they haven't been active in the
last 30 days.

My assumption is, that the 41st should be put at the top. In case you
are escaping the output, maybe that's not worth it?

Currently, when npm run build crashes when markdown-it is not on the $PATH. We should fix that by adding markdown-it as a dependency and modify the npm run build script to use the locally installed markdown-it.

Matomo is no longer being used for analytics, it has moved to Posthog,

We need to confirm what data is being collected for web, android and IoS.

1. What data we collect without an opt-in. - eg user agent etc.
2. What we collect once a user opts in. - eg element call analytics.
3. What tools we are using for opt-in analytics. - PostHog.
4. How long do we retain opt-on analytics for.

Linked issue: https://github.com/vector-im/legal-compliance/issues/261

Riot no longer uses piwik.js (instead uses its own Piwik sending code) and now stores things as parts of its own application data in localStorage.

Describe the bug
A clear and concise description of what the bug is.

Section 1.1 and 2.6 have dead links on the website, but the correct links are in the file in this repository.

Jitsi is not mentioned anywhere

https://element.io/integration-manager-privacy-notice

• List out all third-parties, inc. types and categories of data shared

• Review and update policy in line with other documents

Its a 4h lifespan cookie to track if you opted to use the app on a mobile device instead of following the links to your respective app store

https://blog.cloudflare.com/deprecating-cfduid-cookie/