What the first request needs
What you need to do, who would benefit, a preferred name and a safe email address. Group details, a useful first improvement, barriers and constraints are optional. The form has no attachment field and does not ask for case files, identity documents, account credentials, financial account details or proof of hardship.
Unfinished answers stay in the open page. They are not saved in browser storage or sent as draft records. The practice workspace uses fictional information and clears when the page is refreshed.
Who reviews it
Andrew reviews the first requests. Access is limited to explicitly designated Community Builds reviewers; a DRKNYT account alone does not grant access. The first opening has one request place and closes when that request is received or the invitation expires.
The pilot does not automatically send real applicant content to artificial intelligence services or put it in agent chats. General templates and product maintenance can be developed without using applicant records.
Your saved receipt
After a request is saved, we try to send a neutral confirmation to the safe reply address you chose. It includes your reference and confirmation of private review, with no request description, name, organization or account access link. You can reply to that email to continue the conversation. You do not need to keep the confirmation page open or copy a reference. A small optional download contains the same receipt information.
Resend processes that confirmation using the destination email address and receipt reference. Our private record tracks sending attempts separately from the request and any later human reply. A saved request remains saved if email confirmation is delayed or unavailable; the page reports that state. The designated reviewer must follow up on an unconfirmed receipt; retries are bounded and are not a background mail service. An email already handed to the delivery provider may still arrive after withdrawal or deletion. Resend says its standard email and log retention is 30 days, with backups persisting for seven days; earlier removal requires contacting the provider. See Resend’s data handling information. A DRKNYT account is optional and is not automatically connected to a request by matching an email address.
Connecting to your Profile is optional
You can choose to connect a saved request to your DRKNYT Profile. Its reference, broad status and last update then appear when you return through Profile, including after signing in on another browser. This view does not include your request description, contact details, reviewer notes or reply drafts. Connecting does not change who can review your request or grant access to any other product.
After a new save, a short-lived, secure browser cookie can support the connection you choose. It contains a private connection proof, not your answers, and expires within 30 minutes. The fast connection also requires your freshly verified Profile email to match the request’s safe reply address. Someone signing in with a different address on a shared browser cannot use that proof to see or connect the pending request.
For an earlier request, or a different Profile email, you can explicitly ask for a one-time code sent to the request’s original safe reply address. The reference is optional when that address identifies exactly one eligible request. A missing or ambiguous match receives the same neutral response and can use the private help route. Codes expire after 15 minutes, work once with the Profile that requested them and have a limit on attempts and new-code requests. These messages contain a reference and connection code, with no request description or access link. Asking for a code or opening a page does not connect the request.
Disconnecting removes the request from your Profile and ends that connection; the request and email conversation can continue. Withdrawal and deletion remain separate choices. Connection and recovery records are removed when request details are erased. Expired security and rate-limit records are due for removal within 48 hours through the private cleanup process; no automatic retention job is promised. Email already handed to the provider may arrive after a later disconnection.
A request is one permission
Permission to review the request and reply does not include marketing, public display, sponsor access, a testimonial, publication of a personal story or reuse of applicant material. Those would be separate, optional choices.
Any selected project needs a separate agreement covering the result, costs, data access, ownership, export, maintenance and support. Sending a request or discussing possible work does not reserve a funded place.
Correction, withdrawal and deletion
Email drknytlabs+communitybuilds@gmail.com from the safe address you used for your request to ask for a correction, withdrawal or deletion. Include your receipt reference if you have it. The reference helps find the request but is not proof of identity. No new account or government ID is required for that conversation.
Withdrawal stops consideration when processed. Deletion is a separate action: a status change alone does not erase request details. The reviewer must confirm removal from the request system and check known working or email copies through the established reply route, including confirmation records held by the sending provider.
Retention limits
Request and contact details, review notes and working email copies are due for deletion 30 calendar days after the review closes or 90 calendar days after receipt, whichever comes first. Waiting for a decision or agreeing to review later does not extend the 90-day limit.
A minimal restricted record of the reference, broad decision and action dates may be kept for up to 180 days from receipt. It excludes personal details, email addresses and request or review narratives. Only the necessary agreed brief and contact details would move to a selected project’s separately explained record.
Request records are stored with Supabase; neutral confirmations use Resend and service correspondence uses Gmail. Our Supabase Pro project has daily physical backups available for the last seven days. Removing an active record does not immediately remove earlier backup copies. Before restoring a backup, we must pause access and reapply recorded removals and expired-data handling before resuming review. See Supabase’s backup information.
Gmail messages in Trash can remain recoverable for 30 days. Our removal process includes matching service-owned mail and Trash copies. Google says its wider deletion process generally takes about two months and encrypted backup copies can remain for up to six months. These provider limits are separate from our active-record deadlines. See Gmail deletion information and Google’s retention policy.
The first invited review
We begin with one invited request. Any later expansion is a separate capacity decision, up to five reviews over fourteen days. Each received request has a named reviewer and a dated internal checkpoint. A withdrawal or deletion does not automatically create another place. Intake closes when receiving, reply, access or retention work cannot be covered.
There is no emergency coverage or promised response time. The purpose is private consideration and an honest next step.