This Privacy Policy describes how Revenue Stream Holdings, LLC (“we,” “us”), doing business as Pulse Checks, handles information in the Pulse Checks iOS app and on meetpulse.us. Pulse Checks is designed to keep relationship data on your device. We do not require an account and we do not operate a social feed.

Our Terms of Use govern your use of the app and site. This page is a product-aligned summary for App Store and user transparency. It is not legal advice. Contact support@meetpulse.us with questions.

No sale or sharing of personal information

We do not sell or share personal information, as those terms are defined under the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA) and similar U.S. state privacy laws.

1. No Pulse Checks account

You do not create a Pulse Checks login. We do not run a Pulse Checks messaging server that sends texts for you. When you choose Wave (a quick preconfigured emoji or short message) or Message (a fuller message you compose), the app hands off to Apple Messages.

2. Information on your device

The app stores the following locally on your iPhone:

The following are not copied or persisted by Pulse Checks. They are read live from the iOS Contacts framework each time they are needed (for example, displaying the board, filling a Messages handoff, or checking a birthday-reminder flag):

Stored data stays on your device unless you enable sync tools described below or export it yourself. If you revoke Contacts access, or the underlying contact is deleted or edited in Apple’s Contacts app, Pulse Checks reflects that on the next lookup — there is no stored copy of those contact fields to fall back on.

3. Contacts

If you allow Contacts access, Pulse Checks uses Contacts to link people on your board and to read, at the time they are needed, the name, phone number, email, or birthday for display, birthday reminders, and Messages handoff. Linking stores only the iOS Contact identifier locally — a reference, not the underlying contact fields. Contact access is optional for some flows, but linking a contact with a phone number or email is required to add individuals for messaging. We do not upload your address book to a Pulse Checks server, and we do not persist the underlying contact fields (name, phone, email, or birthday) locally either — only the reference identifier is kept.

4. Notifications

With your permission, Pulse Checks schedules local notifications (“Pulse Checks”) to nudge you to check in. Notification content may include a name and a short note you saved. If you enable app lock and turn off showing names on the Lock Screen, whispers use generic copy instead.

5. Face ID / device lock

Optional Face ID or passcode lock protects access to the app on your device. Biometric data is processed by iOS and is not sent to us.

6. Optional iCloud sync

If enabled through Apple’s iCloud features for the app, some of your board data may sync via your private iCloud container for Pulse Checks. That sync is provided by Apple under Apple’s terms and privacy practices. We do not operate a separate Pulse Checks cloud account for that data.

7. Inspiration drafts & Apple Intelligence

Optional inspiration drafts may use Apple’s on-device models when Apple Intelligence is available on your device. When on-device generation is unavailable, the app can fall back to on-device string templates. Prompt content is built from information already on your device (such as a name and your note). We do not send inspiration requests to a Pulse Checks backend.

8. Purchases & subscriptions

Premium subscriptions are sold through Apple’s App Store / StoreKit. Apple processes payment and related purchase account information. We receive subscription status needed to unlock Premium features; we do not receive your full payment card details.

9. Website

The meetpulse.us site is a static informational site. It does not require a login. Standard web server logs (such as IP address, browser type, and pages requested) may be collected by our hosting provider (for example Namecheap) as part of operating the site. We do not intentionally embed third-party advertising trackers on these pages.

10. Analytics & crash reporting

We do not use third-party analytics or crash-reporting SDKs.

Separately, if Apple App Store Connect analytics are enabled for the app, Apple may provide us with aggregated App Store usage metrics under Apple’s privacy practices. Those reports do not give us access to your on-device board data.

11. Security

We use reasonable administrative and technical safeguards appropriate to this product’s design: app data is stored on your device under iOS protections, and optional sync or purchase-related data that passes through Apple (such as iCloud or StoreKit) is handled by Apple under Apple’s security and privacy practices. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.

12. Children

Pulse Checks is not directed at children under 13. Do not use the app if you are under 13.

If we become aware that a child under 13 has used the app, we will direct the account holder or device owner to remove the data using in-app deletion controls or by uninstalling the app (and, if applicable, managing any iCloud copies through their own Apple ID / iCloud settings). Because Pulse Checks stores board data on the user’s device and we do not operate a backend that holds individual user data, Revenue Stream Holdings, LLC has no technical ability to access, delete, or modify a child’s Pulse Checks data on our systems.

13. Data retention & deletion

You can delete people or use in-app erase / reset controls to remove local app data from your device. Uninstalling the app removes local app data. iCloud copies, if any, are managed through your Apple ID / iCloud settings. To stop notifications, revoke notification permission in iOS Settings or adjust settings in the app.

Because name, phone number, email, and birthday are never stored by Pulse Checks to begin with, there is nothing for you to delete — or for us to retain — regarding those specific fields. Deletion controls apply to the data that is genuinely stored: notes, nicknames, cadence / check-in history, app settings, and the contact identifier (the link itself).

14. Your rights

Depending on where you live, privacy laws such as the CCPA/CPRA and similar state frameworks (including in Virginia, Colorado, Connecticut, Utah, and other states with comparable laws) may give you rights to access, correct, or delete personal information, and to make related requests.

Pulse Checks is built so that relationship and board data stay on your device. There is no Pulse Checks account and no Pulse Checks backend server that stores your board. That means you are the only party with practical control over that data:

Revenue Stream Holdings, LLC has no technical access to, and cannot itself delete, remove, or modify, any individual user’s on-device or private iCloud board data, because none of that data resides on our systems. We cannot fulfill an access, correction, or deletion request in the way a server-based company would by wiping records on our infrastructure — there are no such records for us to wipe.

If you still have a question about these rights, email support@meetpulse.us. We can explain the in-app and Apple controls available to you; we cannot remotely alter data we do not hold.

15. International users

Revenue Stream Holdings, LLC is the data controller for information described in this Privacy Policy. Given Pulse Checks’ on-device design, minimal to no personal data about your board is transferred internationally by us. Services provided by Apple (such as the App Store, StoreKit, or optional iCloud) may involve Apple processing under Apple’s own terms and privacy practices.

16. Changes

We may update this Privacy Policy as the product changes. The “Last updated” date above will change when we do. Continued use of the app after an update means you acknowledge the revised policy.

17. Contact

Email: support@meetpulse.us
Website: https://meetpulse.us

See also our Terms of Use.