Privacy Policy

Effective date: July 25, 2026 Last updated: September 8, 2026

This Privacy Policy describes how the 300 Club Scheduling app ("300 Club", "we", "us", or "our") collects, uses, and shares information when you use our mobile application (the "App") and related services.

1. About the App

300 Club is a scheduling app that helps a Rabbi and members of a learning community coordinate short daily Torah learning calls. The App is intended for adult use only.

2. Information We Collect

2.1 Information you provide

• Account & profile information: first name, last name, email address, phone number (in E.164 format), and your IANA timezone.
• Sign-in identifiers: when you sign in with Apple or Google, we receive an identity token and, where available, your name and email from the provider.
• Scheduling activity: slot claims, snag invite selections, snooze actions, and check-off state indicating whether a call took place.
• Rabbi notes: optional free-text notes a Rabbi may record about a member's participation.
• Contacts you choose to import (Rabbi only): a Rabbi may add members from their device's address book. The App reads contact names, phone numbers, and email addresses on the device in order to show a list to choose from. Only the contacts the Rabbi explicitly selects are sent to our servers; nothing is selected by default, and the contacts that are not selected are never transmitted or stored.

2.2 Information collected automatically

• Push notification token: a device-specific token issued by Expo's push service and the platform type (iOS or Android), used to deliver alarms and invites.
• Timestamps: account creation, update, and notification dispatch timestamps for auditing and idempotency.
• Call activity (Rabbi only, and only if switched on): if a Rabbi turns on automatic check-offs, the App observes when a call starts and ends on that device in order to measure how long it lasted, and records that a scheduled call was completed together with its measured duration. We never record, store, or transmit call audio or call content, and we do not use the microphone. Automatic check-offs are approximate — the measurement cannot distinguish a long voicemail from a long conversation — and can be reversed in one tap from the notification.

How call activity is observed. On Android, the App uses the READ_PHONE_STATE permission to see call-state changes (ringing, in-call, idle). These carry no phone number, and the App does not read the device's call log. A call is therefore only ever associated with a member when the Rabbi started that call from inside the App, because that is the only way the App knows who was dialled; calls placed from the phone's own dialer are not associated with anyone. Only the resulting check-off and its measured duration are sent to our servers. The permission can be revoked at any time in Android system settings, after which check-offs revert to manual.

2.3 Information we do not collect

We do not currently use third-party analytics, advertising, or crash-reporting SDKs. We do not collect precise location data, photos, microphone, or camera data. We do not record or listen to call audio. We do not upload a Rabbi's address book, and we do not transmit or retain any call log.

3. How We Use Information

We use the information above to:

• Create and maintain your account and authenticate you on each device.
• Assign, display, and manage call slots and reminders.
• Send push notifications for alarms, snag invites, and scheduling changes.
• Provide the Rabbi with the roster and notes needed to run the program.
• Add members a Rabbi has selected from their device's address book.
• Automatically mark a scheduled call as completed when its measured duration meets the program's minimum length, where a Rabbi has turned that feature on.
• Debug, secure, and improve the App.

4. How We Share Information

We share information only with service providers that help us operate the App:

• Supabase — stores your account, profile, scheduling, device, and notification records in a hosted Postgres database and handles authentication.
• Vercel — hosts the backend API that processes requests between the App and the database.
• Expo Push Service — receives your push token, member identifier, and notification payloads (including slot times and, for snag invites, phone number) in order to deliver notifications.
• Apple and Google — receive standard OAuth requests when you choose to sign in with their services.

We do not sell your personal information and do not share it with advertisers.

5. Data Retention

We retain account and scheduling data for as long as your account is active. When a member is removed from the program, records are soft-deleted (archived) so the Rabbi can audit prior participation. You may permanently delete your account and associated personal data at any time from inside the App (Profile → Delete account for members; Settings → Delete account for the Rabbi). Deleting your account removes your sign-in, profile, device tokens, and scheduling records from our systems. You may also request deletion by contacting us (see Section 11).

We store call activity as a single duration per completed scheduled call. We do not retain a stream of call-state events, and call observation itself happens only on the device.

6. Data Security

Access to database rows is controlled by Row-Level Security policies, and all client requests are mediated by our backend API. Transport is protected by HTTPS. No system is perfectly secure; we cannot guarantee absolute security of your information.

7. Your Rights

Depending on where you live, you may have the right to access, correct, delete, or export the personal information we hold about you, and to withdraw consent for certain uses. To exercise these rights, contact us using the details in Section 11.

8. Service Availability

The Service is offered only to users located in the United States. It is operated using service providers that store and process data in the United States. If you access the App from outside the United States, you do so on your own initiative and are responsible for compliance with local law.

9. Children

The App is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us and we will delete it.

10. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date above and, where appropriate, provide additional notice in the App.

11. Contact Us

If you have questions about this Privacy Policy or our data practices, contact us at:

mann.robison@gmail.com

See also the Terms of Service.