Osly Privacy Notice

Osly helps you keep a personal record of snooze presses as thermal-style receipts under a night-sky interface. This notice explains how information is handled when you use those morning stacks, seal rituals, archive views, and related tools on your device.

Who this notice is for

Osly is built for individuals who want a lightweight, on-device log of alarm delays and morning wrap-ups. You may open and use Osly without creating a profile, signing in, or maintaining a remote membership identity. There is no mandatory account layer attached to the core snooze-receipt experience.

The kinds of information that may appear in your stacks

Depending on how you use Osly, the app may process categories such as:

• Morning session details you enter or generate, including alarm times, stack labels, weekday tags, snooze timestamps, optional short notes, delay summaries, and seal or wake times.
• Checklist items, alarm presets, leave-by planner values, snooze budget settings, and other tool preferences you configure in the Me area.
• Photos you choose to implant on a receipt or sealed cover, or images captured with the camera for that purpose, plus optional short voice stamps you record while editing a card.
• Exported receipt or stack images you create for sharing through the system share sheet.
• App preferences such as receipt theme, animation toggles, default alarm time, reminder switches, and similar presentation choices.
• Permission-related status for Photos, Camera, Microphone, notifications, and App Tracking Transparency, as reported by the operating system after you respond to system prompts.
• Diagnostic signals the platform may expose in connection with crash or performance reporting if you have enabled such OS-level sharing; Osly does not require a separate cloud account to operate its primary features.

Why Osly processes that material

Processing supports the product’s stated purpose: printing and stacking snooze receipts, sealing a finished morning, browsing archived stacks, calculating simple insights from sealed history, reminding you to seal when enabled, and letting you attach imagery or a brief voice stamp to cards you create. Preferences are stored so your layout and tool settings remain available after relaunch. Permission prompts appear only when you initiate a feature that needs the related resource, such as choosing a library photo, taking a camera shot, recording a voice stamp, or scheduling a seal reminder.

Where information lives on your device

Core stack and receipt records are kept in local application storage on your device. Attached card images are saved as files under the app’s sandbox using relative paths so they can be rebuilt after relaunch. Settings and virtual progress counters used inside Osly are persisted locally through platform storage APIs. Because primary records are device-local, uninstalling Osly or clearing app data typically removes those materials from that installation unless you previously exported content elsewhere yourself.

Permissions and system dialogs

Osly may ask the operating system for access when you:

• Implant a photo from your library onto a receipt or cover.
• Capture a fresh photo with the camera for a card.
• Record a short morning voice stamp.
• Save an image into Photos when you choose that action.
• Receive optional seal reminders through notifications.
• Respond to the App Tracking Transparency prompt shown early in the launch sequence on supported iOS versions.

Each request uses the system’s native dialog. Declining a permission does not block the entire app; related features simply remain unavailable or fall back to alternatives such as bundled sample scenes where offered.

Network pathways and third-party surfaces

Everyday snooze logging does not require you to maintain an online profile. When you open in-app policy pages, Osly may load content through an embedded web view, which involves ordinary network retrieval of those documents. If you export and share a stack image, the destination app or service you select operates under its own terms and practices. Apple’s storefront, device OS services, and any measurement frameworks invoked after you grant tracking permission are governed by Apple’s and the relevant vendor’s disclosures in addition to this notice.

Practical safeguards we apply

Osly relies on the iOS application sandbox, relative-path file handling for attachments, and restrained permission timing so access is requested in context rather than indiscriminately at cold start for media features. We work to reduce unnecessary transmission of morning-stack content. No security measure can eliminate every risk on a personal device; keep your OS updated and protect physical access to your phone or tablet.

How long materials remain

Stacks, receipts, attachments, and preferences generally remain until you delete them inside Osly, clear local data from settings, or remove the app. Pending notification intents are cancelled when you turn related reminders off. Transaction completion markers used only to prevent duplicate in-app credit grants, if present, remain as technical records needed for consistent local state.

Choices available to you

You can decline or later change Photos, Camera, Microphone, Notifications, and tracking permissions in iOS Settings. You can remove individual receipts or sealed stacks, clear local Osly data from the Me area, or stop using seal reminders. You may continue using core logging features without granting optional media permissions by skipping photo or voice attachments.

Younger audiences

Osly is intended for general audiences managing personal morning routines and is not directed at children as that term is defined under applicable child-privacy rules. If you believe a child has provided information to us in a manner inconsistent with those rules, write to dusk.printer@oslynights.app and we will review the concern with care.

Updates to this notice

When Osly’s data practices change in a meaningful way, this page will be revised. Continued use after an update means you have had an opportunity to read the current text. The version that applies to your use is the one presented in the app or linked from it at the time of access.

Governing framework

Privacy questions arising from Osly are interpreted under the laws of the United States and, where they apply to you, other applicable laws and relevant regulatory requirements. Dispute pathways follow competent dispute resolution bodies under those frameworks without naming a specific courthouse in this notice.