Fellowrise · Your information
Privacy policy
Draft prepared September 6, 2026
Private communities are not public directories. Members still share information with one another, and Fellowrise stores the information needed to run those communities.
On this page
1.What this policy covers
Fellowrise is operated by Kahvor, Inc., 115 E Main St Ste A1B-4V, Buford, GA 30518. This policy describes the Fellowrise website and invite-only community service, presented as Fellowrise by Kahvor. It covers community accounts, conversations, learning, events, private messages, and related support. It does not describe connected inbox or calendar features in other Kahvor products.
Community owners decide whom to invite and what to publish. A community may have additional rules. External websites, video providers, and payment services have their own privacy practices.
2.Information used by Fellowrise
- Account and access: email address, display name, account identifiers, community memberships and roles, invitations, and sign-in records.
- Profile: the picture, biography, location, and website you choose to provide. Your profile belongs to your account and may appear in more than one community you join.
- Contributions: posts, replies, pictures and files, links, polls and votes, reactions, follows, and the dates associated with those actions.
- Private messages: message text, sender and recipient identifiers, conversation membership, timestamps, and read-position information.
- Learning and events: course and lesson content, completion records, event information, RSVP choices, and recorded community activity.
- Operations: moderation reports, administrative changes, email delivery records, support communications, and security or error records. Requests also expose technical information such as an IP address to the infrastructure serving them.
- When you send product feedback, Fellowrise stores your message, category, account, community, and a general app page reference. Feedback is visible to the Fellowrise operator and staff the operator explicitly authorizes, not automatically to community administrators. The feedback form does not capture screenshots or page contents.
- Sign-in abuse prevention: derived identifiers based on your email address and IP address, together with request counts and timestamps.
3.How information is used
Fellowrise uses this information to deliver invitations and sign-in links, maintain community access, display content and profiles, deliver private messages, save progress and RSVPs, process member choices, prevent abuse, investigate problems, and respond to support or privacy requests.
Activity records support community counts and your own progress views. A stored action does not necessarily contribute to a score or public ranking.
4.Who can see what
- Active members of a community can see its published content and member profiles. A private room does not prevent another member from copying or sharing something they can view.
- The ordinary member directory does not display email addresses. Community owners and administrators can see member email addresses in member management.
- Community staff have role-based access to content, member management, drafts, or moderation tools. Community management does not provide a general inbox for reading every private conversation.
- Private messages are participant-scoped within the community. They are stored by Fellowrise and are not end-to-end encrypted. Do not use them to send passwords, full financial records, or highly sensitive documents.
- Hosting and delivery providers process information to operate the service. Platform operation and troubleshooting require infrastructure-level access; a private community is not a promise that its data is inaccessible to the service operator.
5.Services involved in delivery
- Cloudflare provides the application runtime, database, file storage, and the email delivery service used for invitations and sign-in links.
- OpenAI Sites provides the website hosting and deployment platform. This does not mean members need a ChatGPT account or that their content is automatically sent to an AI model.
- Stripe handles optional support checkout, payment details, and subscription management when you choose to contribute. The Fellowrise application does not collect your full card number through its own forms.
- YouTube receives requests when video thumbnails load. A supported embedded player loads after you select Play. Other resources and event links open the host’s chosen external service.
6.Draft review and in-app guidance
If you request draft feedback or ask the in-app guide a question, Fellowrise processes the text you submit and the relevant community context. The current beta uses application rules and matching against permitted community material; it does not send those requests to an external generative AI model.
Suggestions do not publish posts, contact people, change membership, or replace a person’s judgment. Future changes to this processing should be explained before they are introduced.
7.Retention and account removal
Our retention policy is to keep personal information only for as long as necessary to provide the service or meet legitimate legal and security needs. Any exception to removal should have a documented reason and be limited to the information needed for that purpose.
Leaving a community ends membership only. It does not delete your Fellowrise account, past posts, comments, messages, or uploads. Ask the team separately if you want particular information removed. Other memberships and optional support are unchanged.
Published posts and replies may remain visible after community membership ends unless separately removed. This is not a blanket retention rule for verified whole-account deletion.
For verified whole-account deletion, our reviewed approach is to remove your profile, avatar, owned uploads, original posts and comments, and sent-message content. This includes messages you previously sent in other members’ Fellowrise conversations, subject to specifically documented retention exceptions.
Preserve other members’ replies and messages using neutral placeholders such as “Former member”, “Post removed”, and “Message removed” where needed to keep a thread connected. Do not keep the departing member’s original content merely under a different name.
Review quotations, screenshots, attachments, and other retained contributions that may still identify the departing member. Preserve unrelated contributions while removing personal information where required; changing the author label alone is not anonymization.
Keep only specifically necessary billing, security, or dispute records privately. Document the retained information, reason, responsible handler, access restrictions, and retention period or review/removal criteria. Do not retain an entire account or conversation by default.
Fellowrise cannot promise to erase screenshots, downloads, or copies held outside its control. Provider backups and retained records require separate verification; a placeholder or completed review is not proof of erasure.
Every deletion request is reviewed by the Fellowrise operator during the private beta. Permanent erasure remains disabled while safeguards are completed. Submitting or closing a request does not delete data.
There is no self-service account-erasure or complete data-export tool in the current beta. Ask the team about access, correction, export, or deletion. Any response must account for identity verification, other people’s information, security, legal obligations, and the technical limits of retained records and backups.
Do not treat the expiry of a sign-in link or session as a promise that the corresponding database record is deleted. Unused uploads are eligible for cleanup, but this is not an exact deletion-time guarantee.
8.Your choices and questions
You can edit your profile, remove your profile picture, change an RSVP, and unfollow another member using the available account or community controls. Browser settings can remove local cookies, but that does not delete information stored by Fellowrise.
Privacy rights and available remedies depend on where you live and the laws that apply. Contact the team to discuss an access, correction, deletion, portability, objection, or other privacy request. Do not send identity documents or sensitive records in an initial email.