Respectful handling of public and controlled information.

Public inquiry information

The contact form collects the inquiry path, name, work email, optional phone, organization, service area, project stage, project or facility location, desired timing, preferred contact method, subject, message, and the time consent was given. Provide only information needed to evaluate the inquiry. Do not submit passwords, access codes, export-controlled data, medical information, or confidential files.

Purpose and access

Inquiry information is used to validate, route, evaluate, respond to, document, and protect the contact workflow. The application stores it in Supabase and limits queue access to authorized founders and employees through database permissions and Row Level Security. Submitting a form does not create a contractual relationship.

Service Finder accounts and business listings

Service Finder stores account preferences, business drafts, organization memberships, review decisions, and the recorded listing consent. A business submission includes a private explanation of the submitter's authority to represent the business. Authorized reviewers access submissions within their assigned scope; founder controls govern publication. Public listings contain the approved business name, summary, service tags, and general location label. Private contact details, account identifiers, authority explanations, and review notes are not published in the directory.

Saving a newer private draft does not replace the existing public listing. An authorized business owner or editor can withdraw a submission and its consent before publication, or remove that organization's public listing from their Service Finder workspace. This removes the submission from review or its public visibility; it does not delete the account, underlying draft, consent evidence, or audit history.

Service Finder requests

A service request records the selected business and service, the email address and description you provide, your sharing consent, and request status. By submitting, you authorize the selected business's currently authorized owners and editors to read those contact details and the request description in their website inbox. The request is also available in your own account. It is not added to the public directory or sent to the Pog platform.

You can cancel an open request in your account. After cancellation, the website hides its contact email and description from subsequent business inbox reads. Cancellation cannot recall information someone has already read or retained. This workflow stores requests in Supabase; it does not automatically send the business an email or text message. To ask about correction or deletion of Service Finder records, use the General inquiry path and provide the relevant account email or request reference without repeating sensitive details.

Pog community profiles and participation

The JR Pog community uses your JR website account. A community profile stores your chosen handle, display name, biography, and publication-consent record. Publishing is an explicit choice: your published profile fields may be visible to other people when the community is open. Public pages do not display your account email or authentication identifier.

Topic discussions are marked for either public readers or community members with a confirmed email and an active, published profile. Submitted comments enter moderation before appearing to the topic's permitted audience. Authorized moderators can review submissions and restrict content or participation. API priority votes are recorded against your account to limit duplicate voting; public views show aggregate counts, not voter email addresses or authentication identifiers. Unpublished or suspended profiles are excluded from those visible vote counts.

You can unpublish your profile from My community profile. This hides that profile and its contributions from public and member discussion views, while retaining the underlying records and moderation history. Your own account can still show your submitted comments. Unpublishing cannot recall copies someone has already retained. For correction or deletion requests, use the General inquiry path and identify your account or community handle without repeating private content.

The separately operated Pog platform at pog.space has its own account and access setup. Following its link does not transfer your JR password, sign you in there, or automatically publish your JR profile, comments, or votes to that platform.

Security and technical information

Vercel, Supabase, and related infrastructure may process ordinary request, device, browser, network, page, error, and security information needed to deliver and protect the site. The application uses a keyed, one-way hash of the request network address for short-window rate control and does not place the raw address in the inquiry record.

Maps-assisted service location

When the location-confirmation step is available and you choose map assistance, your browser sends only the address search or selected place information needed to display and confirm that service location to Google Maps Platform. Google may also receive ordinary browser, device, network, and request information under its own terms and privacy practices. We do not include your name, email, phone, organization, request narrative, attachments, portal information, investor data, employee data, or private visual-asset information in a Google Maps request.

Search text and unselected predictions are not stored by JR Corp. A location record is created only after you explicitly confirm it. That record contains the normalized service address, confirmation source and time, and—when map assistance was used—the minimum coordinates and place reference needed for confirmation and routing. Manual entry remains available when map configuration, browser support, coverage, or the provider is unavailable.

Retention and choices

Inquiry and audit records are kept only as long as reasonably needed for review, response, security, business records, dispute prevention, and applicable legal obligations. A confirmed service-location record is ordinarily deleted within 24 months of confirmation or earlier when it is no longer needed. Google-derived coordinates and place references are cleared no later than 30 days after confirmation. A documented legal, regulatory, dispute, or security hold may pause deletion only for the affected record and approved period. To correct, withdraw, delete, or ask about a submitted inquiry or location, use the General inquiry path and identify the original email and subject without repeating sensitive data.

Optional Service Finder map exploration

Service Finder's optional Google map is a separate exploration view from the Contact form's location-confirmation step. When you choose Google assistance and enter a place to search, the browser sends that query to Google Maps Platform. Google also receives the ordinary browser, device, network, and map requests needed to provide its service. The website does not automatically geocode business listings or send your private Service Finder request, account, or community content to Google.

The selected map label and coordinates remain only in this open exploration view and are discarded when it closes. JR does not save this query or position as a service location, business coordinate, or request record. Choosing a place on this map does not submit or confirm an address. You can continue searching the website directory without enabling Google map assistance.

Appearance preference

The white/black appearance switch saves only your selected appearance in this browser's local storage. It works without an account, is not sent to JR or a map provider, and can be reset by clearing this site's browser storage. If storage is unavailable, the switch still works for the current page. Appearance does not change account permissions.

Secure portals

Public website, community, Service Finder, employee, founder, and approved-investor accounts use Supabase Auth. The authentication service processes account email, password-verification information, recovery events, and session cookies needed to establish and maintain a secure session. The website passes submitted credentials to Supabase Auth for authentication; it does not store the plain-text account password in its application records. Auth confirmation and recovery emails use the email delivery provider configured for that Supabase project. Invitation redemption and controlled investor-document access will be added through separately permissioned workflows.

Access control

Employee and investor materials are intended for authenticated, authorized users. Public navigation to a portal entry, possession of valid credentials, or receipt of a recovery email does not by itself grant access. The application also verifies an active database membership on protected requests. Founder access additionally requires a match to the server-controlled founder allowlist.