Local task information.
Alder stores current requests and plans in its local data directory. A limited history can include plans, outcomes, test observations and changed paths for a place. You can edit or clear the project note used for later tasks.
Your project deserves careful handling.
These notes describe the current preview design. They will be updated before public access and are separate from a model provider's own terms.
Only the context needed for a request.
When you ask a selected provider for a plan or explanation, Alder sends the request and bounded context. That can include DataModel paths, script names, selected objects when Studio exposes them, play state, recent Output and a project note. The initial map does not read script source or screenshots. Later approved actions may request more project detail.
The selected provider processes the request under its own account settings, retention policy and terms. Separate provider charges may apply depending on the access route. Clearing local history cannot retract information already sent to a provider.
Studio sign-in stays in Studio.
Alder does not ask you to paste a Roblox password or session cookie. It does not automatically publish an experience, upload project files to a hosting service or spend Robux.
These are product notes for a waitlist-stage app, not a final formal privacy policy. Contact and formal policy details will be published before public access.
Only an address for access news.
If you join the waitlist, Alder stores your email address, the signup source and the time you joined in the same Supabase project used by the app. We use it to send Alder access news, and do not make the list publicly readable. Joining does not create an app account. No payment information is collected by the waitlist form.
We have not started sending waitlist emails. Any waitlist email we send will include a way to stop receiving them. The signup form gives the same confirmation whether an address was already on the list.