Privacy Policy

Standfirst is a content tool that helps you draft marketing content from your own positioning and, when you choose, publish it to social accounts you connect. Standfirst is operated by Riley Wu, an individual developer. There is no separate company behind it. In this policy, “Standfirst”, “we” and “us” mean Riley Wu operating the Standfirst service.

Standfirst is currently in beta. This policy applies to the Standfirst website and app, including the public pages and the signed-in product.

We collect only what the product needs to work:

• Account information. Your name, email address and profile image. If you sign up with email and password, we store your password only as a one-way hash. If you sign in with Google, we receive your basic Google profile (name, email, profile image) and the sign-in tokens Google issues for that login.
• Organization and workspace information. The organizations and workspaces you create or join, your role in each (owner, editor or viewer), and workspace settings such as industries, selected social platforms and an optional webhook URL.
• Content you add or generate. Brand positioning, personas, competitor names and website addresses, competitor articles you add or ask us to fetch, keyword lists, generation instructions, drafts, image references and edits.
• Publishing and performance records. A record of each publish attempt (where it went, when, whether it succeeded) and any performance numbers you enter, such as views, clicks and engagements.
• Advertising and store data you choose to add. If you use the Ads area, the campaign, keyword, metric and order data you enter or import into a workspace.
• Connected social account data. When you connect a social account, the data described in section 4 below.
• Waitlist sign-ups. If you join the waitlist on our welcome page, your email address and the language you were viewing the page in.
• Your website and its audits. If you connect a website to a workspace, its address, the verification code you add to it, and the results of each audit you run. An audit reads your public pages the way a search engine does (our crawler is described at /bot) and stores, per page, its address, status, title, headings, word count, links, images and the issues found.
• Google Analytics data. If you connect Google Analytics to a workspace, we ask Google for read-only access to your Analytics data. We store the Google account email, the GA4 property you pick, and page view numbers per page and per day (page path, views, active users and sessions). We read these numbers only when someone in the workspace presses Sync now, and we use them only to show how your published pieces did on the Content impact page. We never change anything in your Google Analytics account.
• API keys. If you create a workspace API key, its name, scopes, the first characters of the key and when it was last used. We store only a one-way hash of the full key, never the key itself.
• Product usage events. We record actions inside Standfirst, such as “draft generated” or “policy saved”, with the account and workspace they belong to, counts, durations and outcomes. These events never contain your drafts, titles, prompts, keywords, names, email addresses, URLs or IP addresses, and they stay in our own database.
• Technical data. Our hosting provider keeps standard server logs (such as IP address, browser type, the page requested and the time) to run and secure the service. We also record how much AI usage each workspace consumes so we can keep costs under control.

Cookies and browser storage. We use a session cookie to keep you signed in, and your browser’s local storage to remember small preferences such as the language of the welcome page. We do not use advertising cookies, tracking pixels or third-party analytics.

We use your information to:

• provide the service: sign you in, keep your workspaces, generate and store drafts;
• publish content to the destinations you connect, only after you approve it;
• show you publishing history and the performance numbers you record;
• keep the service secure, prevent abuse and fix problems;
• contact you about your account, the waitlist or changes to these policies.

We do not use your content or connected-account data to build advertising profiles, and we do not sell it.

Standfirst lets you connect social accounts to a workspace, including Pinterest, Instagram, Threads, Facebook, LinkedIn, X and TikTok. You start each connection yourself, and the platform shows you exactly which permissions Standfirst asks for before you agree.

We use connected-account access for two things only:

• Publishing content you approve. Standfirst posts to a connected account only when a person with access to the workspace has reviewed and approved that specific post (for example, a Pin, a post, a video or a carousel). An AI draft is never published on its own, and an approval stops counting if the content changes afterward.
• Reading basic account information needed to publish. This means your account ID, display name or username, profile image and account type, plus the destinations you can post to, such as your Pinterest boards or the Facebook Pages and Instagram professional accounts you choose. For some platforms we also read the posting options the platform allows (for example, TikTok privacy settings) and the status of a post we just submitted, so we can confirm whether it went through.

What we store from a connection: the account ID and display name, the permissions granted, the access and refresh tokens (encrypted, see section 5), token expiry dates, the default destination you choose (such as a board or Page), and for each published post its ID and link on the platform.

What we do not do: we do not read your private messages, your followers or friends lists, or other people’s content; we do not post, like, comment, follow or delete anything on your behalf beyond the approved posts described above; and we do not use data from any platform for advertising, profiling or selling to anyone. If we ever want to add a new use, such as reading performance numbers for your own posts, we will update this policy first and ask you to approve any new permissions on the platform.

Our use of data received from each platform also follows that platform’s developer terms and policies.

• Access and refresh tokens for connected social accounts are encrypted with AES-256-GCM before they are saved to our database. The encryption key is kept separately from the database, in our hosting provider’s encrypted environment settings.
• Tokens are decrypted only on our servers, at the moment a token is needed to publish or refresh a connection. They are never sent to your browser, written to logs, or given to an AI model.
• Google Analytics access and refresh tokens are stored the same way, encrypted with AES-256-GCM, and are used only to read your Analytics data.
• Only workspace owners and editors can connect or disconnect an account. Viewers can see which accounts are connected but cannot use them.
• You can revoke access at any time, either by disconnecting the account in Standfirst or from the platform’s own settings for connected apps. See section 10.

All traffic to and from Standfirst uses HTTPS. No system is perfectly secure, but we take reasonable steps to protect your data and limit who and what can access it.

Standfirst uses Anthropic’s Claude API to generate and edit drafts. When you ask for a draft, or to shorten, extend or regenerate one, we send Anthropic the text needed for that request: your instruction, your workspace positioning and personas, relevant competitor notes and keywords, and the draft being edited.

We do not send account passwords, social account tokens or payment details to the AI model. Under Anthropic’s commercial terms for its API, Anthropic does not use this content to train its models. AI-generated drafts are suggestions: nothing is published until you approve it.

We share data with the following providers only as needed to run Standfirst. Each processes data on our behalf or, for social platforms, receives the content you choose to publish:

• Vercel: hosts the website and app and keeps server logs.
• Neon: hosts our Postgres database, where account and workspace data is stored.
• Anthropic: the Claude API that generates drafts (section 6).
• Firecrawl: fetches public competitor web pages when you ask us to scrape a competitor URL.
• SerpApi: returns public search-result data for keyword research when that feature is used.
• Google: if you choose Google sign-in.
• Google Analytics, only if you connect it: we read page view numbers from the GA4 property you pick, with read-only access.
• The social platforms you connect: Pinterest, Meta (Instagram, Threads, Facebook), LinkedIn, X and TikTok receive the content you approve for publishing and return basic account information (section 4).
• Your own webhook: if you set a webhook URL on a workspace, approved content is sent to that address. You control where it goes.

We may also disclose information if required by law, or to protect the safety and security of our users or the service.

• We do not sell or rent your personal information or your content.
• We do not share your data with advertisers or data brokers.
• We do not use advertising trackers, tracking pixels or third-party analytics on Standfirst.
• We do not use connected-account data for anything other than what section 4 says.

• Account and workspace data is kept while your account is active. When a workspace or organization is deleted, its content is deleted with it.
• Social account tokens are deleted as soon as you disconnect the account. If a platform tells us access was revoked, we stop using the tokens and delete them.
• Google Analytics tokens and numbers are deleted as soon as you disconnect Google Analytics: the tokens and every GA4 number we copied go together.
• Publishing records (post IDs, links, status and the numbers you entered) are kept with the workspace so you can see your history, and deleted with it.
• Waitlist emails are kept until we invite you or you ask us to remove yours.
• Server logs are kept for a limited period by our hosting provider and then deleted.
• Deleted data can remain in encrypted database backups for a limited period before those backups are overwritten.

To disconnect a social account: open your workspace settings in Standfirst, go to Connections, and choose Disconnect on that account. We delete its stored tokens straight away. You can also remove Standfirst from the connected-apps settings of the platform itself (for example, Pinterest, Facebook, Instagram, LinkedIn, X or TikTok), which revokes our access on the platform side.

To disconnect Google Analytics: open your workspace settings, find the Google Analytics card and choose Disconnect. We ask Google to revoke our access and delete the stored tokens and the GA4 numbers straight away. You can also remove Standfirst from the third-party access page of your Google Account.

To delete your data or your whole account: contact us using one of the options in section 15 and tell us the email address on your account. We will confirm the request comes from you, then delete your account, your workspaces and their content, and any connected-account data, within 30 days. Posts that were already published to a social platform live on that platform; you can delete them there.

You can also ask us for a copy of your data or to correct it, in the same way.

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal information, or to object to how we use it. We honor these requests for everyone, wherever you live. Contact us as described in section 15. We will not treat you differently for making a request.

Standfirst is not intended for anyone under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has given us personal information, contact us and we will delete it.

Standfirst is run from the United States, and our service providers may process data in the United States and other countries. By using Standfirst, you understand that your information may be processed outside the country where you live.

We may update this policy as Standfirst changes, for example when we add a new platform connection. We will change the effective date at the top of this page, and if a change is significant, we will let signed-in users know in the app or by email before it takes effect.

For privacy questions, data requests or to report a concern:

Email: rileywu19@gmail.com

You can also leave your email address through the form on our welcome page, and we will reach out to that address.