support and requests
Support & Requests
Support and request handling is still a draft private-beta operating process. Some intake mechanics may be implemented later.
Private beta draft. Last updated: June 14, 2026.
This page is practical private-beta copy for jmpseat. It is not legal advice, not final legal terms, and still needs founder/legal review before broad launch.
What this covers
- Account and access questions.
- Work-email verification issues.
- Privacy, deletion, or export requests.
- Moderation appeals.
- Safety, security, or aviation-sensitive content concerns.
Contact path
Use support@jmpseat.com once configured for private-beta support, account/access questions, verification questions, report follow-up, moderation appeals, and safety or aviation-sensitive concerns.
There is no in-app support form in the current product. Do not rely on support response timelines until they are separately approved and published.
Do not send passwords, portal credentials, employee numbers, confidential company documents, passenger information, exact crew hotel details, or security-sensitive information in support messages.
Deletion and export
Use privacy@jmpseat.com once configured for privacy, deletion, or export requests.
If a separate privacy inbox is not available, route the request through support@jmpseat.com with the subject prefix [Privacy Request], [Deletion Request], or [Export Request].
Deletion/export request handling is manual and may require founder/legal review before completion. There is no automated self-service deletion or export workflow in the current product.
Exports should exclude other users' private data, reporter identities, author user IDs, internal operator notes, proof artifacts, signed URLs, storage paths, and security-sensitive data unless legally required and reviewed.
Incident escalation
Safety, privacy, security, operator-access, or aviation-sensitive incidents should be escalated to the designated founder/operator owner and backup once those roles are finalized.