Privacy Policy

T1M LLC (“we”, “us”) operates Ravenpost, a tool that helps you schedule and publish content to Instagram, TikTok, X, Telegram, LinkedIn, Threads, Bluesky, YouTube and Pinterest, and send email to lists you keep with it. This policy explains what we collect, how we use it, and your choices.

T1M LLC is the data controller for the personal data described below. It is a limited liability company registered in Wyoming, United States (registration number 2026-001903276), with its principal office at 30 N Gould St #46732, Sheridan, WY 82801, United States. For the people on the email lists our customers keep with Ravenpost, we act for that customer instead, as their processor — see Email you send with Ravenpost below.

Information we collect

• Account data — your name, email, and profile image, and how you sign in: a password (held by Google's Firebase Authentication, which checks it when you sign in, only as a salted, slow hash — never the password itself), the Google or Apple account you linked (its account ID and email), and, for each device you are signed in on, the session, its rough location (country and city) and the kind of browser or app — shown back to you on your Account page so you can sign any of them out. The emails that confirm your address or reset your password are sent by Firebase, and each link in them works once.
• Connected social accounts — when you connect an account, page or channel on any supported platform, we receive that platform’s account ID, username, profile picture, and an access token (for Telegram, the channel id and our central bot’s token; for Discord, the webhook URL). We use these solely to publish content you create and to fetch analytics for your own accounts.
• Content you create — captions, media you upload, and scheduling details.
• Billing data — handled by Stripe, our merchant of record (or Polar, for subscriptions started before October 25, 2026), and by Apple or Google for a plan bought in the iPhone or Android app; we store only a customer/subscription reference — for an in-app purchase, the store’s subscription id and the plan bought — never card numbers.
• What you give the dashboard’s agent — your messages, the files you attach, and the links and notes you give it for brand memory, together with the public pages it reads from those links to write that memory.
• Where you came from — on your first visit, the page you landed on, the site that referred you and any campaign tags in the link are kept in your browser’s local storage and sent along with its requests to our API. When you sign up, they are passed on with your name, email and approximate location (the country, and sometimes the region and city, our network provider reports for your connection) to our team’s internal notification channel, so we can see which channels bring people to Ravenpost, together with how you signed up (email, Google or Apple). None of it is stored in our database.
• Email lists and campaigns — the contacts you upload or collect through your subscribe forms, the campaigns you write, and what happens to each message; see Email you send with Ravenpost below.
• Request logs — our servers log each request, including the ones an AI assistant makes for you: which operation, which workspace, a summary of its inputs, whether it succeeded and how long it took. They are used only to operate and secure the service.

How we use information

• To publish and schedule the posts you create, on your behalf.
• To show analytics for the accounts you connect.
• To operate, secure, and improve the service.

We never sell your data, never share it for advertising or lending, and never use your content — or any data we receive from a platform you connect — to develop or train generalized artificial intelligence or machine learning models.

Data sharing

We share data only with the processors needed to run the service: the API of each platform you choose to connect (Instagram, TikTok, X, Telegram, LinkedIn, Threads, Bluesky, YouTube and Pinterest), Google's Firebase Authentication (it holds what you sign in with — your email address and a hash of your password, or the Google or Apple account you choose — sends the emails that confirm your address or reset your password, and keeps no session of yours), Google and Apple (only if you choose to sign in with them), Stripe and Polar (billing and merchant of record), Apple and Google (plans bought in the app, which their stores sell and bill), Cloudflare (R2 media storage, and the network in front of our site and API), and Amazon Web Services (the servers Ravenpost runs on, the emails that tell you when a post could not be published or an account needs reconnecting, the email our customers send through our own sending and our product news, and the AI models behind the dashboard’s agent, which receive what you send the agent), and Telegram (our team’s internal alerts about sign-ups and subscriptions). Nothing is sent to a platform you have not connected. If you connect an email provider of your own, it receives the email you send through it.

Email you send with Ravenpost

Ravenpost’s email features let you keep a list of contacts and send them newsletters and announcements — through our own sending, which runs on Amazon SES in Ireland, or through an email provider you connect (Resend, Postmark, SendGrid, Mailgun or your own Amazon SES account). For the people on your lists, you are the controller and we are your processor: we handle their data only to provide these features, on your instructions, under our Data Processing Addendum. Our Acceptable Use Policy says what may be sent and how a list must be built.

For each contact we keep their email address, the name and fields you gave us, the lists and tags they are on, their subscription status, how and when they were added, and, for each campaign, whether the message was delivered, bounced or reported as spam, when it was first opened and clicked, and which links were clicked. Opens are counted with a tracking image and clicks by passing links through Amazon’s tracking address on their way to the page; on our own sending you can turn both off for a campaign. We do not store recipients’ IP addresses or device details.

When you send through a provider you connect, that provider receives the messages and the recipients’ addresses and handles them under your own agreement with it. We store its API key encrypted with AES-256-GCM.

If you received an email sent with Ravenpost

Businesses and creators use Ravenpost to email their own subscribers. The sender named in the email decides who receives it and is responsible for it; we send it on their behalf. Every such email has an unsubscribe link at its foot, and most mail apps show an Unsubscribe button beside the sender’s name: either takes you off that sender’s list. For anything else about how a sender got or uses your address, write to the sender — their name, and their postal address when they give one, are at the foot of every message — or to us at support@ravenpo.st, and we will pass your request on and help where we can.

If an address bounces permanently on our own sending, we keep the address and the receiving server’s reason on a list that stops any of our customers’ email from being sent to it again.

Product news from Ravenpost

We email the people who use Ravenpost about what is new — features, tips, changes to their plan. Every account receives it, as an existing customer, with no box to tick at sign-up; the sign-up page says so, and every one of these emails carries an unsubscribe link. You can also turn it off at any time in Settings, under Product news by email, and it stays off. For this list we are the controller. We keep your email address and name on it, with your plan, the month you signed up, and whether you use our phone app or have connected an AI assistant, so that what we send fits how you use Ravenpost. It is sent through Amazon SES, and it is deleted with your account.

AI assistants you connect

You can connect Ravenpost to an AI assistant — ChatGPT, Claude, or any other client that speaks the Model Context Protocol — and ask it to work with your account. When you do, that assistant’s provider receives what its requests read: your workspaces, the names of your connected accounts, your posts and captions, media links and analytics. What it sends back — a draft, a schedule, a post you tell it to publish — reaches us on your instruction. The provider handles that data under its own privacy policy. We receive only the requests themselves, never your conversation with the assistant.

You can end the connection at any time: disconnect Ravenpost in the assistant, or, for a connection made with a personal access token, revoke the token on the MCP page of your dashboard.

How we protect your data

Security procedures are in place to protect the confidentiality of your data, and we use encryption to protect it both in transit and at rest.

• Encryption in transit — every connection to Ravenpost, to our API, and onward to each platform’s API is served over HTTPS.
• Encryption at rest — every access and refresh token we hold, on every platform including YouTube, is encrypted with AES-256-GCM before it is written to our database. The encryption key lives in the server environment, never in the database and never in our source code, so a copy of the database on its own yields no usable credential. Uploaded media is stored in Cloudflare R2, which encrypts objects at rest.
• Credentials are never exposed — a stored platform token is never returned by our API, never sent to the browser, and never shown in our own internal administration tools. Personal API tokens are stored only as a SHA-256 hash; the plaintext is shown once, when it is created, and cannot be recovered afterwards.
• Access control — you sign in through Firebase Authentication, and the session that follows is ours: sessions are revocable at any time from your Account page, end when you reset your password, and are held as a hash on our side and an HttpOnly cookie (or your phone’s secure storage) on yours; assistants you connect get their own tokens, limited to Ravenpost’s MCP endpoint, which you can disconnect from the same page; and every request is re-checked against the workspace it addresses, so one customer’s data is not reachable from another customer’s session. Administrative access to production systems is limited to the people who operate the service.
• Least privilege — we request the narrowest permission scopes each platform offers for what the product actually does. On YouTube that is upload access plus read-only access to your own channel’s name and picture; we deliberately do not hold the broader channel-management scopes.
• Payment data — card details are entered directly with Stripe (or Polar and its payment processor), or with Apple or Google for a plan bought in the app, and never reach our servers.

Data retention & deletion

We keep data only as long as the service needs it.

• Connected accounts and their tokens — kept while the account is connected. Disconnecting it immediately deletes the token and the stored platform profile data, together with that account’s scheduled targets and analytics.
• Posts and uploaded media — kept until you delete them, or until your account is deleted.
• Analytics snapshots — deleted automatically 180 days after they are collected.
• Agent conversations — kept until you delete the conversation, or until your account is deleted. Brand memory is kept until you change it, or until your account is deleted.
• Email contacts and campaigns — kept until you delete them, or the workspace. The record of each message sent, which names the recipient’s address, is deleted 90 days after it was made; a subscribe-form sign-up that is never confirmed, after a week. An address that bounced permanently on our own sending stays on our suppression list, as described above.
• Product news — your place on the list is kept while you have an account; turning product news off is remembered with it.
• Request logs — kept for up to 14 days, then deleted automatically.
• Backups — our database is backed up nightly and each backup is kept for seven days, so deleted data leaves the backups within a week.
• Your account — to delete it and everything associated with it, email support@ravenpo.st and we will erase it within 30 days.

For Instagram and Threads we also honor Meta’s automatic deauthorize and data-deletion callbacks. See our Data Deletion page for all the ways to remove your data.

YouTube API Services

Our YouTube integration uses YouTube API Services. By connecting a YouTube channel you agree to the YouTube Terms of Service, and Google’s handling of any data it receives is governed by the Google Privacy Policy.

We use the API only to publish on your behalf. We read your channel’s name and picture once, when you connect it, so you can see which channel is linked, and we upload the videos you schedule to that channel with the title, description and privacy setting you chose. We hold no permission to change or delete anything on your channel: deleting a post in Ravenpost removes our own copy, and the video stays on YouTube until you remove it there yourself. We do not read, display or download anyone’s YouTube content, and we do not use the YouTube player.

From YouTube we store only your channel id, channel name, channel picture, an encrypted access token, and the id and link of each video we published for you. That data is protected by the measures described under How we protect your data above: the token is encrypted with AES-256-GCM at rest, it travels only over HTTPS, it is never returned by our API or shown in our administration tools, and no YouTube data is used for advertising or to train AI or machine learning models.

You can revoke our access at any time from Google’s security settings page. Disconnecting the channel in Ravenpost deletes everything listed above immediately; revoking access at Google stops us publishing, and disconnecting the channel (or emailing us) removes what we stored.

Cookies

We use strictly necessary cookies for authentication and session management. While you are signed in, your browser also keeps your name, email address and profile picture in its local storage, so that our public pages can show your account where they would otherwise offer a sign-in. It stays in your browser, and signing out deletes it.

We also measure our own Google advertising. When you reach the site from one of our Google ads, Google’s tag stores that ad click in a first-party cookie (_gcl_aw, 90 days) so that a later sign-up can be counted against the ad. It is used to measure our advertising, not for personalised ads or remarketing, and it is switched off by default for visitors in the EEA, the UK and Switzerland. You can opt out of Google’s ad measurement in your browser’s cookie settings or at Google’s Ads Settings.

We also measure how the site and the dashboard are used, with Google Analytics (through Firebase). It sets first-party cookies (_ga and _ga_6F2594M037, 2 years) to tell a returning visitor from a new one and to group page views into a visit, and it records which features are used — a post scheduled, an account connected — together with the network involved, but never the content: no caption, no media, no account name and no email address is sent to it. Google Analytics 4 does not store IP addresses. Like the advertising measurement, it is switched off by default for visitors in the EEA, the UK and Switzerland, where no cookie is written. You can opt out with Google’s browser add-on or by blocking cookies for this site.

Contact

Questions? Email support@ravenpo.st, or write to T1M LLC, 30 N Gould St #46732, Sheridan, WY 82801, United States.