Privacy policy
This policy covers Conjur, the service at conjur-ai.com (“the service”), made and run by Pixelabra. Organizations use it to publish their own products' short videos, carousels and newsletters to the products' own accounts on YouTube, TikTok, Instagram and the other platforms below, after a person on their team approves each one, and to see how they perform. Anyone can create an organization; its owners invite the people who work in it. An organization's team may also send the holder of a product's account (for example a creator) a single-use link that lets them connect that one account; the service keeps only what this policy lists for the connected account, and the link's record (who sent it, when it was used, and the account's name).
Each product connects through its own platform apps (its own Google Cloud, TikTok and Meta apps), whose credentials are stored encrypted and used for that product only. What the service publishes is what the product's team uploads and approves. Nothing about the people who watch, follow or comment on a product's posts is used to make them, and the service reads nothing about them.
People who sign up and sign in
- What it stores: for each person in an organization, their email address, the name an owner gave them, their roles, who invited them and when they last signed in; for each sign-in link it emails, the address, the IP address that asked for it (to limit how many are sent) and when it was used; for each session, the address, how they signed in (an email link, or single sign-on with the identity provider they used), the browser's user agent, and when it started and was last used. Only a hash of each link and session token is kept. An organization's audit trail records who changed what in it, by email address.
- Signing up: the signup form asks for an organization name and an email address, and uses Cloudflare Turnstile to check that a person is filling it in. Sign-in and signup emails are sent through Cloudflare's email service.
- Cookies: one, the session cookie, set only when someone signs in. The public pages set no analytics or advertising cookies (see below).
- Who sees it: the organization's owners see its members and audit trail. Pixelabra's operators see each organization's name, plan and counts (of brands, members and the like), and nothing inside it without a role there.
Visitors to the public pages
The home page, the sign-in pages and this policy count visits with PostHog, in its cookieless mode, through conjur-ai.com itself: nothing is stored on your device, so there's no consent banner. It records the pages you open, what you click on them, the page and campaign that brought you, your browser and device type, and an approximate location from your IP address. PostHog tells visitors apart within a day by a one-way hash of the IP address and browser, without keeping a name or address. Nothing ties a visit to your email address, and a waitlist form's contents are never sent to PostHog: only that someone joined, and their answers to the three choices below.
The waitlist
If you join the waitlist, Conjur keeps your email address; your answers, if you give them (what describes you, how many products you market, what you'd hand over first, and a note); the page and campaign that brought you; when you joined; and a one-way hash of your IP address, to limit sign-ups from one place. Cloudflare Turnstile checks that a person filled in the form. Pixelabra uses these only to decide who to invite and to email you about access to Conjur, never shares them, and deletes them when you ask at contact@conjur-ai.com, within 7 days.
An organization's own tools
An organization can connect tools of its own, with its own keys: OpenRouter (AI that suggests ideas, drafts text and labels posts from their scripts, thumbnails and frames), fal (AI images and video), PostHog (its own product analytics, read as totals: how many sessions and conversions came from each post), Linear, GitHub, SerpApi and Resend (its newsletters). The service sends each tool only what that feature needs, under that tool's own terms with the organization, and through OpenRouter only to AI providers that don't keep prompts. It never sends one organization's data to another's tools.
YouTube
The service uses YouTube API Services. By connecting a channel, the channel's manager agrees to the YouTube Terms of Service, and Google's Privacy Policy applies to data held by Google.
- What it does: uploads the videos a person on the product's team has approved to the connected channel, and reads the view, like, comment and share counts of the videos it uploaded, and their aggregate analytics.
- Permissions:
youtube.upload(upload videos),youtube.readonly(read the connected channel and its videos' statistics) andyt-analytics.readonly(read aggregate analytics for the videos it uploaded: engaged views, average view duration and percentage, subscribers gained, shares, and the audience retention curve). - What it stores: the OAuth access and refresh tokens for the connected channel; the channel's name; for each video it uploaded, the video's id, link and privacy setting; and daily counts (views, likes, comments, shares) and the aggregate analytics above for those videos. Analytics are totals for a video, never about a viewer.
- What it does not do: it reads nothing about other channels, viewers, subscribers or comments' content, does not sell or share YouTube data, and does not use it for advertising.
Google Search Console
Where a product connects its own Search Console property, the service reads it with the read-only
webmasters.readonly permission, through the product's own Google app: search performance for the product's
own site (queries, pages, clicks, impressions, average position), to find pages that could serve searchers better.
It stores the OAuth tokens (encrypted) and the findings it draws from those totals; it reads nothing about individual
searchers, and Search Console doesn't provide any. Disconnecting deletes the tokens.
Google Ads
Where a product connects its own Google Ads account, the service reads it with the adwords permission,
through the product's own Google app and developer token. It reads each campaign's name, status, budget, and its daily
cost, impressions, clicks and conversions (by conversion action), to show what the product's advertising costs beside its
other results. The one change it makes in the account is a campaign's daily budget, when a person on the product's team asks for
it and, above the product's limit, an owner approves. It stores the OAuth tokens (encrypted), those daily totals, the
account's conversion actions and the budget changes asked for; Google Ads reports nothing about individual people to it.
Disconnecting deletes the tokens.
Meta and TikTok ads
Where a product connects its own Meta or TikTok ad account (through its own Meta app, with the ads_read and
ads_management permissions, or its own TikTok API for Business app), the service reads each campaign's name,
status, daily budget, and its daily spend, impressions, clicks and conversions by conversion action. The one change it
makes is a campaign's daily budget, as for Google Ads. It stores the access token (encrypted), those daily totals and the
budget changes asked for; neither platform reports anything about individual people to it. Disconnecting deletes the
token.
TikTok
Where a product's TikTok account is connected, the service uses TikTok's Login Kit and Content Posting API, under TikTok's Terms of Service. It stores the account's OAuth tokens and display name, the ids and links of the posts it made, and their daily counts. It reads nothing else.
Where a product's Instagram professional account is connected, the service uses the Instagram API with Instagram Login,
through the product's own Meta app, under Instagram's Terms of Use,
with the instagram_business_basic, instagram_business_content_publish and
instagram_business_manage_insights permissions. It publishes the product's approved Reels (as Trial Reels
where the product chooses) and reads each Reel's views, likes, comments and shares. It stores the account's token, user
id and username, the ids and links of the Reels it made, and their daily counts; it reads nothing about followers or
anyone else. Disconnecting deletes the token and the counts.
Facebook and Threads
Where a product connects its Facebook Page or Threads profile, the service uses the product's own Meta app: Facebook
Login with the pages_show_list, pages_manage_posts, pages_read_engagement and
read_insights permissions, under Meta's Terms of Service, and
the Threads API with threads_basic, threads_content_publish and
threads_manage_insights, under the Threads Terms of
Use. It publishes the product's approved posts as the Page or profile, and reads each post's views, reactions or
likes, comments or replies, and shares or reposts, and the follower count. It stores the Page's or profile's token, id
and name, the ids and links of the posts it made, and their daily counts. It doesn't keep the token of the person who
connected the Page, and reads nothing about followers or anyone else. Disconnecting deletes the token and the
counts.
Where a product connects its Pinterest account, the service uses the product's own Pinterest app, under
Pinterest's Terms of Service, with the
boards:read, boards:write, pins:read, pins:write and
user_accounts:read scopes. It lists the account's boards so a person on the product's team can choose where Pins go, creates
a Pin for each post a person on the team approved, and reads each Pin's views, reactions, comments and saves and the account's
follower count. It stores the account's tokens, id and username, the chosen board's id, the ids and links of the Pins it
made, and their daily counts. It reads nothing about followers or other people's boards and Pins. Disconnecting deletes
the tokens and the counts.
Bluesky, Telegram and Discord
A product can also connect its own Bluesky account (with an app password, under Bluesky's Terms of Service), its Telegram channel (through the product's own bot, under Telegram's Terms of Service) or a Discord channel (with a webhook, under Discord's Terms of Service). The service posts the product's approved posts there. It stores what it needs to post: Bluesky's session tokens (not the app password), the account's id and handle; the Telegram bot's token and the channel's id, name and username; the Discord webhook and its channel's ids. It reads each Bluesky post's likes, reposts and replies and the account's follower count, and the Telegram channel's subscriber count; nothing from Discord, and nothing about anyone's messages, followers or members. Disconnecting deletes what was stored and the counts.
Why the data is used
Only to publish each product's approved posts and to learn which kinds of posts do well, so that future posts are better. The counts are shown to the people in the product's organization and used by the planner that chooses what to make next. Pixelabra doesn't sell any of it, share it beyond the organization it belongs to, or use it for advertising.
Keeping and deleting it
- Data is kept while an account is connected. Counts are refreshed daily from the platforms, and every day the service checks that each connected account still authorizes it.
- Disconnecting an account in the service deletes its tokens and every count read with them, immediately, and revokes the YouTube token with Google.
- Anyone who manages a connected channel can also revoke the service's access at any time in their Google Account permissions (YouTube) or in TikTok's app settings. The service notices a revocation at its next daily check and then deletes that account's stored tokens and counts.
- On request to contact@conjur-ai.com, the stored tokens and counts for an account are deleted within 7 days, and so is what the service keeps about a person who signed up or was invited (their membership, sessions and sign-in links; the audit trail of an organization they acted in keeps their address).
Security
The service runs on Cloudflare Workers with a Neon Postgres database. Each product's platform app credentials are encrypted at rest, and so are an organization's own keys; every query is limited to one product or one organization; signing in takes an emailed single-use link or single sign-on, and each person sees only the products their roles cover; connections are encrypted in transit.
Contact
Questions, or requests to delete data: contact@conjur-ai.com.