Updated October 22, 2026
What should a first enquiry include?
General contact forms are for non-sensitive questions about a service or existing request. Do not include passports, Social Security or tax identifiers, bank credentials, full card details or private tax records in that first message.
When a service needs protected documents, use the specific intake or document-delivery workflow assigned for that service. If the channel is unclear, ask FormLLC to confirm it before sending the records.
How do you verify a payment request?
Check the service, amount, company or invoice reference and intended recipient against the agreed scope before continuing to a payment provider. Do not treat a payment link alone as proof that the work is authorized.
Never send an account password, one-time sign-in code or full card details in a support or referral message. Use an established contact route to ask about an unexpected request.
How do you protect account access?
Use a unique password, protect your email access and sign out on shared devices. Tell FormLLC if you suspect unauthorized account activity rather than sharing your credentials with someone offering to help.
Access, session and protected-document handling depend on the actual workflow. A statement about a website control is not a guarantee that every device, vendor or deployment is free of security risk.
Independent providers have their own controls
Payment processors, government agencies, professional advisers and other independent providers may process information under their own terms and security practices. Confirm the destination and review the relevant notice before supplying data.
Do not assume a general website privacy choice changes an external provider’s account, document or payment requirements.
How do you report a security concern safely?
Contact [email protected] or use the published contact page with the affected page, the type of concern and a non-sensitive description. Ask for the appropriate secure route if evidence contains protected information.
Do not email passwords, secret keys, full identity records, payment credentials or another customer’s documents as proof. Reporting a concern does not authorize access to accounts or intrusive testing.
Understand the limits of this guidance
No system can guarantee absolute security. This page does not assert a certification, audit result, uptime guarantee, fixed response time or universal encryption scope.
For a contractual security requirement, ask about the relevant service and the evidence needed before agreeing to that requirement. The Privacy Policy explains retention and information handling.