A: Hi iabokandil 🖖 Great questions - since you covered several topics, we’ll break our response into parts.

Branding 🙌

In Tier 4 you customize the entire signing experience - logo, header color, button colors, and accent UI colors. The signer sees your brand, not ours. Tier 3 includes only setting up a logo

Supporting CNAME

We don’t support CNAME in any tiers. However, after a document is signed, we do support automatic redirect to a specific URL via API. - Can you specify the use case you have in mind? we might find a solution to that.

Legality in Different countries

This is a great question. Legality depends on the law of the country where the business operates, not on the platform itself.

Signify follows the same legal frameworks that govern e-signatures globally:

⦁ ESIGN & UETA in the United States
⦁ eIDAS in the European Union

In most countries outside the US/EU, e-signatures are recognized as legally binding as long as:

⦁ both parties agree to sign electronically, and
⦁ there is a clear audit trail (we provide one automatically).

Signify records:
✔ signer identity
✔ timestamp
✔ IP address
✔ full activity log
✔ authentication data, depending on the method you chose

This record is called audit trail and it is what makes the signature enforceable in most jurisdictions.

Short version: If electronic signatures are legally recognized in the country, documents signed with Signify are legally binding.

We always recommend checking local regulations if a specific contract requires wet ink (for example: real estate deeds, wills, court documents in some jurisdictions).

ID Language

Yes, IDs in other languages are accepted. The system does not depend on the text language on the document — the signer simply uploads / shows the ID during the verification flow.

ID match with the selfie

Yes, the match is done system checks if the person has turned on the camera and recorded a short video showing their face and ID (matching + liveness detector). This matching process is automatic.