Privacy is part of responsible learning design.
Effective date: 30 September 2026
Last reviewed: 30 September 2026
Dwyl.studio is still being built. That makes it especially important to separate what happens today from what we intend to put in place before real student or classroom data is processed.
This notice explains both.
It covers the public dwyl.studio website, our current interest form, privacy questions and requests, and the privacy principles guiding the future Dwyl learning product.
The responsible legal entity is DWYL STUDIO PTE. LTD, based in Singapore. As Dwyl expands into other countries, we will review and update the notice for the jurisdictions in which we operate.
On this page
What happens today
The current public website has a small data footprint.
The public website
We use Vercel to host the public website. We also use Vercel Analytics to understand how the public site is used.
We are deliberately not making claims here about the exact identifiers, cookies or local-storage behavior, retention periods, processing locations, or transfer arrangements used by Vercel Analytics because those provider and account details have not been verified closely enough for this notice.
The current interest form
The interest form has two routes: educator early access and school interest. Both ask for your name and email address. The school route also asks for your school or organisation. Both include an optional message.
Name and email are required on both routes, and the school or organisation is required on the school route. If a required field is left empty, the form cannot be submitted and we cannot add you to the interest list or send the related acknowledgement. The message can be left blank.
When you submit the form:
- your normalized email address, first and most recent subscription dates, submission count, and source are stored in Notion;
- your name, email address, the route you chose, your school or organisation if you gave one, and your message if you wrote one are sent to Dwyl by email through Google Workspace, which is also used to send you an acknowledgement.
We are collecting a small interest list while we are building with educators. We do not currently operate a separate marketing CRM or mass-newsletter platform for this list.
Future public contact forms
As the public contact experience expands, different enquiries may ask for limited additional context relevant to the reason for contacting us. We intend to keep those questions purpose-specific and optional where possible.
A privacy question should not require educator or school qualification information. Public forms should not be used to send student names, grades, submissions, parent reports, health information, or other sensitive student or family information unless a later, specifically designed process says otherwise.
Keep the processor list concrete.
For the current public website and interest flow, the services we can name confidently are:
- Vercel — public-site hosting;
- Vercel Analytics — public-site usage analytics;
- Notion — the current interest-list record;
- Google Workspace — acknowledgement and related Dwyl email.
These providers operate services across multiple regions and infrastructure environments. We do not currently publish a verified country-by-country processing-location list for the data described above, and we will not guess one.
As our data handling becomes more substantial, particularly before real student or school data is processed, we intend to review the relevant processor relationships, data locations, transfer arrangements, and public disclosures for the actual deployment.
State the current practice as it is.
Our current operating practice for the small public interest list is simple: we keep the interest-list information until you ask us to remove it.
If you ask to be removed, the current process is manual. We delete the subscriber record in Notion and the related subscriber correspondence in Google Workspace that contains your information.
That is the current public-site practice. It is not the retention model we intend to copy automatically into future student-data handling. Before real product or classroom data is processed, we intend to establish defined retention rules tied to the type of information, its purpose, the actual school relationship, and the applicable legal requirements.
For the current public interest form, submissions are handled server-side and validated before processing, with basic controls intended to reduce malformed or automated submissions. Email delivery to Google Workspace uses encrypted transport.
No online service is risk-free, and this notice does not make a blanket security guarantee.
Student privacy should be designed before it becomes operational.
The deployed Dwyl learning product does not currently have real external users. We therefore do not describe student submissions, grades, mastery records, private tutor conversations, parent reports, or similar learning information as current external-user processing.
Before schools or students use Dwyl with real learning data, these are the commitments guiding what we build:
- Purpose before collection.We will collect information because it serves a clear educational or operational purpose, not simply because it might be useful later.
- Data minimization.We will aim to collect the least information reasonably needed for that purpose.
- Educators remain in control of consequential educational decisions.Data and AI-supported signals should inform judgment, not silently replace it.
- Different kinds of student activity need different privacy boundaries.Ordinary project activity should not automatically be treated the same as more private student interactions. Any safeguarding exception should be separately defined and governed.
- Sensitive personal information will not be a routine personalization input.Health, disability, emotional context, family circumstances, and similar information should not become silent default variables simply because a system could infer or use them.
- Important information and representations should be understandable and challengeable.Students and educators should have ways to understand consequential information used about them and reach a human when something appears wrong or incomplete.
- Student and product data will have deliberate retention rules.We intend to define retention periods before external student use rather than defaulting to indefinite retention.
- Request and recourse routes will exist before external student use.Access, correction, challenge, and deletion or removal processes will be designed for the actual data and jurisdiction before they are needed at scale.
- Age and authorization rules will follow the jurisdiction and deployment.We intend to set country-specific account eligibility and any required parent, school, or other authorization before admitting real external users rather than using a blanket global age rule.
- School and Dwyl responsibilities will be made explicit.Before a school deployment, we intend to document the relevant roles, purposes, processors, access boundaries, and responsibilities for the actual relationship.
- The privacy notice will be updated before real student processing begins.The operational notice should describe the system that actually exists at that point, not an earlier product plan.
These are future product commitments. They should not be read as a claim that every process or technical control above is already implemented today.
For the broader principles behind these choices, read our responsible-AI principles. You can also see what this direction means for teachers and for schools.
Ask us directly.
Marc Tjoe Fat is the appointed Regional Data Protection Officer for DWYL STUDIO PTE. LTD. The data protection contact is:
That address is monitored for privacy questions and requests.
If you want to leave the current interest list, tell us which email address you used and ask to be removed. We currently handle that removal manually as described above.
If you ask to see or correct information we hold about you, please include enough information for us to identify you and understand the information or correction you are asking about. We may ask for additional information where reasonably needed to handle the request.
We do not state a universal deletion right or a single response deadline for every request or jurisdiction in this notice.
You can also ask a privacy question through our contact page.
Start with the jurisdiction we actually operate from.
DWYL STUDIO PTE. LTD is based in Singapore.
As Dwyl expands into other countries, we will review which additional laws, notices, age rules, school requirements, rights, and transfer arrangements apply to the actual service in those places. We do not treat a Singapore-focused notice as a permanent global privacy policy.
The notice should change when the product changes.
We will review this page when there is a material change to the information we collect, the purpose for collecting it, the processors we use, our retention or request-handling practices, our geographic scope, or the learning product's external-user status.
In particular, we intend to update this notice before real student or classroom data is processed.
When we update the notice, we will change the effective or last-reviewed date and, where appropriate, explain material changes clearly rather than silently rewriting the history.
For wider context, read our responsible-AI principles, learn more for teachers or for schools, ask us a question, or return to Dwyl.studio.
Change history
- 27 August 2026 — Initial public privacy notice drafted from the verified public-site inventory, with a clear separation between current website practice and future student/product privacy commitments.
- 30 September 2026 — Updated before first publication to describe the educator and school interest form, which asks for a name, an email address, a school or organisation on the school route, and an optional message.