Share and submit forms create a private copy on the server and can send a review notice to the editorial inbox. Use a safe email only if follow-up is actually safe for you.
If you use share, submit, the resource feedback form, or the newsletter, the project stores the information you send so it can be reviewed. That includes the text you enter, the email address you choose to provide, and basic submission metadata such as time received.
Nothing from those forms publishes automatically. The first step is always private review.
The project does not ask for more than it needs. If a situation is active or unsafe, keep identifying details to the minimum required and use safer routes first.
- Stories, resource notes, and signups are stored privately for review.
- Email addresses are used for review or direct follow-up only.
- The project does not treat submissions as automatic permission to publish.
- If you need a correction or deletion request handled, use direct contact.
The resource feedback form stores the note you send about a listing, link, community, or support route so it can be reviewed before the directory changes. Use a safe email only if follow-up is actually safe for you.
The newsletter stores your email, optional name, and stated interests for manual review before anything is added. It is a small review queue, not an automated growth funnel.
Direct contact
Use contact when the request is administrative.
Corrections, deletion requests, and operational questions should go through direct contact rather than being buried inside a story submission. Resource recommendations and resource complaints should use the dedicated feedback form.