Privacy

Sandhour, for iPhone  ·  last updated 26 October 2026

Sandhour has no account with us, and no server of ours holds your calendar. That is not a statement about how we behave. It is how the app is built, and it is why this page is short.

What Sandhour collects

Never an event, a title, a place, a person or a note. What leaves your iPhone is this, and none of it is linked to you or used to track you:

• Crash reports. When Sandhour crashes, a report of where in the code it happened, with the iPhone model and the iOS version, so we can fix it.
• How the app is used. Which screens are opened, and what happens on the purchase screen, as counts. There is no advertising identifier, no advertising and no tracking.
• Purchases. That a purchase or a free start happened, which item, and its price, so we know the app pays for itself.
• Speed. How long the app takes to start and to draw its screens.
• An install number and a general location. The measurement above uses a random number for this copy of the app, and works out the country and region from the network address, which it does not keep. Neither says who you are.
• A push address and coming start times. See the small things we run, below.

The crash reports, counts and speed go to Google Firebase, which processes them for us under its data processing terms.

Where your events are

• On the iPhone you are holding.
• With whoever already holds the calendar. If you signed in to an account, that account keeps your events, exactly as it did before Sandhour existed. If you added a calendar link, the events stay wherever that link publishes them.
• Nowhere else. There is no Sandhour server holding a copy, and nothing is uploaded to one.

Sandhour reads and writes those calendars on your device and hands nothing to us on the way through. Remove the app and the calendars are still with the account that held them.

When Sandhour suggests keeping an event as a log, it asks Apple's own language model, on this iPhone. Nothing you type leaves the phone for it.

When you make a meeting

Sandhour can create a Google Meet or a Microsoft Teams meeting while you are typing an event. When you use it, three things are true and worth stating plainly.

• You sign in to your own account with that provider, on that provider's own page. We never see the password, and the sign in is kept on your iPhone.
• Your phone asks that provider to make the meeting, directly. The request does not pass through anything of ours, and the title and time you send are governed by that provider's own privacy policy from the moment they arrive.
• If you never use it, nothing is ever sent, and no sign in is ever asked for.

The small things we run

Neither ever sees an event, a title, a calendar or anything you wrote.

• Waking your phone. Your phone makes up a random key and sends us that key and the address Apple gives your phone for notifications. If you connect a Google or Outlook account, Google or Microsoft tell us, by that key, that something in your calendar changed, and we send your phone a silent notification with nothing in it. Your phone then reads your calendar itself, with its own sign in. We never learn your name, your email or what changed.
• The countdown on your Lock Screen. So the countdown can appear fifteen minutes before a meeting and leave when it starts, even with Sandhour closed, your phone tells us the start times of the next day and a half of meetings. Each comes with a random id that only your phone can match to an event. We keep a start time until its moment has passed, then delete it.

Delete the app and Apple stops accepting that address, and we forget it as soon as Apple says so.

Permissions, and why

• Calendars. So the app can show your days and write the events you make. This is the app, so declining it leaves nothing to draw.
• Contacts. Only if you turn birthdays on, and to complete a name when you invite someone. No contact leaves your device.
• Reminders. Only if you turn Reminders on in Settings, so reminders with a due date appear on their day and can be ticked off. Nothing about them leaves your device.
• Location. Only for the weather on the date widget, and only asked once that widget is on your Home Screen or when you choose Location in Settings. See Apple Weather below.
• Notifications. Asked once, so an event can reach you before it starts. Declining it leaves the rest of the app working.
• Photos and files. Only the ones you choose to add to an event, through Apple's own picker. Sandhour never sees the rest of your library. What you add is kept on this iPhone and, if you use iCloud, in your own iCloud, so Sandhour on your other devices shows it too. It never reaches a server of ours.
• Never anything else. No microphone, no camera, no health data and nothing that reads another app.

Apple Weather

The date widget shows the weather where your iPhone is. Your phone asks Apple Weather for it directly, with your location. That request goes to Apple, never to us, and Apple's own privacy policy covers it. Sandhour keeps the last forecast and the place it was for, on your iPhone only, so the widget does not ask again for six hours. Turn Location off for Sandhour in iPhone Settings and the widget simply shows no weather.

If you sign in to Google

Sandhour asks Google for three things and nothing else. Each one is named here because Google requires an app to say exactly what it reaches for, and because you should not have to guess.

• The list of calendars in your account. So the app can show you which ones there are and let you choose what appears.
• The events on those calendars. Read, so your days can be drawn, and written, so an event you make in Sandhour lands in your own calendar. This is also what creates a Google Meet link when you ask for one.
• Your Google contacts, read only. Only to complete a name while you are adding somebody to an event.

Nothing from your Google account is sold, shared with anybody, or used for advertising. Nothing is used to train an artificial intelligence model, ours or anyone else's. Sandhour uses your Google data to show you your calendar and to save what you write, and for nothing else at all.

Sandhour's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How it is kept safe

Your events are held on your iPhone, inside the app's own storage, which iOS keeps encrypted and locked to your passcode and which no other app can read. The key that lets Sandhour talk to your account is kept in the iPhone's Keychain, the same place the system keeps your passwords, and never in a file of ours.

Every connection to an account is made over an encrypted link, straight from your phone to that provider. There is no server of ours in between, which means there is no copy of your calendar anywhere for anyone to take.

How long it is kept, and deleting it

Only as long as you keep the app. What Sandhour holds is a copy on your own phone so your days open instantly, and it is refreshed from the account every time the app runs.

• Sign out of an account and everything Sandhour held from it goes at once, along with the key that reached it.
• Delete the app and every copy goes with it, in the same moment, because all of it lived inside the app.
• Your calendars are untouched either way. They stay with Google, or iCloud, or whoever held them, exactly as they were.

The crash reports and counts in Firebase carry no name and cannot be traced to you by us. Google keeps them for a limited time and then deletes them.

Payment

The purchase happens inside Apple's App Store. We never see your name, your card or your address. We receive an anonymous record that a purchase occurred, and which item it was.

This website

Everything above is about the app. This website is a different thing, and it is measured. sandhour.app runs Google Analytics, which sets a cookie in your browser and reports back which pages were opened, roughly where in the world from, and which link or search brought you. It is how we know whether anyone is reading this.

That measurement stops at the edge of the website. It has no reach into the app, no way to see an event or a calendar, and no connection to anything you do once Sandhour is on your phone.

The one other thing the site remembers is whether you asked for the light appearance, the dark one, or the one that follows your system. That choice is kept by your own browser, on your own device, and it is never sent anywhere.

The company that hosts these pages records ordinary web server requests, the way every web server does. We do not join those records to anything.

Children

Sandhour is not directed at children under 13, and the app collects nothing that identifies anyone of any age.

Your rights

Data protection law gives you the right to see, correct, export and delete the personal data a company holds about you. We hold none that identifies you, so there is nothing of yours for us to hand over. If you want the anonymous records from your copy of the app removed, write to us and delete the app; without the app, nothing can be tied to it again. Your events belong to the calendar account that holds them, and that account's own export and deletion tools work on them as they always did.

Changes

If this page changes materially, the date at the top changes with it, and the previous version is replaced rather than quietly amended.

Who we are

dymn.io LLC, a limited liability company registered in the State of Wyoming, United States.

Questions about this page: hello@sandhour.app