Send the useful version.
Use this page for corrections, source suggestions, privacy requests, partnership questions, or a building problem that belongs in the answer queue.
What to include
For a technical question, describe the expected result, the actual result, and the smallest set of collections, relationships, filters, or actions needed to reproduce the difference. Say whether you saw it in Preview, a published web app, or a native build, and whether refreshing or navigating changes the behavior.
For a correction, link to the Adalocado page and identify the exact claim that appears outdated or incomplete. Current official Adalo documentation, a dated forum discussion, or a reproducible counterexample is especially helpful. A correction can be reviewed without publishing the submitter’s identity.
For a privacy request, include the same email address only if it was supplied with the original question. Do not send passwords, API keys, private app data, authentication tokens, or production user records.
What happens next
Submissions enter the editorial queue. They are used to identify missing answers, review reported errors, and decide which legacy walkthroughs deserve a current written resource. Submission does not create an account, a paid support relationship, or a guaranteed response time.
Adalocado is independent and is not affiliated with Adalo. Product billing, account access, outages, and platform-specific support requests should go to Adalo through its official channels. This site can explain public workflows and evidence, but it cannot access another company’s systems or a visitor’s private app.
Before submitting, you can also search all answers, review the editorial policy, or read the privacy notice.
One form, routed by context.
Start the message with “Correction,” “Privacy,” “Partnership,” or the feature you are trying to build. Email is optional unless you need a direct reply or need us to locate a prior submission.