Table Planner
Privacy Policy
Contents
Information you share with us 3
How You Control the Information You Share with Us? 5
Additional information we receive about you 6
When you use Table Planner, we receive some personal information from you like the type of device you’re using and your IP address. You can choose to share additional information, for example to help us monitor the performance of your installed app or to allow our service to send you push notifications from time to time.
We give you control through your settings to limit the data we collect from you and how we use it. You can also always download the personal information related to you on Table Planner.
Table Planner uses Google’s Firebase services as the underlying infrastructure. We will explain what this means to you and how Google’s privacy policy applies to your data.
If you have questions about this policy, how we collect or process your personal data, or anything else related to our privacy practices, you can email us at hello@tableplanner.app.
We require certain information to provide our services to you. For example, you must have an account in order to use our service. When you choose to share the information below with us, we collect and use it to operate our services
You will have to create an account to use the Table Planner service. If you choose to create an account, you must provide us with some personal data so that we can provide our services to you.
The personal data needed for your account are:
This data is not shared publicly but we use it to display to those Table Planner users who you have invited to connect to you or those who’s invitation to connect you have accepted. They will see this information as part of the initial invitation as well as in screens that display the status of yours and their walking activity.
When creating a Table Planner account you can use an identity from Google, Facebook or Twitter. Table Planner will not have access to any of your login credentials (e.g. username or password) from these login services and will only have access to a token. A token is an identifier created by the login provider for Table Planner to use for the purpose of identifying you on their systems.
We also ask for additional information from these login services. See below.
If you choose to create login credentials specifically for Table Planner we store the following information you give us:
We use the email address provided solely for the purposes of login. It is not shared or used for any email communications by Table Planner or any other party.
The password you give us is stored using a encryption algorithm that means individuals with access to the Table Planner database cannot see or guess the characters that comprise your password.
The information you provide Table Planner is not available publicly. Only individuals with a Table Planner account who you explicitly connect with using the Table Planner service can see this information.
Your basic account information and information from your device’s health services are fundamental to providing our services. You can remove access to these by closing your account and requesting all personal data is erased. You can delete your account in the app in privacy setting screen. Or you can email us at hello@tableplanner.app.
We use of Google Analytics for Firebase to understand the usage of Table Planner in order to improve our product for users.
A list of data captured by default by Google Analytics for Firebase can be found here.
In addition, we capture data about the following events that occur during your usage of the Table Planner app.
Event | Data Captured | Purpose |
onboarding_tutorial | Anonymised analytics data | Improve app usability |
onboarding_join_start | Anonymised analytics data | Improve app usability |
onboarding_signup_start | Anonymised analytics data | Improve app usability |
onboarding_signup_complete | Anonymised analytics data | Improve app usability |
onboarding_signup_failedtutorial_coachmark_action | Anonymised analytics data | Improve app usability |
tutorial_sidebar _action | Anonymised analytics data | Improve app usability |
event_add | Anonymised analytics data | Improve app usability |
event_delete | Anonymised analytics data | Improve app usability |
event_rename | Anonymised analytics data | Improve app usability |
event_invite_create | Anonymised analytics data | Improve app usability |
event_invite_accept | Anonymised analytics data | Improve app usability |
event_export | Anonymised analytics data | Improve app usability |
event_collaborator_delete | Anonymised analytics data | Improve app usability |
tables_add | Anonymised analytics data | Improve app usability |
tables_delete | Anonymised analytics data | Improve app usability |
table_name_edit | Anonymised analytics data Anonymised analytics data | Improve app usability Improve app usability |
table_repositioned | Anonymised analytics data | Improve app usability |
single_guest_added | Anonymised analytics data | Improve app usability |
guests_imported | Anonymised analytics data | Improve app usability |
guests_deleted | Anonymised analytics data | Improve app usability |
guest_edited | Anonymised analytics data | Improve app usability |
tag_added | Anonymised analytics data | Improve app usability |
tag_deleted | ||
tag_assigned | ||
tag_activated |
When technical errors occur in the Table Planner app, we use the Firebase Crashlytics service to store data about the error. This is also known as ‘crash reporting’.
The data stored includes details of the technical error (known as a ‘stack trace’) along with device information.
This allows us to analyse the cause of the technical error and update the Table Planner source code with technical fixes, sometimes specific to the make and software version of a device.
Firebase is a suite of tools and services for mobile app developers. Provided by Google, the Firebase services provides Table Planner with functionality like analytics, databases, messaging and crash reporting.
Table Planner uses the following Firebase tools and services.
Firebase Service | What we use it for |
Firebase Firestore Database | Storing Event data for the Table Planner service. |
Google Analytics for Firebase | Understanding use of the Table Planner app to improve and extend product features. |
Crashlytics Reporting | Understanding of technical errors that happen in the Table Planner apps. |
Performance Monitoring | Understanding with the Table Planner app software is operating at speed. |
Cloud Functions for Firebase | Code that runs inside the Firebase platform for handling workflows such as Table Planner Event invites & collaboration. |
Firebase Hosting | Hosting for the Table Planner product website. |
Firebase Authentication | Integration with login services from Google, Facebook and Twitter. Maps a user’s identify from external services to a Firebase identifier. |
Firebase Predictions | Predicts user behaviour based on analytics data from Google Analytics for Firebase |
Table Planner uses the default Firebase configuration which shared data gathered by Google Analytics for Firebase with the Firebase services. This is done to improve how these service work.
Details of how the different Firebase service use shared data from Google Analytics for Firebase is found here: https://support.google.com/firebase/answer/6383877
The following Firebase Services used by Table Planner stores data in an encrypted format. This means that the data cannot be read without knowing the necessary decryption keys and process.
Table Planner uses Facebook Login to allow users to login to a Table Planner account via Facebook. Public profile, including email is needed for login. Email is not used for any other purpose. Friends list is used to find friends who also use Table Planner to make it easier to add friends.
Basic Google Profile for login purposes
Basic twitter profile for login purposes