TJB Ventures FZE, a company registered in Ajman Free Zone, United Arab Emirates (“Orla”, “we”, “us”), publishes the Orla app. This policy explains what happens to your information.
Orla runs no server that holds your health information. There is no Orla account, no login, and no database of ours containing what you log.
1. What you log in Orla
Symptoms, severity, cycle dates, hormone therapy (type, dose, route, start and stop dates), supplements, and any notes or questions you write.
Where it is stored. On your device, in the app’s own encrypted storage, protected by iOS Data Protection and your device passcode or biometric lock.
Who can see it. You. We cannot. It is not sent to any server we operate, because we do not operate one.
iCloud sync. This version of Orla does not offer iCloud sync. The app never sends your records to iCloud and never copies them to another device; they exist only in the app’s storage described above. If a future version adds an optional sync feature, it will be off unless you turn it on, and this policy will be updated before it appears.
2. The questions asked before you subscribe
During onboarding, before any payment or consent screen, Orla may ask a short set of questions about symptoms you experience. These answers:
- are held in the app’s memory only, for the length of that onboarding session
- are never written to the app’s storage, never synced, and never transmitted anywhere
- are discarded when onboarding ends
They are used only to tailor what the following screen shows you. They do not become part of your health record in the app. If you want any of that information in your record, you log it yourself after subscribing.
3. Apple Health
If you grant Health permission, Orla reads wrist temperature, heart rate variability, sleep, and heart rate so they can be displayed alongside what you have logged.
- Orla reads this data live, at the moment a screen displays it.
- Orla never copies it into its own storage, never includes it in iCloud sync, and never puts it in a PDF export.
- Orla never writes anything back to Apple Health.
- You can change or withdraw Health permission at any time in iOS Settings, under Privacy & Security, then Health, then Orla.
4. Subscription information
Orla uses RevenueCat to manage App Store subscriptions. RevenueCat is one of two third-party software components in the app (the other, AppsFlyer, is described in section 4A). It receives:
- an anonymous identifier generated for your installation, not your name or email address
- your subscription status and purchase history (plan, price, renewal, cancellation)
- basic technical information such as device model, operating system version, app version, and country
Where people stop before subscribing. From version 1.0.4, Orla also tells RevenueCat the date and time a person first reaches each step of the set-up screens and the subscription screen. The list of step names is fixed in the app — each one names a screen and its place in that sequence, never an answer, a symptom, or free text, and it does not change with anything you enter or choose. Orla also tells RevenueCat when a plan is tapped, a purchase starts, a purchase ends without access, or the payment sheet is dismissed.
Each step carries a date and time and nothing else. They are attached to the anonymous installation identifier listed above, not to a name, an email address, or an account. We use them for one thing: to see at which step people stop before subscribing, so that we can fix that step. They are not used to advertise to you, and not used to track you across other apps or websites. RevenueCat keeps them on the same basis as the rest of the subscription record described in section 9.
Which advertisement brought you here. From version 1.0.5, when Orla is first opened it asks Apple for a short token that says whether the download followed a tap on one of our Apple Search Ads advertisements in the App Store, and if so which campaign, ad group and keyword. Apple designs this token so that it identifies the advertisement, not you: it carries no name, no email address, no advertising identifier, and nothing about your searches. Orla passes the token once to RevenueCat, which asks Apple what it stands for and records the answer against the same anonymous installation identifier. We use it for one thing: to see which advertisements bring people to Orla, so that we spend less on the ones that do not. It is not used to advertise to you, and not used to track you across other companies’ apps or websites. If the download did not follow one of our advertisements, Apple’s answer says so and nothing else is recorded.
RevenueCat receives no symptom, cycle, hormone therapy, note, or Apple Health information. It has no technical route to that data. RevenueCat acts as our processor for subscription information. Its privacy policy is at revenuecat.com/privacy.
Payment itself is handled entirely by Apple. We never see your card details.
4A. Measuring our advertising (AppsFlyer)
From version 1.0.6, Orla includes AppsFlyer, a measurement service. We use it for one thing: to see which of our advertisements, for example on Instagram or in the App Store, led to a download. That lets us stop paying for the ones that do not work.
When you install and open Orla, AppsFlyer receives:
- that the app was installed or opened, and when
- an identifier Apple gives the app for your device, which is different in every company’s apps, and an identifier AppsFlyer creates for this installation
- basic technical information: device model, operating system version, language, and your IP address, which AppsFlyer uses to work out your approximate country or region and to detect fraudulent installs
- whether the download followed one of our Apple Search Ads advertisements, the same Apple token described in section 4
AppsFlyer receives no symptom, cycle, hormone therapy, supplement, note, or Apple Health information, and nothing you type into the app. It has no technical route to that data. Orla does not read your device’s advertising identifier (IDFA) and never asks for permission to track you.
For advertisements on Meta (Instagram and Facebook), Orla uses Apple’s SKAdNetwork. With SKAdNetwork, your iPhone itself later tells the advertising network, in a delayed, aggregated form designed by Apple, whether an advertisement led to an install. It carries no identifier for you or your device, and a copy goes to AppsFlyer.
Orla also gives RevenueCat the AppsFlyer installation identifier. This lets us see, in aggregate, whether people who came from an advertisement went on to subscribe. It connects the two services’ records for the same installation. It does not connect them to your name, email address, or anything you log.
AppsFlyer acts as our processor. Its privacy policy is at appsflyer.com/legal/services-privacy-policy.
5. Diagnostic events
Orla records a small number of event names on your device (for example, that an export was generated) so that faults can be diagnosed. These records:
- contain the name of the event and nothing else, by design; they cannot carry your data
- are written to the device’s system log and stay on the device
- are not sent to any analytics, attribution, crash-reporting, or advertising service. AppsFlyer, described in section 4A, receives that the app was installed and opened, not these event names
The subscription steps described in section 4 are the one exception, and they are the whole of it. Those step names, each with a date and time, are sent to RevenueCat and are used for analytics. Every other event name stays on your device.
6. PDF exports
When you generate a summary for a medical appointment, the PDF is created on your device. Where it goes next is entirely your choice, through the standard iOS share options (Mail, Messages, Files, AirDrop, printing). Once you share a file, this policy no longer governs it, and the app has no visibility into or control over it.
7. What Orla does not do
These are statements about the app. Our marketing website is a separate thing and works differently — see section 14.
- No advertising inside the app, and no reading of your advertising identifier (IDFA). Orla never asks for permission to track you. To learn which of our own advertisements led to a download, Orla uses Apple’s attribution token (section 4) and AppsFlyer with Apple’s SKAdNetwork (section 4A).
- No crash-reporting software, and no analytics software that can see anything you log. The subscription steps in section 4 go through RevenueCat. AppsFlyer (section 4A) measures installs and app opens only.
- No sale or rental of personal information to anyone, for any purpose.
- No tracking of you across other companies’ apps or websites.
- No sharing of your health information with data brokers, advertisers, employers, or insurers.
8. Deleting your information
In Settings, “Delete all my data” permanently removes everything the app holds: your logged symptoms, cycle, therapy and supplement records, notes, and your consent record.
Deleting the app from your device removes its local storage.
The subscription steps described in section 4 are held by RevenueCat, not by the app, so deleting your data in the app does not remove them. They contain no health information, only a date and time for each step.
The advertising measurement described in section 4A is held by AppsFlyer, not by the app, so deleting your data in the app does not remove it. It contains no health information. To have it deleted, contact us using the details below.
Deletion is not reversible and we cannot restore data for you, because we never held it.
Your subscription is separate. Deleting your data does not cancel a subscription. Manage or cancel it in the App Store under Subscriptions.
9. How long information is kept
On-device information is kept until you delete it. Subscription records held by RevenueCat are kept for the life of the subscription and for the period afterwards required for financial and tax record-keeping. The subscription steps described in section 4 are part of that record and are kept for the same period. The advertising measurement described in section 4A is kept by AppsFlyer for the period set out in its privacy policy, and we use it only to report on our advertising.
10. Your rights
United Kingdom and European Economic Area (UK GDPR / GDPR). Health information is a special category of personal data and receives additional protection. Our lawful basis for handling what you log is your explicit consent, given on the consent screen in the app and withdrawable at any time by deleting your data or by declining to continue. Our lawful basis for subscription information is performance of our contract with you. Our lawful basis for the advertising measurement in section 4A is our legitimate interest in knowing which of our advertisements work. You can object to it by contacting us.
You have the right to access, correct, delete, restrict, and object to processing, and to data portability. Because what you log stays on your device, you exercise most of these directly: your records are visible and editable in the app, exportable as a PDF, and deletable in Settings. For subscription information, contact us using the details below. You may also complain to your national supervisory authority, or to the Information Commissioner’s Office in the UK.
California (CCPA/CPRA). We do not sell or share personal information as those terms are defined, and we do not use sensitive personal information for purposes requiring an opt-out. The advertising pixel on our marketing website, described in section 14, is operated with Meta’s Limited Data Use setting, which restricts what Meta may do with a California resident’s data. You may request to know, delete, or correct, and you will not be treated differently for asking.
United Arab Emirates (PDPL). We handle personal data under Federal Decree-Law No. 45 of 2021. You may contact us to exercise the rights that law provides.
Everywhere. Regardless of where you live, the deletion control in Settings is available to you.
11. Children
Orla is intended for adults and is not directed at anyone under 18. We do not knowingly handle information from children.
12. International transfers
We hold no health data, so there is no international transfer of it by us. Subscription information, including the subscription steps described in section 4, is processed by RevenueCat, which operates in the United States, under contractual safeguards including the applicable standard contractual clauses. The advertising measurement in section 4A is processed by AppsFlyer outside your country, including in the United States and the European Union, under the same kind of safeguards.
13. Security
Your records rely on Apple’s device encryption. No system is absolutely secure, but Orla is built so that the smallest possible amount of information ever leaves your device.
14. Our website
This section is about orla.tjbventures.ai, the page we advertise. It is not about the app, and nothing described here can reach anything you have logged in Orla.
That page carries the Meta Pixel, a small piece of code from Meta Platforms, so that we can tell whether the ads we pay for actually bring anyone. It records that the page was loaded, which ad brought you (we add a campaign tag to our own links), and whether you tapped the “Download on the App Store” button. To do that it passes Meta your IP address, your browser and device details, and the page address, and it stores a cookie in your browser. If you have a Facebook or Instagram account, Meta may connect that visit to it.
No health information is involved. The website holds none, asks for none, and cannot read the app.
Consent. Outside the United States the pixel is switched off before it starts, and stays off unless you press Accept on the bar at the bottom of the page. Pressing Decline leaves it off. Inside the United States it runs, with Meta’s Limited Data Use setting applied.
Opting out. Press Decline, or clear the site’s cookies, or use your browser’s tracking protection. You can also change what Meta does with advertising data in your own Meta account settings, at accountscenter.facebook.com. None of this affects the app in any way.
15. Changes
We will update the date at the top when this policy changes, and will tell you in the app if the change is significant.
16. Contact
TJB Ventures FZE
Building C1, Ajman Free Zone, United Arab Emirates
info@tjbventures.ai
Privacy queries: info@tjbventures.ai