Contacts Journal CRM is a contacts relationship management system with privacy built-in. With no account signup required, your data is always under your own control!
By default, all data in Contacts Journal is stored in a database that lives on the device itself. This includes all the contacts that you create or import from the Contacts app, all your Logs, ToDos, Files, User Fields etc. We the developers don’t have any access to this data.
You have the option to enable CloudSync to sync your data between multiple devices running the Contacts Journal app. CloudSync uses your own iCloud account to save your data to iCloud servers, and transfers the data between devices automatically using iCloud. We the developers again don’t have any access to any of the data.
You can delete all your data saved onto iCloud using CloudSync by following instructions in this link.
You also have the option to enable Dropbox sync, which also allows you to sync your data between devices, though it requires a couple of manual steps each time to “Save” and “Fetch” data from Dropbox. Even in this case, we the developers don’t have any access to the data. However, Dropbox’s engineers may or may not have access to this data.
You can delete all your data saved onto Dropbox by going to the Dropbox website, and then deleting the folder called “ContactsJournal”.
We collect anonymous data to track app usage using an analytics library. This helps us track things like page views within the app, which feature is used more than others, what option is used to import files, etc. None of this contains any data that is input by you, and it contains no personally identifiable information or identifiers to track your visit across sessions or devices.
We also use an anonymous and randomized identifier to keep track of your iCloud account, against which we can track how many devices you have used with Contacts Journal, which devices were last active, what operation system version is running on that device, which version of Contacts Journal, which sync setting (if any) is enabled etc. None of the data is personally identifiable. We can provide a copy of this at your request, by using the randomized identifier that only you can access through the Contacts Journal app.
We also collect anonymous crash reports, in case the app crashes for any reason, to help us diagnose and fix any issues. The crash report can contain information like which device model is used, and some metadata about what the app was doing when it crashed. The crash reports don’t contain any data that is input by you, and it contains no personally identifiable information or identifiers to track your visit across sessions or devices.
On the Contacts Journal version for the Mac, the crash reporter has the option for you to include your email address as part of the crash report, and this is stored, along with the crash report, on the service (HockeyApp) we use for collecting and analyzing crash reports. We can provide a copy of all your crash reports if you have provided an email address along with the crash reports.
We also have an option to send diagnostic activity logs to us, in case you are running into any problems, when you use the “Report a Problem” option. The activity logs contain information about the internal operation of the app while it’s running on your device, and can help us identify any issues or bugs that come up. The activity logs do not contain any personally identifiable information, and are only stored on the device you are using and never transmitted to us or anyone else, other than a small snippet of the logs that is added to the crash report in case the app crashes for some reason. You can access the contents of the activity logs by using the “Report a Problem” option and emailing the file to yourself, which you can open with any text editor.
Contacts Journal Teams
If you use Contacts Journal for Teams, we store some additional information used for managing the subscriptions and team metadata. The data we keep track of contains:
- Subscriptions: plan expiration date, plan type, plan start date, unique plan identifier, whether the subscription is active or expired etc
- Subscription payments: transaction identifier, payment plan identifier, etc
- Team data: created date, team name, count of participants, number of participants who have accepted or rejected the shared link, etc
We still do not have any access to any of the actual shared data, nor any information about the iCloud accounts of the team owner or participant. That data is saved on the iCloud account of the user who created the Team, and shared directly with the iCloud accounts listed as the participants of the Team, without going through any of our ‘servers’. The information about team owner and participants is also embedded in the link that is created when the team is created, and can be updated by the team creator.
If you have any questions about any of this, please contact us at firstname.lastname@example.org