Skip to content

Commit

Permalink
update privacy policy to make it clearer that mobile push notificatio…
Browse files Browse the repository at this point in the history
…ns will be encrypted too
  • Loading branch information
taoeffect committed Aug 3, 2024
1 parent e66886b commit 9fe6be2
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/pages/privacy-policy.astro
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ import Layout from '../layouts/DefaultLayout.astro'

<p>Group Income does not share your data with any third-party service, and therefore we have no need of such agreements.</p>
<p>As mentioned in previous sections, the data in public unencrypted chatrooms is public and should be treated with the same care and expectations of privacy that you should have with normal social media: that is, you should have zero expectation of any privacy for the content you post to public chatrooms. By default, chatrooms are non-public, and like direct messages, they are end-to-end encrypted.</p>
<p>Certain possible future features might necessarily require some of your data passing through third-party servers. For example, certain types of notifications (mobile push notifications and emails) require that data travel from our server to another before it reaches you, and in the process this data could be read by those servers. As far as we are aware, no end-to-encrypted alternatives to such services exist. If you are aware of any, <a class="is-link" href="https://github.com/okTurtles/group-income/discussions" target="_blank">please let us know</a>.</p>
<p>Certain possible future features might necessarily require some of your data passing through third-party servers. For example, while we can end-to-end encrypt some types of notifications (push notifications), other types such as email are more difficult to encrypt. We will update this privacy policy in the future as necessary to give any disclosures should we choose to implement email notifications (or other notifications) that cannot be encrypted. In all cases, such notifications will be opt-in on the part of the user.</p>

<h3>Note On Public Chatrooms</h3>

Expand Down Expand Up @@ -106,7 +106,7 @@ import Layout from '../layouts/DefaultLayout.astro'
</h2>

<p>Nobody. If we are forced by a court to share information with a government body, the data we can share with them is described above in the section "Note On Metadata".</p>
<p>Future features that cannot avoid using third-party services (e.g. email or mobile push notifications) may necessarily expose limited data to some third-party providers should users choose to enable such features. See the section above on third-party agreements for more details.</p>
<p>Future features that cannot avoid using third-party services (e.g. some types of notifications) may necessarily expose limited data to some third-party providers should users choose to enable such features. See the section above on third-party agreements for more details.</p>
<p>Please bear in mind, everyone you've authorized to read your messages (e.g. the other people in your group), clearly have access to whatever information you choose to disclose or share with them, and information shared in public chatrooms is… public (see section "Note On Public Chatrooms").</p>
<p>Group members can read the information in the group because they share a secret key. Again, this secret key is available only to group members, not us. Similarly, direct messages can only be read by sender and recipient.</p>

Expand Down

0 comments on commit 9fe6be2

Please sign in to comment.