Send your supplier a link by email. They open it, answer a short PFAS questionnaire, and submit — no login, no account, nothing to install. Their answer lands on your product as a disclosure, and you can see who has opened the link and who hasn’t.
You ask a factory whether a component contains PFAS. The answer comes back three weeks later in a reply-all, in a format nobody can file, and the next person to need it starts the thread again.
A factory contact who fills in one form a year is not going to register for your compliance software, remember a password, or sit through an onboarding email. Ask them to and you get silence.
Without a record of who was asked and when, an unanswered request looks exactly like one that was never sent — which you find out when someone asks for the declaration you assumed you had.
Request a declaration against a specific product, or at company level when it covers everything they supply you.
Enter the supplier’s email, optionally name the product it covers, and add a note if you want. Aleph sends them a private link.
The link opens straight to the questionnaire. They say whether the item contains PFAS — yes, no, or they don’t know — and can decline if it isn’t something they can speak to.
The answer attaches to your product as a PFAS disclosure, where the rest of your compliance record already lives — not in an inbox.
If the supplier says PFAS is present, they have to name at least one component — what it is, which substance, the concentration in parts per million, and what it’s doing in the product. “Yes” on its own isn’t an accepted answer.
They can flag which states the item is sold into — California, Maine, New York, Washington, Colorado and Connecticut — so a declaration lines up with the state reporting duties that actually apply.
Every request shows where it stands: sent, opened, completed, declined or expired. You can copy the link to send it again yourself, or cancel a request you no longer need.
Links expire 30 days after they are sent, so an old link found in a forwarded email cannot be used to file an answer against your account.
This flow covers PFAS material disclosures — the question importers most often have to put to a factory, and the one that is hardest to get answered. It is not a general document portal, and it does not replace the certificates and test reports you upload against a product yourself. If a supplier answers “unknown,” that is recorded as unknown; Aleph does not turn a missing answer into a compliant one.