Reporting Security Issues

Overview

SPRL takes security and abuse reports seriously. If you discover a potential security vulnerability, suspicious activity, abusive content, or a link that may violate SPRL policies, you can report it to the SPRL team for review.

Providing accurate information helps the appropriate team understand the issue and investigate it more efficiently.

Good to Know:
If you are reporting a suspicious or abusive SPRL link, include the complete URL and as much relevant information as possible. Do not include passwords, API keys, authentication codes, or other confidential credentials.

Report Abuse or Suspicious Activity

If you believe an SPRL link or service is being used for phishing, fraud, malicious activity, spam, or other abusive behavior, submit a report through the SPRL Report Abuse page.

Report an Issue:
Report Abuse & Suspicious Activity

What Should I Report?

You can report activity that appears to violate SPRL policies or presents a potential security or safety concern.

Phishing or credential-stealing pages.
Fraudulent or deceptive content.
Malware or malicious downloads.
Abusive or harmful content.
Spam or unwanted activity.
Suspicious SPRL short links.
Potential misuse of SPRL services.
Other activity that may violate applicable SPRL policies.

Reporting a Security Vulnerability

If you believe you have discovered a security vulnerability affecting SPRL, report it responsibly so that the SPRL team can investigate the issue.

Where possible, provide enough technical information to reproduce or understand the issue without exposing unnecessary personal information or confidential credentials.

Describe the vulnerability clearly.
Identify the affected page, endpoint, or component.
Provide steps to reproduce the issue where possible.
Explain the potential security impact.
Include relevant screenshots or technical information when useful.
Remove passwords, API keys, access tokens, and other secrets.

Security Reminder:
Never include passwords, API keys, access tokens, authentication codes, or other private credentials in a security report.

Information to Include in a Report

Information	What to Provide
URL	The complete SPRL URL or affected page where applicable.
Issue	A clear description of the suspicious activity or security issue.
Details	Relevant steps, behavior, or circumstances that help explain the issue.
Evidence	Screenshots or other relevant evidence where appropriate.
Impact	The potential security, safety, or policy impact when known.

Do Not Include Sensitive Information

Security and abuse reports should contain enough information to investigate the issue, but should not expose unrelated confidential information.

Passwords.
API keys.
Access tokens.
Authentication codes.
Private customer information that is not necessary for the report.
Other confidential credentials.

Important:
If sensitive credentials are accidentally exposed in a report, take appropriate steps to secure or replace the affected credentials immediately.

Abuse Reporting Process

When submitting a report, provide the relevant information through the SPRL Report Abuse page. The SPRL team can then review the submitted information and determine the appropriate action.

Identify the suspicious or abusive activity.
Collect the relevant URL and supporting information.
Submit the report through the SPRL Report Abuse page.
Provide additional information if requested.

Responsible Security Reporting

If you discover a security vulnerability, avoid publicly disclosing technical details before the issue has been reviewed and addressed where appropriate.

Responsible reporting gives the affected service an opportunity to investigate and address a potential vulnerability while reducing unnecessary risk to users.

Reporting Best Practices

Provide accurate information.
Include the complete affected URL where applicable.
Describe what you observed clearly.
Include reproducible steps for technical vulnerabilities.
Provide relevant evidence when appropriate.
Remove sensitive credentials before submitting your report.
Avoid publicly disclosing vulnerability details before appropriate review.

Reporting Checklist

Requirement	Status
Complete URL identified	Recommended
Issue clearly described	Required
Relevant evidence collected	Recommended
Steps to reproduce documented	Recommended for vulnerabilities
Potential impact explained	Recommended
Passwords and credentials removed	Required
Report submitted through the appropriate channel	Required

Frequently Asked Questions

Where can I report an abusive SPRL link?

Use the SPRL Report Abuse page to submit suspicious or abusive links for review.

Can I report phishing through SPRL?

Yes. Phishing and other suspicious activity involving SPRL links can be reported through the Report Abuse page.

What information should I provide?

Provide the affected URL, a clear description of the issue, relevant evidence, and any additional information that can help the SPRL team understand and investigate the report.

Can I include an API key in my report?

No. Never include API keys, passwords, access tokens, authentication codes, or other private credentials in a report.

Should I publicly disclose a security vulnerability?

Avoid publicly disclosing vulnerability details before the issue has been appropriately reported and reviewed.

Quick Reference

Report Type	Recommended Action
Phishing	Submit the suspicious URL through the SPRL Report Abuse page.
Fraud	Provide the affected URL and relevant supporting information.
Malicious Content	Report the URL and describe the suspected malicious activity.
Spam	Submit the relevant SPRL link or activity for review.
Security Vulnerability	Provide technical details and responsible disclosure information.
Credentials	Never include passwords, API keys, or authentication codes.

Report an Issue:
If you have identified suspicious, abusive, or potentially harmful activity involving SPRL, use the SPRL Report Abuse page .

Tip: A clear report containing the affected URL, a concise description, and relevant evidence can help the SPRL team investigate the issue more efficiently.

Security Overview
4 min read

Enable Two-Factor Authentication (2FA)
4 min read

Managing Login Sessions
3 min read

Password Security Best Practices
3 min read

Recognizing Phishing Attempts
5 min read

Data Privacy & User Information
4 min read