Icon for identity which consists of a white glyph of a person on a yellow-orange background

Identity

What: Any personally-identifiable information about you.

When: This information is accessed when you contact us via email (via the ‘from’ field of the email). This information can also be accessed if you create an account tied to your email, which is not required but allows you to sync data between your devices.

Why: Our primary means of customer feedback is email and when we receive an email it will show us who it is from. Your email will also be stored if you sign up for an account. The purpose of signing up for an account is to sync data between devices or to have multiple users on the same device.

Where: Your email will be stored in Jira if you contact us. As well as Gmail. If you sign up for an account, your email will also be stored in Firebase.

How: This data is not encrypted. We won’t contact you, unless you email us first.

[↑ Top]

Icon for calendar which consists of a white glyph of a calendar on an orange background

Calendar

What: Your calendar events.

When: This information is accessed when a Planning page is showing and discarded once you go to a different page.

Why: We show events from the native Calendar app on the Planning pages.

Where: This data never leaves your device and we don’t store it. We read it from the local device, format it, then display it locally.

How: This data is not encrypted because we don’t keep a copy of it or send it outside of your local device.

[↑ Top]

Icon for location which consists of a white glyph of a location pin on an purple background

Location Data

What: Your location.

When: This information is accessed when providing weather forecasts for your current location.

Why: Location information is required to provide weather for the current location.

Where: Location information is sent to DarkSky to receive weather information. Location info is also sent to Google Places if you decide to find the weather for a location that is not the current location. This data is also stored in Firebase to reduce the frequency that the weather data needs to be requested.

How: This data is encrypted via SSL when communicating with DarkSky. This data is also encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for habit-tracking which consists of a white glyph of a line graph on blue background

Habit-Tracking Data

What: Your habit-tracking data.

When: This information is accessed locally when updating your habit tracking.

Why: This information is stored so that you can access it in future.

Where: Your habit-tracking information is stored locally as well as in Firebase.

How: This data is not encrypted locally. However, it is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for photos which consists of a white glyph of a photo frame with mountains and a sun on a magenta background

Photos

What: Your photos.

When: This information is accessed when you add a photo to the Photos component from your Photos library. We only store the photos that you add to the app. We do not upload your whole Photos library nor any albums.

Why: This information is stored so that you can view the photos you added in the future.

Where: The specific photos you add to Capsicum are stored locally within the app. We also store these photos in Firebase so that they can be synced between devices.

How: Photos are not encrypted locally. We only have access to individual photos you select and do not access your entire Photo library.

[↑ Top]

Icon for to-do list and goals which consists of a white glyph of a list with checked boxes on a teal background

To-Do List/Goals Data

What: Your To-Do list and Goal data.

When: This information is accessed locally when updating your to-do lists or goals.

Why: This information is stored so that you can access it in future.

Where: Your to-do list and goal information is stored locally as well as in Firebase.

How: This data is not encrypted locally. However, it is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for notes which consists of a white glyph of lines representing text on a sky blue background

Notes

What: Your Notes data.

When: This information is accessed locally when updating your notes.

Why: This information is stored so that you can access it in future.

Where: Your notes information is stored locally as well as in Firebase.

How: This data is not encrypted locally. However, it is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for health data which consists of a white glyph of a heart on an dark pink background

Health Data

What: Your health data.

When: This information is accessed locally when updating your steps.

Why: Your step data is stored so that you can access it in future.

Where: Your step data is stored locally, as well as in Firebase.

How: This data is stored locally in the Health app. It is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for decorative tape which consists of a white glyph of tape with a jagged edge on a midnight blue background

Decorative Tape

What: Your decorative tape.

When: This information is accessed locally when viewing decorative tape on your page.

Why: This information is stored so that you can access it in future.

Where: Your decorative preferences are stored locally, as well as in Firebase.

How: This data is not encrypted locally. However, it is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for notebook titles and preferences which consists of a white glyph of a notebook with a bookmark on a dark red background

Notebook Titles & Preferences

What: Your Notebook title and preferences data.

When: This information is accessed locally when updating or viewing your Notebook.

Why: This information is stored so that you can access it in future.

Where: Your Notebook title and preference information is stored locally as well as in Firebase.

How: This data is not encrypted locally. However, it is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for push notificagtions which consists of a white glyph of a megaphone on a red background

Push Notifications

What: Push notifications.

When: Push notifications will only be sent when you set alerts for a task and ask to be reminded about it.

Why: Push notifications will be sent because you requested to be alerted about a task.

Where: Your preferences for push notifications will be stored locally.

How: Your preferences are not encrypted locally. However, your preferences will be encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for Loose Leaf pages which consists of a white glyph of a stack of paper on a light aqua background

Loose Leaf Pages & Titles

What: Your Loose Leaf pages and titles.

When: This information is accessed locally when viewing Loose Leaf pages and titles.

Why: This information is stored so that you can access it in future.

Where: Your Loose Leaf pages and titles are stored locally, as well as in Firebase.

How: This data is not encrypted locally. However, it is encrypted when being stored in Firebase and is not readable by us.

[↑ Top]

Icon for analytics which consists of a white glyph of a bar graph on an lavender-purple background

Analytics

What: Analytics collected from the app.

When: Analytics are gathered every time the app is used.

Why: We collect analytics to help improve the experience of the app.

Where: Anonymized analytics data is stored in Firebase. It cannot be linked to you personally.

How: For more information read Google’s Privacy & Terms and Crashlytic’s Privacy Policy.

[↑ Top]