Your information and choices
Privacy Policy
Effective and last updated: October 21, 2026
Read Bayside without an account. When you reserve a chair or send a message, we use the information you provide to support the study and respond to you.
Email a privacy requestWho operates Bayside
Bayside with Pops is operated by Jay Carver of JCMNJ, with Jim Carver (Pops) hosting the Bible study in Ocean City, New Jersey. This policy covers the Bayside website and Bayside mobile app.
For privacy questions or requests, email james@jcmnj.com with the subject “Bayside privacy request.” You may also contact Pops at jim.carver500@gmail.com.
Information you provide
You can read public Bayside content without creating an account. Reserving a chair requires your name and an email address, phone number, or both. You can also reserve for named guests, with optional email and phone details shared with their permission. Each guest has an individual reservation linked to the person booking. Guest details do not grant permission for future updates. We store the gatherings selected, reservation or reserve-list status, timestamps, contact preferences and permissions, and any attendance check-in or check-out recorded by a host. Hosts can also add or correct contact and attendance records.
We keep contact records across gatherings, including duplicate-contact review and merge history, so hosts can manage reservations and contact the right person. Gathering signup is separate from a participant account.
Questions, comments, suggestions and survey responses include the text or choices you submit, a random submission or response identifier, timestamps, optional name, and your email address if you request a reply. Leaving your name off does not hide an email address you provide for a reply, identifying details in your message, or technical information processed when the request reaches our services.
Participant accounts, journals and group discussion
All published study guides, recaps, documents, photos, videos and resource links are available without an account. When participant features are enabled, verified email registration is required to keep a journal or participate in discussion. We store an account identifier, the name shown with comments, participation status, acceptance of the participation rules and relevant timestamps.
Journal entries are private to their owner through the application. They are not displayed to Pops, hosts, other participants or in group discussion, and they do not generate host email alerts. The hosting and database services process and store entries; authorized technical operators may need access for maintenance, security, support or legal obligations. Journal access is not end-to-end encryption. We do not store journal drafts in browser storage or queue them for offline sending.
Group comments and replies show the registered author name and are visible to the relevant group and authorized hosts. Breakout membership is managed by hosts. Authors can edit or remove their own comments; hosts can hide, remove, close or archive discussion, review reports and pause discussion access. Moderation history records actions and identifiers. Participant-to-participant private messaging is not provided.
Use My account to export journal entries or choose Delete my account. Eligible Bayside-only sign-ins are permanently deleted together with private journals, memberships and group contributions. Accounts with shared or associated records require an owner-verified deletion review; submitting a request is not completed deletion. Moderation and request metadata may remain for security and recordkeeping, and backups may retain earlier data under the service providers’ retention practices.
Uploaded study files remain private until a host reviews and approves them and attaches them to a published guide. Public download links may remain usable briefly after withdrawal. External resource links are handled by their destination services.
Prayer requests and sensitive information
In the current public website and mobile app, prayer requests are directed to Pops by email or text. The separate online prayer log is not enabled. An email or text request is handled by Pops and the email or messaging services used to deliver it, rather than saved through an active Bayside prayer form.
Prayer messages and study questions may reveal religious beliefs, health concerns or information about other people. Share only what you want the hosts to receive, avoid unnecessary sensitive details, and obtain permission before identifying someone else. Tell Pops whether a prayer request may be shared with the group. Contact him to change that instruction. Information already shared in a gathering or delivered to another person cannot necessarily be recalled.
If online prayer intake or community posting becomes available, we will update this policy to explain the collection, access and sharing involved.
How we use information and who can see it
We use information to reserve chairs, manage capacity and attendance, answer questions, prepare gatherings, send confirmations and Bayside updates, respect contact preferences, review duplicate records, and operate and troubleshoot the service.
Reservation names, email addresses, phone numbers and individual attendance records are available to authorized hosts and administrators, not displayed in the public chair tally. The public tally shows counts.
Submitted questions and individual survey responses are available to authorized hosts and administrators. They are not automatically posted publicly. Host email alerts contain generic activity notices and a link to authenticated management pages, rather than private message text or reply addresses. Survey totals can be displayed publicly when results are enabled. Questions may inform group discussion; avoid including details you do not want discussed and tell the hosts if your message is confidential.
Authorized administrators use authenticated management pages. Their account identifiers, email addresses, roles, session information and records of administrative actions are processed to control access and maintain records. Administrative records can include previous versions of contact information.
Notifications and your choices
Reservation contact details are used for your booking. Separate, optional choices allow future email and text updates; providing a contact method alone does not grant this permission. We retain permission timestamps and preferences. Existing permissions can be changed by contacting Pops. Confirmation and invitation emails can be sent through our email service. Hosts can also use their email or messaging app to send reminders and notices.
When a Bayside participant sign-in link is accepted for sending through the account form, authorized hosts receive an activity email identifying the address used. The notice does not contain the authentication link or prove that sign-in or registration was completed.
Submitting a question and asking for a reply does not itself enroll you in gathering updates. To change your details or preferred contact method, or stop future invitations and reminders, email james@jcmnj.com or tell Pops. The current native app does not implement push notifications.
Cookies, local storage and technical information
If you choose Remember my name and contact details on this device when reserving, we save those details in local storage after a successful reservation so you can reuse them. This is optional and does not sign you into an account. Use Forget my details or clear browser or app storage to remove this local copy. Avoid enabling it on shared devices.
Survey forms store a random response identifier and completion flag on your device to help prevent repeat responses. The identifier is sent with your answer. This is not an advertising identifier. A separate random request identifier helps avoid duplicate question submissions.
Administrative sign-in uses a session cookie. The native app also stores a copy of public gatherings, announcements, Scripture and recap content for offline reading. Its offline cache does not include submitted form entries or private prayers. Clearing browser or app storage removes local copies and response flags, but does not delete records already submitted to us.
When you connect, hosting and service providers process technical information such as your IP address, request details, browser or device information, timestamps and errors to deliver and operate the service. Provider logs and any configured error monitoring may retain technical information.
The website loads Google Analytics for usage measurement, which can process page visits, interactions, browser and device information, IP-derived approximate location and cookie identifiers. Browser cookie controls and content blockers may limit that collection. Bayside routes exclude PostHog initialization and stop its session recording; this does not remove the separate Google Analytics integration. The native app source does not include the website’s Google Analytics or PostHog providers. Pages opened in its browser are subject to the website’s practices.
Service providers and external resources
Vercel hosts the website and API. Supabase stores Bayside records and supports administrative authentication and hosted assets. Resend processes outgoing application emails, including recipient addresses and message content. Email delivery records can include recipient address, subject, delivery status, provider identifier, errors and related submission or gathering identifiers. Host email and text communications also involve the hosts’ mailbox providers and mobile carriers.
When video resources are enabled, Mux receives uploaded recordings for video conversion, storage and streaming. Opening a video connects your device to Mux delivery services, which receive technical request information such as your IP address and browser details. Draft recordings are for host review; published study resources are available without an account. We retain the original recording for review and recovery unless it is separately removed.
The shared website includes Sentry error-monitoring integration that runs when configured. Its production activation and provider-side retention are not established by this policy. Google Analytics is present on the live website. We do not treat the presence of a library elsewhere in JCMNJ’s code as proof that it receives Bayside submissions.
When Jay enables watching for a gathering, the embedded YouTube player loads automatically and requests muted playback. This connects your device to YouTube and shares technical request information such as IP address and browser details. Playback may require pressing Play. YouTube controls sound and its own service policies apply. Joining Zoom opens Zoom separately for two-way participation; displaying a Bayside watch link does not start or stop a broadcast.
Bible.com and YouVersion are external Bible resources. Bayside does not receive your Bible-app login, reading history or account information merely because you follow those links. Their own privacy policies govern their services. The Bible App card loads an image from YouVersion’s asset service, so that service receives the technical request needed to display it even before you follow a link. Maps, linked videos and other external resources may similarly process information when opened.
Our verified Bayside submission flows do not include advertising placements, data-broker sharing or a sale of submission information. Service-provider processing and any separate external services are described above.
Storage, protection, retention and deletion
Bayside records are stored in the connected Supabase database; the website and API run on Vercel. These services can process information outside your state or country. Access to private management features requires authentication and role checks. Bayside database tables have row-level security enabled, and server-side code handles privileged database access. Connections to the public service use HTTPS. These measures reduce risk but cannot guarantee absolute security.
There is no fixed automatic deletion period established for Bayside contact records, reservations, questions, delivery records or contact-history records. Records can remain until the operator removes them. Archiving a contact, gathering or submission is not the same as deleting it. Provider logs, backups, delivered emails and host messages have separate retention arrangements; we do not promise a specific deletion deadline for those copies.
To request access, a copy, correction or deletion of your information, or withdrawal of contact permission, email james@jcmnj.com. Describe the request and provide the name and contact method used, plus a gathering date or submission details if relevant. Do not send passwords or unnecessary sensitive information. We may ask for enough information to verify the request before disclosing or changing a record.
A deletion review needs to cover linked reservations, contact records, questions, delivery records and historical copies, not only the visible contact entry. We will explain any records that need to be retained and any limits involving backups, legal obligations or messages already delivered to others. When participant accounts are enabled, My account provides Delete my account. Eligible Bayside-only sign-ins are permanently deleted with their journals, memberships and discussion contributions. Records indicating shared JCMNJ use, host ownership, gathering participation or uncertain ownership require a deletion review; the screen clearly says when a request is pending rather than completed. Contact the privacy address for help with associated records and historical copies.
Children’s privacy
Bayside’s current forms do not ask for a date of birth and do not verify age. They are not designed to establish a child’s age or obtain verified parental consent. A parent or guardian should contact a host directly about a child’s participation rather than submit a child’s personal information through these forms.
If you believe information about a child under 13 has been submitted, email james@jcmnj.com so we can review it and arrange appropriate removal. Public study material may be read without submitting personal information. An App Store age rating does not establish parental consent for data collection.
Changes to this policy
We will update this page when Bayside’s features or data practices change. The date above identifies the latest revision. Contact james@jcmnj.com with questions about this policy or your information.