Every analytics tool wants a subscription. And your data. I built Twiligent instead. YouTube stats. Instagram stats. One dashboard. Runs locally on your machine.
export const meta = { title: 'Security', description: 'How member data is kept apart, and the settings an administrator must get right.' }
## What members can rely on
- Other members cannot see your accounts, scheduled posts or tracked content.
- Instagram access tokens are stored on the server and never sent to any browser, including yours.
- No member, including you, ever handles the instance's API keys.
## How isolation works
The browser signs in with Supabase and sends its token with every request. The Worker verifies the token and takes the member's ID from it, never from anything the browser sends. Every database query is limited to that ID. A scheduled post or tracked item can only use one of the member's own accounts: the Worker checks it, and the database refuses it too. Responses are stripped of access tokens before they leave the Worker.
## Administrator responsibilities
| Setting | Why it matters |
| --- | --- |
| All migrations applied | The publishable key ships in the website. The migrations turn row level security on and remove the browser's access to every table, so nobody can use that key to read or change the tables directly. |
| Secret key only in server secrets | It bypasses all database rules. Keep it in Worker secrets and GitHub Actions secrets only. |
| Signups | Supabase allows anyone with the address to sign up. Turn signups off for a private instance. |
| backend/.dev.vars never committed | It holds every secret for local development. |
| Instagram testers | In development mode, only people you add can connect Instagram. |
Applying the migrations is on the [Supabase](/docs/self-host/supabase) page.