Who is responsible
This policy applies to the Timary iPhone and iPad app and this information website. The developer of Timary is responsible for the app's data practices. Contact the developer at anton.andreev.general@gmail.com for privacy questions or requests.
Timary does not require a separate Timary account. You decide what client and appointment information to enter. If you use Timary for your work, you are responsible for having an appropriate basis to store and share your clients' information.
Client and appointment information
Timary stores the information you enter: client names, phone numbers, social contact handles and notes; services, prices and durations; appointments, visit history, payments recorded by you and tips; working hours, days off, preferences and message templates. Payment amounts are bookkeeping entries, not payment-card details.
These records are stored on your device and used to provide scheduling, client management, reminders, statistics and data transfer. We do not operate a separate server that receives your client database. We do not sell client information or use the contents of your records for advertising.
Timary's defined analytics events do not include client names, phone numbers, message or note text, appointment details, prices, service names or client identifiers. Analytics and crash reporting are described separately below.
Optional iCloud sync
iCloud sync is off until you enable it. When enabled, Timary uses Apple's CloudKit private database associated with your Apple Account to sync records and supported settings across your devices. This includes clients, services, appointments, days off, preferences and message templates. System contact links and device permissions stay on the device.
Apple processes the synced data under its service terms and privacy policy. The developer does not have a support interface for browsing your private iCloud records. Turning sync off does not delete data already stored in iCloud. Changes to the sync setting take effect after you fully close and reopen Timary.
Contacts, photos and notifications
If you choose a person through Apple's contact picker, Timary imports the name and selected phone number you choose and keeps a local link to that contact. Timary does not upload your address book to a developer-operated server.
If you choose to save an image of your available hours, Timary requests permission to add it to Photos. This feature does not require access to read your photo library.
Appointment reminders are local notifications for you. You can change notification permissions in your device settings. Reminders are not automatic messages to your clients; their contents may appear on the lock screen according to your notification settings.
Optional Apple Calendar connection
If you enable Apple Calendar sync, Timary requests full calendar access to find, create, update and delete its events. Client names, service names, visit times, statuses and links to appointments are sent to the calendar you choose. Phone numbers, social contacts, notes and financial fields are not sent. The calendar account provider processes the exported information under its own terms; iCloud calendars can make it available on your other devices.
Sync is one-way from Timary and is configured locally on one device. Turning it off keeps existing calendar events. The separate cleanup action shows the events for review before deleting them; it leaves the calendar and other events intact. Calendar permissions can be revoked in device settings.
Usage analytics and crash reports
Timary uses Google Analytics for Firebase and Firebase Crashlytics to measure app usage and stability. Collection is enabled by default. Defined analytics events exclude client names, contact details and appointment contents. The app does not collect IDFA or use cross-app advertising tracking. Data practices are disclosed in the privacy policy.
These services can process app-instance or installation identifiers, device and operating-system information, app versions, event times, usage events and crash traces. Crash reports may include technical application state and recent action breadcrumbs. Google Analytics can derive approximate geography from network information. The app uses FirebaseAnalyticsCore without IDFA collection and does not display third-party ads.
This data is processed by Google/Firebase; it is separate from your locally stored client database. Contact us about data questions, objections or deletion requests. A request does not automatically stop collection on your device or delete data already received by Google. Where data is associated only with a generated installation identifier, we may need additional information to identify it, and we may not be able to link it to your email address.
How long information is kept
Client and appointment records remain in your app storage until you edit or delete them, app cleanup rules apply, or the app's local data is removed. Removing a client profile does not necessarily remove the historical information saved in appointments; review and delete those records separately if needed.
Synced data remains in your private iCloud storage until deleted through the app or Apple's available storage controls. Exported files and device backups remain under your control and the relevant storage provider's retention rules. Uninstalling Timary or turning sync off does not by itself remove those copies.
Event-level analytics retention follows the retention setting for the Google Analytics property; aggregate reports can have different retention rules. Contact us for the current setting or a deletion request. Firebase states that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from live and backup systems.
If you email support, we use your address, message and any attachments to handle your request. We keep that correspondence while it is needed to resolve and follow up on the issue, or to meet applicable obligations. You can ask us to delete it.
Your choices and requests
You can edit or delete records in Timary, export your data, leave iCloud sync off, and manage notification and photo permissions in device settings. A deletion made while iCloud sync is active can propagate to your other connected devices.
To ask about access, correction, deletion, restriction or objection to processing, or to withdraw consent you have given, email anton.andreev.general@gmail.com. Your rights depend on applicable law. We may need to verify a request and identify the relevant data. Withdrawing consent does not affect prior lawful processing.
The developer cannot remotely retrieve or erase data held only on your device or in your private iCloud database. We can guide you through the controls available to you. To remove all copies, also consider synced devices, exported files and backups. Please do not email your client database or other people's personal information unless it is necessary and we have agreed a suitable way to share it.
Service providers and security
Apple provides iCloud and system services; Google/Firebase provides analytics and crash reporting. Messages and files go to external services only when you choose the relevant action. Providers may process information in countries other than yours under their applicable privacy and data-protection terms. We do not promise that information is stored in a specific country.
Read Apple’s privacy policy, Firebase’s privacy and security information, and Google’s privacy policy for provider details. We use these services under their applicable data-protection terms and expect providers processing data on our behalf to protect it accordingly.
We rely on device security and the protections of the selected service providers. No storage or transmission method is completely secure. Protect your device and Apple Account, and take particular care with exported files.
This website
This static website is hosted on GitHub Pages. We do not add analytics scripts, advertising, forms or cookies to this site. GitHub records visitors’ IP addresses for security purposes. See the GitHub privacy statement. If you email us, your email provider also processes that communication.
Children
Timary is intended for people managing professional appointments and is not designed specifically for children. We do not knowingly request personal information directly from children. Contact us if you believe a child has sent personal information to the developer.
Changes to this policy
We will update this page when the app's data practices change and revise the date at the top. Where required, we will provide an additional notice or seek consent before a relevant change takes effect.