How Maître stays within the lines
What Maître will not do on LinkedIn, who can publish, how page loads are budgeted, where sessions live, and how drafting and shared state are kept apart.
Maître never
Whatever the settings, the plan or the role, these stay off.
Likes, comments, connects or messages.
Rankings, intro paths and engagement suggestions are for you to act on by hand. Maître takes no social action on LinkedIn.
Calls LinkedIn’s API.
LinkedIn is driven through the browser only, with no OAuth. Selector rows from the database are data; nothing fetched from Supabase runs inside a LinkedIn page.
Holds your AI keys.
Drafting goes through engined on your computer, with the model you pick. Maître ships no provider SDKs and stores no provider API keys.
Maître always
Built into how Maître runs, not left to a setting.
Questions about how this works? Contact usWaits for an approval.
A post goes out only after someone with publish permission approved it. Recommendations and drafts are never a publish.
Stays inside 100 page loads a day.
Per account and UTC day: at most 40 for the crawl, and the last 10 kept for publishing. Your own sign in is not counted.
Keeps sessions on your computer.
LinkedIn cookies are decrypted only for the machine you chose for that account. This website never reads them, and staff access never extends to them.
Guards shared data with row level security.
Workspace state lives in Supabase behind row level security. Machines keep only local settings, keyring secrets and browser profiles.
Be first when Maître launches.
Leave your email and we'll tell you once, when it's ready: the download, pricing, and a setup that takes about three minutes.
Get early access