Help and FAQs

RippleEnd lets you share a request through one public link, choose who can view selected private details, and set a deadline for access. Requests include items for sale, adult marriage introductions, blood donation, community donations, missing-person notices and Other requests.

Sign in, open Your requests and choose Create request. Save a private draft, review the public preview, then confirm publication. An eligible published request has a Share panel for copying or sharing its public link. Saving a draft does not publish it. You choose recipients and confirm sending in the destination app.

• Your requests (sign-in required)

While an available request is open, its category, public title, description and deadline can be seen by anyone with its link. Name, contact, address and optional custom fields kept in the private-details area require specific approval. Anything you type into a public title or description is public too. Share only information you are entitled to share, and keep unnecessary personal details out of public text.

Open the request’s management page from Your requests. Choose Complete when the request has been fulfilled, or Withdraw to end it for another reason, and confirm the consequence. Both actions are final. The public link shows a generic status instead of the original content, and viewers can no longer fetch private details. You can still see your own retained content in History.

The request expires at its displayed UTC deadline. New public reads show an Expired notice without the original content, and protected access stops. A viewer’s individual access may end earlier. Owners retain their own private history until they delete it. An already open page is not remotely erased; reopen or refresh the link to check its status.

No. You can change the deadline while a request is a private draft. After publication, its deadline cannot be extended or changed, and completed, withdrawn or expired requests cannot be reopened. Create a new request if needed. A lifted moderation restriction is different: an otherwise eligible request may become visible again, but its original deadline, closure and revoked access do not change.

Opening the RippleEnd link shows the request’s current status. Text and preview images already sent through other apps may still show an earlier version. RippleEnd cannot rewrite those messages or guarantee a cached preview refresh. Open the link before acting on or forwarding a request.

No. People can forward a public link or text they have received. Forwarding a link does not grant the recipient permission to view selected private fields: they still need their own approved access. Information copied into an external message is outside those access controls.

From an open public request, follow the access link, sign in with an email-confirmed account and select the available fields you need. The owner can approve some of those fields with an access deadline or deny the request. Check Access requests for the in-app decision; email notifications are not implemented. Approval is personal, can be revoked and never goes beyond the request deadline. A final decision cannot currently be resubmitted as a new access request for that same request.

• Access requests (sign-in required)

Yes. Ending access stops future access through RippleEnd. It cannot remove screenshots, copied text or information someone has already saved or shared. Preview cards in other apps may also show an older status. Share only the details needed, and carefully choose who can access them. Permission to view details does not automatically authorize republishing them.

Ending access stops future viewing through RippleEnd. It does not delete screenshots, copied text, downloaded information or messages someone has already saved or sent. Access ends at the deadline. Screenshots and saved copies are not deleted.

In Access requests, find the viewer’s approval and confirm Revoke access. This stops future viewing, not copies already held. To delete a published request’s content, open its management page and confirm Delete request content by typing DELETE. This removes its saved content and access records; its stable public link stays generically unavailable. Drafts have a separate confirmed deletion action. Independent reports, moderation decisions and appeals are not erased by deleting request content.

• Manage access
• Your request history

Deleting a request does not delete your account. Account and privacy provides an own-data download and a separate account-deletion procedure with recent password verification, authenticator verification for staff and explicit confirmation. Beginning deletion removes owned request content and access and stops ordinary account activity. Final identity deletion is a separate processing step; linked support, reporting, decision or audit records can keep it pending operator review. Pending is not completed deletion. Backup and retention procedures are still launch-readiness work, and neither procedure recalls external copies.

• Account and privacy (sign-in required)

For an available request, use Report a concern on its public page and sign in with a confirmed account. You can follow your own submitted reports from Account → Your safety reports. For questions, technical issues, feedback or privacy assistance, use Contact support and follow the conversation in the app. These options require sign-in; guest reporting is not available. Do not include passwords, verification codes, recovery links or unnecessary private information. This is not an emergency response service.

• Contact support (sign-in required)
• Your safety reports (sign-in required)

Revoke their access where available and report the concern through the available reporting or support options. Authorized staff can review submitted concerns and use the service’s restriction and appeal tools. This cannot guarantee a particular outcome or recovery or removal of copies held by other people or services. These practical limits do not remove RippleEnd’s applicable legal obligations.

Sign in and open Account → Account notices and appeals, or Request notices and appeals. Your private notice explains the decision and identifies the review process and offers one review request for that decision. In the solo beta, owner-led reconsideration means the operator may reconsider their own decision; it is not independent review. Existing independent appeals remain with a different authorized reviewer. No response time is promised. An account restriction does not remove your permitted access to existing records, support, reporting, privacy controls, appeals, closure/deletion or sign-out. Public unavailable pages do not disclose restriction reasons.

• Account notices and appeals
• Request notices and appeals