Just a moment...
Frequently asked questions about account and platform security.
This article answers frequently asked questions about account and platform security when using SPRL. It covers account protection, passwords, two-factor authentication, login sessions, phishing, API security, domain security, privacy, and reporting security issues.
Following these security practices can help protect your SPRL account, integrations, branded domains, and business information from unauthorized access and misuse.
Use a strong and unique password, enable two-factor authentication where available, keep your credentials confidential, and regularly review your account security and login sessions.
No. Your password should remain confidential. Avoid sharing account credentials with other users or employees.
Change your password immediately, review your active login sessions, sign out of unfamiliar sessions where possible, review your security settings, and contact SPRL Support if you suspect unauthorized access.
No. Your SPRL password should be unique and should not be reused on other websites or services.
Two-factor authentication (2FA) adds an additional verification step to your account login process. It provides an additional layer of protection beyond your password.
Yes. Enabling two-factor authentication where available is recommended, particularly for accounts with administrative responsibilities or access to important business resources.
No. Authentication codes should always remain confidential. Never provide an authentication code to another person or enter it into a suspicious website.
Do not approve the request or provide any authentication information. Review your account security and contact SPRL Support if you suspect unauthorized access.
A login session is authenticated access established after you sign in to your SPRL account from a browser, device, or supported application.
Reviewing active sessions can help you identify old, unused, or unfamiliar access to your account.
If you cannot identify the session, secure your account, review your credentials and security settings, and sign out of the session where possible. Contact SPRL Support if you suspect unauthorized access.
Secure your account as soon as possible, review your active sessions, sign out of the affected session where possible, and change your password if you believe your credentials may have been exposed.
A strong password should be long, unique, difficult to guess, and free from predictable personal information or commonly used patterns.
A reputable password manager can help generate, store, and manage unique passwords for different services.
Change your password when you believe it has been exposed or compromised, when you have entered it into a suspicious website, or when there is another reason to believe your credentials may no longer be secure.
No. Never send your password or authentication codes through support requests, email, chat, screenshots, or other communication channels.
Phishing is an attempt to deceive users into revealing sensitive information, visiting malicious websites, downloading harmful content, or performing an action that benefits an attacker.
Be cautious of unexpected messages, urgent requests, suspicious website addresses, requests for passwords or authentication codes, unexpected attachments, and unusual payment or account-verification requests.
No. HTTPS encrypts communication between your browser and the website, but it does not guarantee that the website itself is legitimate or trustworthy. Always verify the domain and context.
Close the page and avoid entering additional information. If you entered your SPRL credentials, change your password immediately and review your active login sessions.
Change your SPRL password immediately, use a new unique password, review active login sessions, and check your account for unusual activity.
Treat API keys and other authentication credentials as confidential information. Store them securely and restrict access to authorized applications and users.
Private API credentials should not be exposed in browser-side code because users may be able to inspect the application and retrieve the credential.
No. Never commit private API credentials to public repositories. If a credential has been exposed, treat it as compromised and replace or deactivate it where applicable.
No. Passwords, API keys, access tokens, and authorization headers should not be stored in application logs.
Secure or replace the affected credential where applicable, review API activity, investigate unexpected requests, and contact SPRL Support if assistance is required.
Yes. SSL activation is part of the custom domain setup process after successful domain verification.
No. Manual certificate installation is not normally required for SPRL-managed custom domain SSL activation.
DNS changes may still be propagating, or SPRL may not yet be able to detect the required DNS configuration.
No. HTTPS secures the connection to the branded domain but does not guarantee that the destination website is safe or legitimate.
Yes. Dedicated subdomains such as go.example.com or links.example.com can be used for branded links.
Personal information generally refers to information that can identify, relate to, describe, or reasonably be associated with an individual.
The information processed through SPRL depends on how the platform is used. It may include account information, contact information, campaign data, form submissions, link-related information, and other information provided through supported services.
No. Collect only information that is necessary for your intended business purpose and follow applicable privacy and data protection requirements.
It is strongly recommended to avoid placing unnecessary personal or confidential information in URLs. URLs may appear in browser history, analytics, logs, referrer information, screenshots, emails, and other systems.
Customers are responsible for ensuring that their collection and processing of personal information complies with applicable privacy and data protection requirements.
You can report suspicious or abusive SPRL links through the SPRL Report Abuse page.
You can report phishing, fraudulent content, malicious activity, spam, suspicious SPRL links, potential security vulnerabilities, or other activity that may violate SPRL policies.
Include the affected URL, a clear description of the issue, relevant evidence, steps to reproduce a technical issue where applicable, and information about the potential impact.
No. Never include passwords, API keys, access tokens, authentication codes, or other confidential credentials in a security or abuse report.
Secure the account immediately by changing your password, reviewing active login sessions, checking two-factor authentication settings, and investigating unusual activity.
Secure or replace the affected credential where applicable and review recent API activity for unexpected requests or changes.
Secure your domain or DNS provider account immediately, review recent DNS changes, enable available security controls such as two-factor authentication, and verify that your SPRL DNS configuration remains correct.
| Security Area | Recommended Practice |
|---|---|
| Password | Use a strong and unique password. |
| 2FA | Enable two-factor authentication where available. |
| Sessions | Review active login sessions periodically. |
| Phishing | Verify suspicious messages and website addresses before taking action. |
| API | Keep API credentials private and securely stored. |
| SSL | Use HTTPS for branded links. |
| Privacy | Collect and process only necessary personal information. |
| Reporting | Report suspicious or abusive activity promptly. |
| Security Practice | Status |
|---|---|
| Strong and unique password configured | Recommended |
| Two-factor authentication enabled where available | Recommended |
| Login sessions reviewed periodically | Recommended |
| API credentials protected | Required if using API |
| Branded domains configured with HTTPS | Recommended |
| Personal information collected appropriately | Required if applicable |
| Suspicious activity reported | Required if applicable |
Our support team is always happy to assist you.
We use cookies to improve your experience, analyse traffic, and personalise content. By clicking “Accept”, you consent to the use of cookies as described in our Cookie Policy .
Accept cookies Read our Cookie Policy
