Privacy Policy
Effective 13 August 2026 · ~6 minute read
Hamdam does not collect your data. It observes a small set of signals, on your own device, to shape today's reflection, and those signals stay there. There is no Hamdam server watching what you do, no profile built up behind the scenes, and nothing collected to sell or trade.
This policy explains, plainly, what Hamdam looks at, why, and what it never touches. It covers the Hamdam app for iPhone and Apple Watch, and this website.
Hamdam is made by Seyed Valiallah Azizollahi, also known as Ealia Azizollahi. Both names refer to the same person, and both appear in this policy and in the Terms of Service.
1. Data Hamdam Accesses
Each of the following is opt-in. Hamdam works without granting any of them; enabling one simply lets that part of the reflection experience use the relevant signal.
1.1 Health data (HealthKit)
With permission, Hamdam reads:
- Resting heart rate and heart rate variability (HRV SDNN)
- Sleep analysis
- Blood oxygen saturation
- Step count, exercise minutes, and active energy burned
- Menstrual flow, only if you separately enable cycle awareness
With permission, Hamdam writes State of Mind entries to Apple Health when you enable mood logging. These signals shape today's reflection qualitatively: a gentle nudge in tone, not a score or a chart. They stay on your device. Cycle awareness is a separate opt-in from the other health signals, and is never displayed anywhere in the Hamdam interface.
1.2 Calendar data (EventKit)
With permission, Hamdam reads free/busy time only, never event titles, descriptions, attendees, or locations. Separately, with its own permission, Hamdam can write optional reflection blocks and cultural moment reminders to your calendar. Every event Hamdam creates is written to a dedicated “Hamdam” calendar and prefixed “Hamdam:” so you can always tell it apart. Hamdam recognises its own events by that calendar's identifier rather than by matching the title text, so renaming an event never puts it out of Hamdam's reach, and never brings one of your own events within it. Hamdam never modifies any event it didn't create. Reading and writing calendar data are separate opt-ins. Enabling one does not enable the other.
1.3 Location and weather
Location is only used when you enable weather or cultural moment features. Weather comes through Apple's WeatherKit, using your location to theme today's reflection. Hamdam does not store your location and does not share it with anyone.
1.4 iCloud synchronisation
iCloud synchronisation requires a Hamdam Plus subscription. On the free tier your data stays on your device and is never written to iCloud. If you have Plus and enable sync, your journal entries, streak counter, and settings sync between your own devices through Apple's CloudKit Private Database, scoped to your Apple ID. Hamdam does not run servers that receive this data. If you delete your iCloud data or sign out, the synced Hamdam data goes with it.
1.5 Persian poetry content
The verses in Hamdam, from Hafez, Rumi, Saadi, Khayyam, and Parvin Etesami, are curated by Hamdam and sourced from the public domain via Ganjoor.net with attribution. The core library of 235 verses is built into the app itself and needs no network connection to read. Separately, Hamdam Plus subscribers receive a pool of additional verses that is stored in a CloudKit Public Database and fetched as it grows. Free users never fetch that pool. All of this content is read-only for users and contains no data about you.
1.6 Discover recommendations (iTunes Search API)
Hamdam's Discover tab refreshes once a day with books and podcasts from Apple's public catalogue. These requests go from your device directly to Apple, never through a Hamdam server, and no identifier tied to you is sent with them.
1.7 AI-generated reflections (Apple Intelligence)
On supported hardware (iPhone 15 Pro and later, iOS 26+), reflections are generated on-device using Apple's Foundation Models. No text and no personal data leaves your device for this. On unsupported devices, Hamdam falls back to a static, pre-written content library.
2. What Hamdam Does Not Collect
- No user accounts, and no email collection at signup
- No dedicated crash-reporting or analytics SDK. The only crash data collected is Apple's own built-in iOS crash reporting via App Store Connect, aggregated and anonymised
- No advertising SDKs: no AdMob, Meta Pixel, or tracking pixels
- No behavioural tracking and no user profiling
- No selling of data, ever
- No Hamdam-owned backend servers receiving user data
- No newsletter and no marketing automation
- No cross-app tracking
- No SDK collecting personal data on Hamdam's behalf
- No cookies, because this website is fully static
- No third-party font loading: fonts are hosted locally, with no requests to Google Fonts or any other font CDN
2.1 What this website does collect
This website uses Cloudflare Web Analytics to count page views. It records aggregate, cookieless page counts only. It sets no cookie, it does not track you across sites, and it cannot identify you. Hamdam uses none of Firebase, Mixpanel, Amplitude, or Google Analytics.
This applies to the website alone. The Hamdam app carries no analytics of any kind.
3. How Your Data Is Used
The signals described in Section 1, where you've enabled them, are used only to:
- Shape the tone and content of today's reflection
They are never used:
- For advertising
- To train AI models outside your device
- Shared with third parties
- Sold, under any circumstance
4. Data Storage and Retention
- Locally, on your device, using Apple's SwiftData framework
- In the cloud, only in your own iCloud account, if you enable sync
- Never on a Hamdam-owned server
Data is retained until you delete it in the app or uninstall Hamdam.
5. Third-Party Services
Hamdam is built on Apple's frameworks: iCloud, HealthKit, EventKit, WeatherKit, StoreKit, MusicKit (Apple Music), and Foundation Models. Apple's own privacy policies govern how these frameworks handle data on Apple's side. Ganjoor.net is credited as the public-domain source of Persian poetry text. No data is exchanged with Ganjoor.net at runtime. The iTunes Search API is an Apple public API, called directly from your device. Two of these frameworks load images as they display them: Apple Music artwork in the mini player, and the WeatherKit attribution mark shown beside a forecast. Both come from Apple's own servers.
Hamdam reads poet biographies and cultural symbol descriptions from the Wikipedia REST API (en.wikipedia.org), and the accompanying portrait images from upload.wikimedia.org. Your device sends only the title of the page being looked up. Nothing about you, your reflections, or your health is included in those requests.
The cultural symbol cards in Roots each show a photograph that Hamdam is licensed to display, and finding one takes your device to a few reference services. It askswww.wikidata.org which image is recorded for the subject, using a fixed identifier that ships inside the app. It then askscommons.wikimedia.org for that image's licence and credit, because a photograph cannot lawfully be shown without them, and loads the picture itself from upload.wikimedia.org. If Wikimedia holds nothing Hamdam may use, it asksapi.inaturalist.org for the same subject by its scientific name and loads any resulting photograph frominaturalist-open-data.s3.amazonaws.com, where iNaturalist serves its open data images. Every value sent is a fixed identifier or a species name compiled into the app. Nothing about you, your reflections, your journal, or your health is included, and no account or device identifier is attached.
Nager.Date (date.nager.at) supplies public holiday dates so the Roots calendar can show the days that matter where you live. Your device sends a country code and a calendar year, and nothing else. The country code is derived on your device from the same location permission already used for weather; your coordinates are never sent to Nager.Date. The request carries no account, no device identifier, and no personal information, and Hamdam refreshes it at most once per calendar year.
In full, the hosts Hamdam contacts that are not operated by Apple are: en.wikipedia.org, upload.wikimedia.org, www.wikidata.org and commons.wikimedia.org, all run by the Wikimedia Foundation; api.inaturalist.org and inaturalist-open-data.s3.amazonaws.com, which serve iNaturalist's photographs; and date.nager.at. There are no others. A link you tap that opens in your browser, such as an Apple Music search or the source credit under a photograph, is a page you have chosen to visit rather than a request Hamdam makes.
6. Your Rights (Australian Privacy Principles)
- Access: your data lives on your own device (and your own iCloud, if sync is on)
- Correction: edit or delete any entry in the app, any time
- Complaint: contact Hamdam first (Section 11); if unresolved, the OAIC (Section 12)
- Opt out: turn off any feature in Settings, at any time
7. Account Deletion
Go to Settings → Content → Delete all my data in the app. This clears your reflections, favourites, and streak and lifetime statistics, both in local SwiftData storage and in their CloudKit Private Database copies. Three records are deliberately kept: your language preference, your weather settings, and your subscription status, so that your purchase and your usage limits survive reinstalling the app. None of the three contains anything you have written. Signing out of iCloud on a device also removes Hamdam's synced data from that device. There is no account to delete, because Hamdam doesn't have accounts.
8. Data Security
- iOS Data Protection encrypts data at rest on your device
- Apple's end-to-end encryption applies to iCloud data where you've enabled it
- Any network request Hamdam makes uses HTTPS/TLS
9. Children
Hamdam is not intended for users under 13, and Hamdam does not knowingly collect data from anyone under 13. Hamdam is designed to be age-appropriate for users 13 and over.
10. Changes to This Policy
If this policy changes materially, you'll be notified through an app update. Continuing to use Hamdam after a change means you accept the update. The effective date at the top of this page always reflects the current version.
11. Contact
Email developer@hamdam.com.au.
Seyed Valiallah Azizollahi (sole trader) · ABN 74 389 481 503 · Brisbane, Queensland, Australia
12. Complaints and Regulatory Contact
If you raise a concern with Hamdam and it isn't resolved to your satisfaction, you can contact the Office of the Australian Information Commissioner (OAIC) atoaic.gov.au.
13. Governing Law
This policy is governed by the laws of Queensland, Australia. The Australian Privacy Principles under the Privacy Act 1988 (Cth) apply to how Hamdam handles personal information.
HAMDAM™ is the subject of Australian trade mark application no. 2674427 (filed 11 July 2026), owned by Seyed Valiallah Azizollahi. All rights reserved.
See also our Terms of Service.