Number security, privacy and responsible use
Message results, phone numbers and private API links may contain sensitive information. Safe use requires access control, limited data exposure, lawful authorization and compliance with the target service's terms.
1. Protect accounts and private URLs
Use a unique strong password and available account-security controls. Treat every API URL as a read credential, keep it server-side and never place it on an indexable public page.
- Use controlled staff access.
- Never send a full URL in a public group chat.
- Share exports only with authorized people.
- Remove access when a role or employment relationship changes.
2. Minimize collected and retained data
Collect only what the workflow needs and retain it only as long as necessary. Redact unrelated numbers, links and personal details from exports or support screenshots.
- Redact tokens and full URLs from logs.
- Do not send codes to unrelated analytics or marketing systems.
- Delete local exports when no longer needed.
- Explain data purpose and retention to customers.
3. Use only for lawful, authorized purposes
LFRelay supports legitimate business verification, product testing and customer support. Fraud, spam, harassment, impersonation, restriction evasion and unauthorized account access are prohibited.
- Confirm you are authorized to use the target account.
- Follow applicable privacy and communications law.
- Follow the target platform's terms.
- Report suspected abuse through the reporting page or support.
4. Respond to a security incident
If an account or URL may be exposed, stop the affected automation, record the necessary order and timing evidence, review access and contact LFRelay. Never send a password or full private token in a ticket.
- Stop the exposed task or URL calls.
- Record the order ID, time and observed behavior.
- Review account and staff access.
- Contact support@lfrelay.com.