Fictional manufacturing company. All services, equipment, and scenarios are demonstration content.
Fictional manufacturing company. All services, equipment, and scenarios are demonstration content.
Configure privacy before launch.
Configure privacy before launch.
Configure privacy before launch.
A configuration checklist for the site owner. This is not a published privacy policy.
A configuration checklist for the site owner. This is not a published privacy policy.
Start your RFQ
Match the policy to the service.
Match the policy to the service.
Match the policy to the service.
This template uses an in-memory mock RFQ and has no live receiving service. A production privacy notice must describe the real operator, purposes, recipients, retention and user rights for the actual setup.
This template uses an in-memory mock RFQ and has no live receiving service. A production privacy notice must describe the real operator, purposes, recipients, retention and user rights for the actual setup.
01 — Identify the operator and the data flow. Replace fictional company details with verified information. Decide which fields are necessary and where enquiries would be received before enabling any live form.
01 — Identify the operator and the data flow. Replace fictional company details with verified information. Decide which fields are necessary and where enquiries would be received before enabling any live form.
02 — Keep sensitive files out of this demo. File uploads are disabled. Do not enter real contact details, drawings, or confidential specifications. Use synthetic data and a .invalid address when testing the mock.
02 — Keep sensitive files out of this demo. File uploads are disabled. Do not enter real contact details, drawings, or confidential specifications. Use synthetic data and a .invalid address when testing the mock.
03 — Configure and verify a separate service. Replace RFQMock with a native Framer form or a suitable external form, then test its destination. Review provider access, retention and deletion. Add an accurate privacy-policy link after the owner reviews the configuration.
03 — Configure and verify a separate service. Replace RFQMock with a native Framer form or a suitable external form, then test its destination. Review provider access, retention and deletion. Add an accurate privacy-policy link after the owner reviews the configuration.
This setup checklist is not a privacy policy or a compliance guarantee. Live receiving, file handling and any analytics you add require separate configuration and validation. Keep the mock warning until you replace the demo with a tested service.
This setup checklist is not a privacy policy or a compliance guarantee. Live receiving, file handling and any analytics you add require separate configuration and validation. Keep the mock warning until you replace the demo with a tested service.