Memuat… / Loading…
Memuat… / Loading…
Builders (builders.swegrowth.id) and swegrowth OSS (oss.swegrowth.id) share one account and one set of data, so this policy covers both. Because making work visible is central to the service, this page plainly explains what is public, what stays private, and where your data goes.
You can sign up with email and password, with Google, or with GitHub. Authentication is handled by Supabase Auth; this app never stores your password in plain text. When you use Google, we only receive your name, email, and Google account ID under the permissions you grant. Your account email is used for sign-in and system notices and is never public unless you separately add it as a public email. When you use GitHub, we only receive your name, email, and GitHub username. If you tick “Show my GitHub activity” on your profile yourself, we also read your public pull requests and commit counts from GitHub every 30 minutes for the Activity page; untick it and that data is hidden at once, then deleted.
Other than your name, every field on /account/profile can be filled in or skipped: your GitHub account, profession, introduction, bio, skills, and contact links. Filled fields appear on your public profile.
Project links, names, descriptions, icons, highlights, problems, solutions, audiences, topics, stages, current work, journeys, open roles, logos, comments, boosts, and follows are public. Role applications and tasks taken or completed are also recorded so collaboration can work. Do not enter anything you would not want to be public.
Certain events are recorded automatically as they happen—for example, a project created, a stage changed, a role opened or filled, a task completed, a comment posted, a boost given, or an update posted. You can hide specific activity kinds from your public profile; hiding them does not delete the record.
Application decisions are sent as private notices to /inbox. When you import a public repository, we read its public metadata and README from GitHub to prefill the form. No private data is accessed, and the result is not stored until you save the project.
Feedback sent through /feedback is not stored by this site. The form only drafts a GitHub issue from what you typed and opens it in a new tab; nothing is sent until you press Submit on GitHub with your own account. That issue is public and governed by GitHub's privacy policy.
Your session is stored through cookies managed by Supabase Auth, plus a short-lived PKCE cookie during Google sign-in. This site also stores your ID/EN language choice. We do not use advertising or third-party analytics cookies.
Data is used to run the features you see: showing projects and profiles, matching people to roles, sending application notices, and building activity trails. It is not sold or used for targeted advertising.
Data is only shared with providers that run this site:
Data access is restricted directly in the database through Postgres row level security. Sensitive actions, such as deciding an application or moving a task, run through restricted database functions.
You can edit or clear profile fields, hide specific activity kinds, delete projects you own, and sign out. Account deletion is not yet self-service; to request deletion or ask about your data, email zikrulihsanmd@gmail.com.
This site is not directed at children under 13, and we do not knowingly collect their data.
Builders is under active development, so this policy may change with its features. The date below reflects the latest version.
Last updated: August 29, 2026.