Privacy Policy

Last updated: 4 August 2026

Overview

Perirosa is a reproductive and hormonal health app for iPhone, iPad and Mac, published by DynamWorks LLC. It records some of the most sensitive information a person can write down: menstrual cycles, hormone therapy doses, symptoms, pregnancy, and free-text notes.

DynamWorks LLC does not collect, receive, transmit, store or have access to any of it. There is no account to create, no server to sync with, and no analytics. Everything you log is written to a private database on your own device and stays there.

This policy explains what that means precisely, including the small number of cases where data can leave your device because you chose to send it somewhere.

Data We Collect

None. Perirosa has no user accounts, no sign-in, no email capture, and no server infrastructure of any kind. We do not know that you have installed the app, we do not know who you are, and we could not produce your data if we were asked to — because we have never had it.

What Stays on Your Device

All of the following is stored only in the app's private database on your device:

You can erase all of it at any time from Settings → Privacy Controls → Delete all data. Deleting the app also removes the database.

Health Data

Much of what Perirosa stores is health data concerning sex life and sexual health. Under the UK and EU General Data Protection Regulation this is a special category of personal data (Article 9) that attracts additional protection.

Perirosa's answer to that obligation is architectural rather than procedural: we do not process this data at all. It is never transmitted to us, so there is no lawful-basis question to answer, no processing agreement to rely on, no retention schedule on our side, and no breach of our systems that could expose it.

When Data Can Leave Your Device

There are three ways information can move off your device. All three require a deliberate action by you, and none of them sends anything to DynamWorks LLC.

1. The doctor PDF, when you share it

Perirosa can generate a clinical summary PDF from your records. It is created entirely on your device. Nothing happens to it until you use the share sheet — at which point it goes wherever you send it: your own Files, an email, a messaging app, a printer. That destination's own privacy policy then applies. If you email it, a copy exists in your sent mail and on the recipient's device.

2. Apple Calendar, if you turn it on

Perirosa can optionally create appointment events in Apple Calendar. This is off by default and requires you to grant calendar permission.

When enabled, Perirosa creates a dedicated "Perirosa" calendar and prefers to place it in a local, on-device calendar account so events do not sync anywhere. If your device has no local calendar account available, Perirosa will tell you before continuing and ask you to confirm a second time — because in that case the calendar, and the event titles and notes you type into it, will be stored in whichever account your device uses (typically iCloud) and will sync to Apple's servers and to your other devices under that account.

Anything you type into an appointment title is what syncs. If you would rather a clinic name or treatment not leave your device, either leave this feature off or keep titles non-specific.

3. Device backups

If you back up your device to iCloud or to a computer, the backup includes Perirosa's database along with your other app data. This is standard iOS and macOS behaviour and is outside the app's control. iCloud backups are encrypted by Apple. Unencrypted local backups to a computer are not — we recommend enabling the "Encrypt local backup" option in Finder or iTunes if you back up that way.

Apple Health

This version of Perirosa does not read from or write to Apple Health. The app does not request Health permissions and does not link the HealthKit framework. If a future version adds Health integration it will be opt-in, and this policy will be updated before that version ships.

Notifications

Reminders for doses, periods and appointments are scheduled locally on your device using Apple's local notification system. There is no push server, and no notification content is ever sent over a network.

Notification text can appear on your lock screen. Perirosa includes a Discreet notifications setting, on by default for cycle-related reminders, which replaces the text with a neutral title so nothing identifiable is displayed.

Purchases

Subscriptions and the lifetime purchase are processed entirely by Apple through the App Store. We never see your name, payment details or Apple Account. Perirosa asks Apple's on-device StoreKit framework whether the current Apple Account holds a valid entitlement, and unlocks features accordingly. Your purchase is governed by Apple's Privacy Policy.

Analytics and Tracking

Perirosa contains no analytics SDK, no crash reporting service, no advertising framework and no tracking of any kind. We do not use cookies, device identifiers, fingerprinting, or the Advertising Identifier, and the app never presents an App Tracking Transparency prompt because there is nothing to track. No data is used for advertising, profiling, or sold or shared with anyone, ever.

Third-Party Services

Perirosa integrates with no third-party services. It uses only Apple's own on-device frameworks — SwiftData for storage, StoreKit for purchases, UserNotifications for reminders, EventKit for the optional calendar feature, and PDFKit for the report. The app ships with zero third-party software dependencies.

Data Retention and Deletion

We retain nothing, because we receive nothing. Your data persists on your device for exactly as long as you keep it. You can delete all of it in one action from Settings → Privacy Controls, or by deleting the app.

Note that deleting the app does not remove data you have already sent elsewhere — a shared PDF, or events written to a synced calendar account. Those you would need to remove from wherever you sent them.

Your Rights

Depending on where you live, you may have rights under the GDPR, the UK GDPR, the California Consumer Privacy Act, or similar laws — to access your data, correct it, delete it, port it, or object to its processing.

We want to be straightforward about how those rights work here. Because DynamWorks LLC never receives your data, we cannot access, export, correct or delete it on your behalf — there is nothing on our side to act on. You hold all of it, and the app gives you the controls directly:

We do not sell or share personal information as those terms are defined under the CCPA, and we never have. If you have a question about any of this, write to us at the address below.

Children's Privacy

Perirosa is intended for adults managing their own reproductive and hormonal health, and is not directed at children. We do not knowingly collect data from anyone — including children — because we do not collect data at all.

Security

Perirosa's database is stored inside the app's private container, protected by the operating system's sandbox and by your device's own encryption, which is tied to your passcode, Face ID or Touch ID. On macOS the app runs sandboxed and is built without any network capability at all.

The strongest security property of this app is a structural one: there is no server holding your data, so there is no server to breach.

Changes to This Policy

If we change this policy we will update the date at the top of this page. If a future version of the app changes what happens to your data in any material way, we will say so here before that version ships.

Contact

Questions about this policy or about privacy in Perirosa can be sent to the address below. DynamWorks LLC is the data controller for the purposes of the GDPR and UK GDPR.

DynamWorks LLC
10 W Bay State St #7004
Alhambra, CA 91801
contact@dynamworks.com