Privacy
Privacy policy
[REVIEW] Draft effective date: [PLACEHOLDER — effective date].
What Riby stores
Riby stores the information needed to operate your account and deliver pages. This includes request titles, gists, optional extended detail, answers, request status, and timestamps. It also includes agent metadata such as agent names, instance labels, and device identifiers.
When you link a channel, Riby stores the Telegram or Discord identity and linking records needed to deliver requests and accept answers from the right person.
Telegram and Discord
Riby sends pager-sized request content to the channels you connect. Telegram and Discord receive the agent name, request title, gist, answer controls, and resolution needed to render and update a page. Optional extended detail stays on the Riby dashboard.
[REVIEW] Telegram and Discord process data under their own terms and privacy policies. Their infrastructure may retain message and interaction data outside Riby's control.
Authentication and cookies
Clerk processes authentication for Riby. Clerk receives the account and sign-in information you provide and sets the session cookies needed to keep you signed in. Riby does not use those cookies for advertising.
Deletion
You may ask for deletion of your personal data. If you delete your account, Riby deactivates it immediately and schedules it for hard deletion after 30 days.
[REVIEW] Confirm whether de-identified resolved-request history remains after account deletion. The current product policy retains resolved-request history indefinitely.
A single-operator service
Riby is built and operated by one independent developer, Sivaram. That operator may access account or request data when needed to run, secure, or support the service.
No sale of data
Riby does not sell personal data. Riby does not share it for third-party advertising.