Contact Spark
Send a request through NevetsInc support and identify the product as Spark. Include the topic in your request so it can be understood: account help, privacy, safety, appeal, security, or technical issue.
See the Help Center for troubleshooting, Privacy Policy for data handling, and Terms for service rules. Learn about the operator at NevetsInc or see its other products.
What to include
- Your account reference, where relevant. Use the account associated with the request where possible.
- A clear description: what happened, what you expected, and the exact visible error.
- Date/time and time zone, plus the relevant message, group, or feature reference.
- Device and browser for technical issues, and steps you already tried.
- A requested outcome, such as account recovery, investigation, correction, or appeal review.
Do not include passwords, sign-in codes, authenticator secrets, recovery links, payment details, or unnecessary identity documents. Redact unrelated personal information from supporting material.
Safety reports and underage accounts
Use Report in a conversation where available and Block for unwanted contact. For concerns involving a group, status, call, underage user, or another feature, contact support directly.
Describe the account/content reference and relevant context. Do not download or forward abusive sexual imagery as evidence, and do not publish another person's sensitive information. Under-18s should involve a trusted adult when appropriate.
Read the Community guidelines. Response and enforcement depend on the facts; support is not a guarantee of continuous monitoring or personal protection.
Privacy and account-data requests
Label the request “Spark privacy request” and specify access, correction, erasure, restriction, portability, objection, or a question about processing.
Use Settings for available account export/deletion controls. Support can help with failures, legacy documents, retention questions, or a more specific request. Proportionate identity/authority verification may be needed; your password is not required.
GDPR requests must be answered without undue delay, normally within one month, with lawful extensions where applicable. See Privacy rights and timing. This does not promise removal of every recipient copy or backup in 30 days.
Moderation appeals
Include your account reference, the decision/date, and why you believe it should be reconsidered. Add relevant context without attacking the reporter or contacting someone who blocked you.
Appeals do not guarantee reinstatement. Support review does not replace any regulator, court, or other remedy available under applicable law.
Copyright and legal concerns
For content that infringes your rights, identify the work/right, the affected Spark content or account, your authority to act, a way to contact you, and the reason for the concern.
For formal legal requests, describe the requesting authority, legal basis, and precise scope. A request is assessed under applicable law; sending it does not guarantee disclosure of member information.
Security incidents and developer help
Label suspected unauthorized access or exposure “Spark security incident.” Give a minimal description of the affected feature and time. Avoid testing on someone else's account or extracting unrelated information. The published contact also appears in security.txt.
For public API questions, start with Developers and OpenAPI. Include the endpoint, timestamp, status code, and a redacted request example. Never include authentication secrets.
Response expectations
Response time depends on severity, request complexity, and available capacity. We do not promise 24/7 monitoring or a fixed turnaround for ordinary support. Applicable statutory deadlines remain in effect.
Keep your request reference for follow-up. If circumstances change, add the new relevant information. For immediate danger, contact emergency services rather than waiting for a support response.