Reap
Privacy Policy
Your notes are personal. This policy explains what Reap collects, how we use it, and the choices you have.
Effective
Who this policy covers
Reap ("Reap," "we," or "us") provides the Reap mobile app, reapnotes.com, and the church editorial workspace. This policy covers those services. Questions or privacy requests can be sent to jason@follo.dev.
Information we collect
- Account information: identifiers, name, phone number, email address, profile image, and authentication information provided when you create or use an account. Not every sign-in method requires every field.
- Your writing and activity: notes, journal responses, Scripture selections, highlights, bookmarks, collections, tags, and related dates and settings that you save or sync with Reap.
- Optional media and processing: recordings, uploaded files, transcripts, prompts, chat messages, and generated results when you use those features. Recording is optional and is not needed to write or save a note.
- Church information: your chosen home church and, for staff, workspace membership, teaching content, files, invitations, and publishing activity.
- Technical and purchase information: device and browser information, IP addresses, session and diagnostic logs, usage events, and church billing information, subscription status, or transaction identifiers when a church purchases AI or YouTube upload capabilities. Payment providers handle payment details.
- Support messages: information you send when contacting us.
Some drafts, preferences, and cached content are stored on your device. Content you sync or submit for processing is also handled by Reap's service providers. Notes can contain sensitive information, including religious beliefs; choose what you include and share carefully.
How we use information
We use information to authenticate you, save and sync your content, provide search and Revisit, deliver Scripture and guidance, operate church publishing, process features you choose to use, manage subscriptions, respond to requests, and maintain the reliability and security of Reap. We also use limited activity and diagnostic information to understand and improve how the service works and prevent abuse.
Your notes and your church
Linking a home church does not give church staff access to your private notes, journal responses, recordings, transcripts, highlights, or chat history. Church staff may receive privacy-protected aggregate information about reach and note-taking, with small cohorts suppressed or coarsened. These reports do not provide individual identities or activity histories.
Church staff share access to church-owned workspace content. Content staff explicitly publish or share by public or unlisted links may be viewed by its audience or anyone with the link. Your own export or sharing actions may also disclose the content you select.
Churches retain ownership of the content they create or upload, including material created using Reap's AI tools. Paying for AI or YouTube uploads does not give Reap ownership of that content. We process it to provide the service and carry out the church's requests.
Service providers and optional processing
We use service providers for authentication (Clerk), application data (Convex), hosting (Vercel), file storage (Cloudflare), and other operational functions such as messaging and subscription management. They process information needed to perform their functions for Reap.
When you request transcription or AI features, the relevant audio, text, conversation, or selected source material is sent to providers that perform that processing. This may include Deepgram for transcription and model providers accessed through Vercel AI Gateway for generated text. Generated material can be inaccurate and is distinct from your writing, Scripture, and church-authored teaching.
We do not sell personal information or use private notes for targeted advertising. We may disclose information when required by law, to protect people or the service, or as part of a business transfer subject to appropriate privacy protections. Authorized personnel may access information when necessary for support, security, or operating Reap.
Google and YouTube
Reap uses YouTube API Services. Google's handling of information is described in the Google Privacy Policy. Embedded YouTube videos may allow Google to receive technical information and use cookies or similar technologies when the player loads or you interact with it.
If an authorized church staff member connects a YouTube channel, Reap requests the youtube.force-ssl permission to support the church's video publishing. We access the connected channel's identifier and title, available playlists, and video metadata and upload status. We store the channel identity, an encrypted authorization token, and publishing records. Files and metadata you select for an upload, including a title, description, thumbnail, visibility, and playlist, are sent to YouTube to carry out that request.
This connection supports explicit church publishing actions. It does not give church staff access to personal Reap notes. We do not use Google or YouTube API data for advertising, sell that data, or use it to train generalized AI models. Reap's use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including its Limited Use requirements.
You can disconnect the channel in Church settings and revoke Reap's permission through your Google account security settings. Disconnecting removes Reap's saved channel authorization. Existing uploaded files and publishing history may remain in the church workspace; contact us to request deletion of stored Google or YouTube API data. We will process that deletion within 30 days, subject to legal requirements. Removing information from Reap does not delete videos or other information held by YouTube; manage those separately in YouTube.
Cookies, storage, and permissions
Reap and its authentication and hosting providers use cookies and similar storage for sign-in, security, preferences, and service operation. Your browser can restrict cookies, but doing so may prevent sign-in or other features from working. Device permissions, such as microphone access for optional mobile recording, can be managed in your device settings.
Retention, deletion, and your choices
Uploaded audio copies used for transcription have a 48-hour recovery window to support processing and retries when processing fails. Server copies become eligible for automatic deletion once they are older than 48 hours. Cleanup runs periodically, so deletion is not guaranteed at exactly 48 hours. The current cleanup applies to successful and failed uploads alike. This temporary storage is not a permanent audio backup.
This server cleanup does not delete your saved notes or transcripts, or recordings kept locally on your device. Completed church video uploads intended for YouTube are retained as church content and are separate from the temporary transcription-audio recovery window.
We retain account and saved content while needed to provide the service and retain operational records as needed for security, legal obligations, and resolving disputes. Deleted information may remain temporarily in backups or logs until those copies expire. We do not promise immediate removal from every backup.
You can edit or delete your notes, export content using available export tools, change your home church, and request account deletion. Account deletion is available in the mobile app's account settings. Church staff may need to transfer workspace responsibility before deleting the only staff account. Deleting a personal account does not delete shared church content or copies other people already received.
For access, correction, export, or deletion requests, or to exercise privacy rights available where you live, email jason@follo.dev. We may need to verify your identity before acting. Depending on your location, you may also have rights to object to or restrict processing, withdraw consent, or complain to your local data protection authority.
Security and international processing
We use access controls and other safeguards to protect information. No online service or device storage is completely secure. Reap is not end-to-end encrypted: our service providers process content to deliver the features described above. Information may be processed in countries other than where you live, including the United States, where privacy laws may differ.
Children
Reap is not directed to children under 13. If you believe a child under 13 has provided personal information, contact us so we can investigate and address it.
Policy changes and contact
We will update the effective date when this policy changes and provide additional notice for material changes when required. Contact Reap at jason@follo.dev with questions. Our Terms of Service describe use of the service.