>Sensitive user data like calendar events don’t pass through our servers.
This could be a selling feature, but it isn't clear from your privacy policy that calendar events don't go through your servers. You might want to make that clearer and upfront in your privacy policy (and possibly make that promise separate from the clause that lets you change the policy at any time, or at least commit to notifying users of changes to the privacy policy).
Also, just generally, you might consider other edits to your privacy policy for clarity. For example, there's a heading that refers to "Personal information we collect" but then "personal information" is never actually defined; instead you define something called "device information". It's unclear (to me anyway) whether device information is the same as personal information. This makes it hard to interpret the rest of the privacy policy, which refers to personal information.
This could be a selling feature, but it isn't clear from your privacy policy that calendar events don't go through your servers. You might want to make that clearer and upfront in your privacy policy (and possibly make that promise separate from the clause that lets you change the policy at any time, or at least commit to notifying users of changes to the privacy policy).
Also, just generally, you might consider other edits to your privacy policy for clarity. For example, there's a heading that refers to "Personal information we collect" but then "personal information" is never actually defined; instead you define something called "device information". It's unclear (to me anyway) whether device information is the same as personal information. This makes it hard to interpret the rest of the privacy policy, which refers to personal information.