Camellia 的隐私政策
Camellia 作者: Petr Flaks
Camellia's Privacy Policy describes how Camellia collects, uses, and shares your personal data.
Personal Data We Do Not Collect
We do not collect this data and never will:
- We do not track links you visit
- We do not track actions you perform on websites you visit
- We do not collect your bookmarks (their names and links)
- We do not know about your account data you are authenticated in your browser (your name and email address)
Personal Data Camellia Collects from You
We strive to collect only the personal data that we need to improve overall experience of our users. All data we collect is depersonalised, it means it's impossible to use the data we collect to identify you as a person. We do not share collected information with third-parties.
Sentry
Sentry is a service we use to collect information about errors, it also allows us to measure performance of the app. When you launch Camellia and perform there some actions we collect some performance metrics, and when some error happens we receive automatic error report.
What Data Camellia Maintainers Can Access From Sentry
Automatic error reports and performance metrics may contain following information about you:
- Extension version
- Event date and time
- Browser name and version
- Operating system name and version
- IP address. We use IP address only to determine amount of users affected by an error or a performance issue
- Error details. It includes an error message and a code that produced the error
Since error reports collected by Sentry may contain IP addresses we limit access to error reports in Sentry to core maintainers only and we don't share such information with third-parties.
Sentry Privacy Policy
All this data stored on Sentry's side, so they may access your information. For more details please read "Sentry Privacy Policy": https://sentry.io/privacy/
Cloudflare
Cloudflare is a content delivery network service we use to host some services that require executing code on server-side.
Currently there is only one service deployed called Unsplash Bridge (https://github.com/camellia-app/unsplash-bridge). This service picks random photos from Unsplash collections. Unsplash Bridge also uses Sentry to track errors.
What Data Camellia Maintainers Can Access From Cloudflare
We only have depersonalised chart dashboards about out users. For example, we know geographical spread of people use deployed services, but we can't know their IP addresses.
Cloudflare Privacy Policy
All this data stored on Cloudflare's side, so they may access your information. For more details please read "Cloudflare Privacy Policy": https://www.cloudflare.com/en-gb/privacypolicy/
Unsplash
Unsplash is a photo stock service with permissive license. When you launch Camellia for the first time it will be opened with random photo background loaded from Unsplash. Please read "Unsplash Collection" (https://github.com/camellia-app/camellia/wiki/Unsplash-Collection) article to know more about how we use Unsplash.
What Data Camellia Maintainers Can Access From Unsplash
We are pretty limited to available information about our users:
- How many times API was used
- How many times photos were displayed as a background
- How many times photos were downloaded. It's pretty confused concept covered in "Guideline: Triggering a Download" (https://help.unsplash.com/en/articles/2511258-guideline-triggering-a-download). To be short: when you configured Camellia to pick random photo from Unsplash collection you will receive random photo every 12 hours, and when your old photo changed with new, it's counted as a download.
We can't access slices about how some categories of users used our Unsplash integration (e.g. there are no ways to access geographic and language slices).
Unsplash Privacy Policy
All this data stored on Unsplash's side, so they may access your information. For more details please read "Unsplash Privacy Policy": https://unsplash.com/privacy