Singapore's Personal Data Protection Act (PDPA) sets the foundation for protecting personal data while balancing the needs of business innovation and consumer trust. For B2B SaaS companies, onboarding is often the first real interaction with a new client—making it a critical touchpoint for both compliance and user experience.

Here’s how you can design an onboarding flow using Walla while aligning with PDPA requirements:

1. Clearly State the Purpose of Data Collection

Under PDPA, organizations must notify individuals of the purpose for which their data is being collected, used, or disclosed. Even in a B2B context where the primary user is a company, you’re still likely to collect personal data such as names, emails, and phone numbers of individual users.

Walla allows you to:

• Add a “purpose of collection” statement at the start of the form

• Customize tooltips or microcopy to clarify why each field is needed

• Maintain logs of user acknowledgements for audit readiness

2. Obtain Valid Consent—Explicit or Deemed

PDPA supports both explicit and deemed consent, but for high-trust onboarding experiences, explicit consent is preferred.

With Walla, you can:

• Include clear opt-in checkboxes with consent wording

• Offer language options if operating across multi-lingual teams

• Time-stamp and log consent as part of the user session

Remember: Consent must be voluntarily given and informed.

3. Minimize Data Collection

PDPA emphasizes data minimization. In your onboarding forms:

• Avoid requesting unnecessary personal data (e.g., ID numbers unless required)

• Use progressive disclosure to collect more only as needed

• Indicate which fields are optional vs. mandatory

Walla's dynamic form logic makes this easy to implement without sacrificing UX.

4. Provide Access to Data Protection Policies

Transparency is essential.

Ensure that your onboarding flow links to your:

• Privacy Policy

• Data Retention Policy

• PDPA contact or DPO (Data Protection Officer) email

You can embed these as hyperlinks or expandable sections directly within the Walla form.

5. Support Withdrawal of Consent and Data Access Requests

PDPA gives individuals the right to withdraw consent and request access to their data. While not all of this needs to be handled at the onboarding stage, setting up a system that makes it easy to manage these requests later is key.

Walla supports:

• Tracking who submitted what data

• Mapping form submissions to user IDs

• Triggering automated workflows to handle withdrawal or deletion

Conclusion

Compliance doesn’t have to compromise design. With Walla, B2B SaaS providers can craft an onboarding flow that is not only PDPA-aligned but also clean, reassuring, and efficient. By building transparency and control into the first user touchpoint, you’re not just meeting legal obligations—you’re building trust from the start.

https://home.walla.my