Stay in Touch Privacy Policy

Who We Are

Stay in Touch is published by StudioBlank LLC. If you have questions about this policy or the app, contact us at hello@studioblank.dev.

What the App Accesses

The app may access contacts that you choose to import, notification permissions for local reminders, and optional in-app purchases processed by Apple.

What Data We Collect

Stay in Touch is designed to work primarily on your device. Contact information is read so you can choose people inside the app. Selected contact identifiers, reminder settings, and app preferences are stored locally on your device.

We do not collect analytics, advertising identifiers, or tracking data. We do not receive your payment card details; Apple handles optional in-app purchase transactions.

How Data Is Used

Your data is used only to operate app features, including to:

• let you pick contacts,
• schedule local reminder notifications,
• open Messages with a selected contact, and
• support optional tip jar purchases through Apple.

Sharing and Third Parties

We do not send your app data to our servers, sell your data, or share it with advertisers or analytics providers.

Apple may process data related to in-app purchases through StoreKit. The app also relies on Apple frameworks such as Contacts and UserNotifications to provide core functionality. We do not use other third-party SDKs for analytics or advertising.

Storage, Retention, and Deletion

App data is stored locally on your device. It remains there until you remove contacts from the app, change your reminder settings, or delete the app. We do not retain this data on our own systems.

Your Choices and Permissions

You can revoke Contacts access or turn notifications off at any time in iOS Settings. You can also remove contacts from within the app. Deleting the app removes its locally stored data from your device.

Children

Stay in Touch is not directed to children under 13, and we do not knowingly collect personal information from children.

Changes to This Policy

We may update this policy from time to time. If we do, we will post the revised version on this page and update the effective date above.