Hexis · Updated 10 October 2026
Features depend on the version of Hexis installed on your device. The Groups and Reporting sections apply only if your app offers a Groups tab. Without that feature, Hexis does not create or join shared groups. Other sections describe features where available. How earlier TestFlight builds handled Groups is described in the earlier policy and in Groups in earlier builds below. The app was previously called Tally.
Hexis is a private habit journal developed by Martin Elenjikkal. There is no Hexis account or developer-operated journal server. The app includes one third-party SDK, RevenueCat, which handles purchase checks (see Purchases); no advertising, tracking or remote analytics SDK is included. The app does not automatically send your journal to the developer. Information can move through optional private iCloud sync, your paired Apple Watch, exports and sharing you initiate, and emails you choose to send.
Habit names, icons, targets, amounts, cadence, reminders, daily marks, streaks, routines, settings, signatures and commitments are stored on your devices. Optional iCloud sync is off by default. It mirrors habits, signatures, earned-mend balance and change/deletion records to your private iCloud using Apple's key-value store. Routines are not included. Turning sync off stops further mirroring; the developer cannot read or restore your private iCloud data.
Removing the app does not erase existing iCloud data or exported backups. Manage iCloud storage through your Apple Account settings, and contact Apple Support if you need help with retained Apple-hosted data. Keep a backup before deleting storage you may need.
The paired Watch receives a habit snapshot over Apple's device-to-device connection and sends habit marks back. The current snapshot includes signature data and other habit fields that the Watch does not display. Routines are not sent to the Watch. Widgets and complications use on-device journal storage; marks made on these surfaces can subsequently sync to your own devices.
Habit and routine reminders are local notifications, as are the optional gentle “come back” and weekly-page nudges, and, when you start the free trial from Hexis with notifications allowed, a single reminder two days before the trial ends. Each is scheduled and delivered on your device; none is sent from a server. Routine Live Activities are driven by local state. The app registers for remote notifications so Apple can tell it silently that a group has changed; see Groups. No developer push server is used, and no notification carries journal content.
Keeping a task on Apple Calendar is optional and off until you turn it on for a task. The first time you do, iOS asks you to give Hexis access to your calendars. Hexis asks for full access because write-only access cannot move or remove the events an app has saved, so an edited or deleted task would leave its old event behind. Hexis creates its own calendar named “hexis” and writes only the tasks you choose into it. It reads back only the events it saved, to update or remove them, and does not read your other calendars or events. Nothing moves from your calendar into Hexis.
The “hexis” calendar is stored by Apple Calendar in the account that holds it, such as iCloud, and syncs the way your other calendars do; the developer does not receive it. Turning the calendar off for a task removes that task's upcoming events. You can withdraw access at any time in Settings › Privacy & Security › Calendars.
Exported backups contain habits, daily marks, amounts, routines, mend balance, signatures and commitments. Protect these files. Sending a backup or screenshot to someone gives that recipient its contents. Progress cards are generated locally and handed to the app or destination you choose, whose privacy rules then apply. If you choose Save Image on the share sheet, iOS asks once for permission to add to your photo library; Hexis uses it only to save that card and cannot see or read your other photos. There is no in-app social feed, public profile or discoverable content; the one way journal information reaches another person inside Hexis is a group you create or accept an invitation to, described next.
Groups is optional and inactive unless you create or accept an invitation to one. Each participant needs a Hexis+ entitlement and an iCloud account; an eligible earlier purchase can provide the entitlement without a current subscription. A group is hosted in its creator's own private iCloud, as a shared record zone. There is no developer-operated group server, and the developer cannot read, change or delete what is in a group — a creator's private iCloud database is not reachable by us.
Invitations are private. Invitations are issued to specific people through Apple's own sharing controls. Public link access is not enabled, so holding a forwarded invitation does not by itself allow an uninvited Apple Account to join.
What the other members of a group can see. The group's name; the name, icon and weekly cadence of the single habit the group is built around; and, for each member, the display name they joined under, a colour index, their time zone, when they joined, when they last published, and their marks for that one habit — completed days, intentional rest days, days covered by a mend, and dated edit receipts retained for about 90 days. Nothing else from your journal is put into a group: your other habits, routines, amount targets, reminders, signatures, commitments and history stay out of it. Your own copy of the habit may be named differently in your private journal from the name the group displays.
On your device. A copy of the group is cached on your device so its page works offline, and Apple's silent notifications tell the app when something has changed. Which of your habits is connected to which group is recorded only on your device and is never shared.
Names are checked on your device before they are published. A group's name, the name you show up under, and the name of the habit a group is built around are compared against a list held inside the app, and refused if they match. This check runs entirely on your device and transmits nothing.
Leaving, removing, ending and blocking do different things.
Each member's row offers Report. Filling it in writes the report on your device and prepares an email to the developer; you send it. Nothing is uploaded automatically, there is no Hexis server involved, and the app does not put a report in the group or notify the person reported.
Who can read a report. Whoever you email it to — the developer — and nobody else. It does not pass through any other service on the way. In builds before this one the app uploaded reports to a record in its own public iCloud database, which required a permission that would also have let other signed-in users read them; no report from any user was ever stored under that arrangement. That upload has been removed entirely.
A report contains a reference code, the reason you selected, any note you write, the reported member's display name and their group member identifier, the group's name and identifier, your own group member identifier when available, the app version, and the time. It contains no habit marks or other journal fields unless you type them into the note.
The app saves the report on your device first, so it cannot be lost while you get to the email; up to twenty wait there, and you dismiss each one once you have sent it. If it cannot be saved, the app says so and offers the draft anyway — that draft is the only thing that delivers it. Sending the email discloses your email address to us, as any email does. Reports you send are held in the developer's email account for as long as needed for safety and support, not advertising. Quote the report's reference code to request access or deletion; information needed for an unresolved safety or legal matter may need to be retained. Blocking takes effect on your device whether or not you send the email.
Changes to the app do not automatically delete shared iCloud records created by an earlier version, revoke invitations already accepted, or alter copies of the app already installed on other people's devices.
Groups in earlier TestFlight builds could be shared by a public invitation link, which allowed anyone holding the link to join. Those older shares are not converted merely by installing a later version. If you created a group in a TestFlight build, open it and use Apple's Manage Access screen to check who has access and how it is shared, and end the group if you no longer want it. The same categories of information listed above were shared in those builds; the earlier policy describes them.
The developer cannot erase another person's private iCloud zone, and will not claim information has been deleted without confirming it. Contact us, or Apple Support, for help with data held in iCloud.
Apple processes purchases, trials, subscriptions and refunds through your App Store account. Hexis uses StoreKit to load products and verify entitlements, and uses RevenueCat (RevenueCat, Inc., United States) to confirm whether this device has Hexis+. Purchases and restores communicate with Apple; valid local entitlement records can support offline access. The app does not send journal contents with purchase checks, and the developer does not receive card details. Removing a feature or uninstalling the app does not cancel a subscription; manage it in your Apple Account subscription settings.
To answer that question, RevenueCat is sent the App Store receipt and purchase history for this app (which plan, when it was bought, whether it is in a trial, when it renews or lapsed), together with the device's platform, operating system, app version, language and country, and the IP address the request arrives on, which it uses to place the purchase in a country and not to locate you. It is not given your name, email address, Apple Account or advertising identifier. Hexis has no accounts, so it asks RevenueCat to issue a random anonymous identifier, and Hexis does not use RevenueCat for advertising attribution or marketing tracking. No journal contents are passed to RevenueCat. RevenueCat handles this on the developer's behalf under its own privacy policy.
If RevenueCat cannot be reached, Hexis also checks Apple's records on the device and accepts either answer, so a purchase you have already made is not lost.
A small first-run event log is stored on your device, not transmitted. It records events such as onboarding and paywall presentation, with timestamps; the answers you give to the onboarding questions about how habits have gone for you before; and, for a starter habit you pick from Hexis’s own list, that list name (a habit you name yourself is recorded only as “custom”). It holds no habit name you typed and no daily marks. It is not connected to a remote analytics service.
When Hexis first opens, it uses Apple's AdServices framework to learn whether it was installed after a tap on an Apple Ads advertisement. iOS creates a token for this that describes the ad interaction, not you. Hexis sends the token to Apple's attribution service, which replies either that the install did not come from an ad, or with the identifiers of the campaign, ad group and keyword. If Apple's service has not yet recorded the install, Hexis tries again on a later launch until it gets an answer.
The answer is kept with the local diagnostics log on your device and is not sent to the developer or anyone else. It is not used to track you across other apps or websites, which is why Hexis does not ask for tracking permission.
Support and suggestion controls prepare emails for you to review and send from your own mail app. Opening or discarding a draft does not send it. We receive your email address, displayed sender name, message and any attachments you include. In-app messages may include the app version; suggestions also include their selected category and preparation time. They do not automatically attach your journal.
Reports about a group member are described under Reporting someone in a group. We use correspondence for support, resolving reported problems and safety, not advertising or marketing. It is held in the developer's email account for as long as needed for those purposes. Contact us to request access or deletion; limited records may need to be retained for legal or unresolved safety obligations.
The developer holds almost nothing about you: there is no Hexis account, and your journal stays on your devices and in your own iCloud. What the developer can hold is the email you send to support or in a report (see above) and, through RevenueCat, an anonymous purchase record with no name or email. Depending on where you live (for example under the GDPR in the EU and UK, the CCPA in California, or the Australian Privacy Act) you may have the right to ask what is held about you, to have it corrected or deleted, and to complain to your local regulator. Contact us at the address below and we will respond; we cannot look up or remove data we do not hold, such as your private iCloud or another person’s group. To have the anonymous purchase record deleted, tell us roughly when you first opened Hexis and we will ask RevenueCat to remove it; Apple keeps its own purchase records, which only Apple can erase. Hexis does not sell personal information, does not share it for advertising, and does not track you across other companies’ apps or websites. RevenueCat is based in the United States, so a purchase check sends that record there.
Hexis is not directed at children and does not knowingly solicit their personal information. If a child sends personal information to support, a parent or guardian can contact us to request deletion. A group is the one part of Hexis where something a person types is shown to other people; it can only be entered by accepting an invitation from someone who already has it, and a parent or guardian who wants a child removed from one should use Leave in the app, ask the group's creator to remove their access, and may contact us for help.
The 10 October 2026 revision describes saving a share card to your photo library. The 7 October 2026 revision adds the reminders Hexis schedules about coming back and about the end of a free trial, corrects the description of what the local diagnostics log records, and adds Your rights and retention. The 1 October 2026 revision names RevenueCat as a purchase-verification service, replacing the statement that no third-party SDK handles purchases, and describes what it receives. The 27 September 2026 revision adds Apple Calendar and install attribution, both introduced in Hexis 1.4. The previous revision distinguishes features by installed version, describes the invitation-only form of new Groups and the separate reporting route, and does not claim that information shared by earlier TestFlight builds has disappeared. It also records that reports are no longer uploaded by the app at all: they are written on your device and emailed by you. Future material changes will be reflected here.
Martin Elenjikkal · martyelenjikkal@gmail.com