Security
Security and data handling
Last updated: November 19, 2026
This is an English translation for convenience. If there is any discrepancy, the Japanese version prevails.
A social media tool posts to accounts that matter to you. You should know what permissions you are handing over, what is stored, and when it is deleted. This page explains, as concretely as we can, how Ritomira is actually built. The legally binding terms are in the Privacy Policy. This page explains them in plain language; if the two ever differ, the Privacy Policy takes precedence.
The short version
- We never hold your passwords. Neither signing in to Ritomira nor connecting a social account uses a password.
- Two-factor authentication (authenticator app) is available. We strongly recommend turning it on.
- We post only through each network's official API. We never use unofficial methods such as automating the website.
- The keys used to access your social accounts (access tokens) are stored encrypted.
- Your data is stored in Japan (Tokyo).
- We define what is deleted and what is kept when you disconnect an account or close your account. Data is deleted within 30 days of a closure request.
- When an AI operates your account (MCP), you choose which permissions to grant. Only “read” is on by default, and actions that cannot be undone, such as replies and follows, are approved by a person on a confirmation screen, not by the AI.
Signing in to Ritomira
There are only two ways to sign in to Ritomira.
| Method | How it works |
|---|---|
| Email address | Each time you sign in, you enter a one-time code sent to your email. There is no password |
| You confirm with your Google account (OAuth). Ritomira never receives your Google password |
Password sign-in is not just missing from the screen; our servers refuse it. Because we do not hold passwords, no password can leak from Ritomira.
Sign-in is also protected by the following.
- Verified email only: accounts whose email address has not been verified cannot be used.
- Session storage: your signed-in session is kept in a cookie that scripts on the page cannot read (HttpOnly).
- Rate limits: sign-in actions cannot be retried many times in a short period, and repeated failures are monitored.
- Confirmation before closing your account: you must have signed in again within the last 10 minutes. This prevents someone from closing your account from a screen you left open.
Social accounts such as X and Instagram are connected after you sign in, as places to post. You cannot sign in to Ritomira with a social account.
Turn on two-factor authentication
Ritomira posts to your connected social accounts and can be operated by AI. If someone gets into your email, they could use the code we send to sign in to Ritomira as well. With two-factor authentication, they still cannot sign in without your phone, even if your email is compromised. We especially recommend it for business accounts and team owners.
How to set it up (after signing in)
- Install an authenticator app on your phone (an app that shows a 6-digit code that changes every 30 seconds, such as Google Authenticator or Microsoft Authenticator).
- Sign in to Ritomira and open “Account & security” in Settings.
- Under “Two-factor authentication”, choose “Set up authenticator app” and scan the QR code with your app. If you cannot scan it, you can type in the code shown instead.
- Enter the 6-digit code shown in the app to confirm.
Once set up, you are signed out of all other browsers. From then on, you sign in with your email code (or Google) plus the code from your authenticator app. The app code is required when signing in with Google too.
Also worth checking
- On the same screen, “Signed-in browsers” shows where you are signed in. If you see anything you do not recognize, choose “Sign out of all other browsers”. Ritomira also leaves a notification each time there is a new sign-in.
- Before changing phones, turn two-factor authentication off on this screen and set it up again on the new phone.
- If you lose your phone and can no longer use the app, you cannot turn it off yourself. Please reach us via Contact and we will verify your identity.
Permissions we request when you connect a social account
Social accounts are connected only through each network's official authorization (OAuth). You never enter a social media password into Ritomira. When you connect, the network shows you the permissions Ritomira is asking for. Here is what each one is used for.
X
| Permission | Used for |
|---|---|
| Read posts (tweet.read) | Import your past posts and metrics for analysis |
| Post (tweet.write) | Send scheduled posts and replies |
| Read profile (users.read) | Show the connected account's name and picture |
| Upload media (media.write) | Attach images and videos to posts |
| Follow (follows.write) | Follow accounts from the app or via AI (only when you do it) |
| Stay connected (offline.access) | Send scheduled posts while you are not using the app |
We do not request permission for X direct messages (DMs). We can neither read nor send your DMs.
| Permission | Used for |
|---|---|
| Basic info (instagram_business_basic) | Import the account's name, picture and posts |
| Publish (instagram_business_content_publish) | Send scheduled posts |
| Comments (instagram_business_manage_comments) | List comments and reply to them |
| Messages (instagram_business_manage_messages) | The DM auto-reply feature (see below) |
| Insights (instagram_business_manage_insights) | Analyze post and account metrics |
On Instagram, we do request DM permission. It is used by the “DM auto-reply” feature on paid plans to read incoming DMs and reply under conditions you set.
- Automatic replies are sent only when a message matches a rule you created and turned on.
- When AI suggests a DM reply, it only creates a draft. A person decides whether to send it.
- Records of automatic sends are deleted automatically 180 days after they are created.
You can also connect Instagram through a Facebook account. In that case, Facebook shows the equivalent Facebook permissions (page list, publishing, comments, insights and so on) for the same purposes.
Threads
We request permissions to read and publish posts, view metrics (insights), delete posts, read and manage replies and mentions, search keywords, look up profiles, and tag locations. There is no DM permission.
Facebook Pages
We request permissions to list your Pages, read Page posts and metrics, and publish to Pages. We do not request Messenger permissions.
How we store access tokens
When you connect a social account, the network gives Ritomira a key called an access token. Because it lets Ritomira post to that account, we treat it as carefully as a password.
- Stored encrypted. Tokens are encrypted with standard encryption (AES) before they are written to the database. The encryption key is managed separately from the database.
- Never stored unencrypted. If something is wrong with encryption, we stop rather than save the token unencrypted.
- Checked at startup. When our servers start, they check that the encryption key is valid and is not reused for any other purpose, and refuse to start if it is not.
- Unreadable tokens are never used. If a token cannot be read for any reason, we do not force it; we ask you to reconnect.
Where data is stored, and who processes it
Your data is stored in a database in Japan (Tokyo) run on Supabase. The database uses row-level security (RLS) so that one user's rows cannot be read by another.
The website and server processing run in Vercel's and Railway's Singapore locations. We also use outside providers for payments, email, AI and so on. Their names, countries and the information shared with each are listed in the processors table of the Privacy Policy.
Payments
Payments are handled by Stripe. Your card number goes directly to Stripe; Ritomira neither receives nor stores it.
Data sent to AI providers
Analysis, writing assistance, image and audio creation, and the AI agent send content such as post text, notes and your conversations with the AI to AI providers. Only what is needed for the feature you are using is sent.
- Anthropic (Claude): data received is, as a rule, deleted within 30 days and is not used to train AI models without our consent.
- Cohere: used to convert text into numbers so that your posts and notes can be searched.
- Google (Gemini): when you create images or audio, we send the text used to create them and the character images you chose (only when you use these features).
- Tavily, Jina AI: when the AI agent searches the web, we send the search terms and the URLs of the pages it reads (only when you use this feature).
When AI operates Ritomira (MCP)
AI apps such as Claude and ChatGPT can read your Ritomira analytics and create scheduled posts (MCP). Because this hands your account to an AI, it is protected as follows.
How you connect
You approve an AI app on an OAuth consent screen. You never type your Ritomira credentials into the AI app, and we do not issue API keys.
You choose the permissions
There are six permissions, and only “read” is on by default. The others work only after you turn them on in settings.
| Permission | What it allows |
|---|---|
| Read | Read posts, metrics and analysis |
| Draft | Create drafts |
| Schedule | Create and change scheduled posts |
| Publish articles | Publish X articles |
| X actions | Reply and follow on X |
| Meta actions | Reply to comments on Instagram and other Meta networks |
A person approves actions that cannot be undone
Replies and follows on X, replies to comments on Instagram and other Meta networks, and publishing X articles reach other people immediately and cannot be undone. These are approved by a person, not by the AI.
- Before sending, we show a confirmation screen in the AI app. You are the one who presses the button.
- AI apps that cannot show a confirmation screen cannot perform these actions (they can still read and prepare).
- We never send anything different from what was shown on the confirmation screen.
This ensures that even if instructions aimed at the AI are hidden in someone else's comment, nothing is sent without a person seeing it.
Disconnect at any time
In Settings you can see the connected AI apps and disconnect them. A disconnected app stops working from its next request, and reconnecting asks for your consent again. Turning a permission off also takes effect immediately.
Using teams
In a team, each member has a role: owner, admin, editor or writer.
- Writers can only create drafts; posting requires approval from an editor or above.
- Actions that cannot be undone, such as deletions, require admin or above.
- Only owners and admins can add or change members.
- Team activity is recorded in a log.
Disconnecting and closing your account
When you disconnect a social account
- The access token is deleted. From then on, Ritomira cannot post to that account.
- Imported posts, analysis and notes are kept. If you reconnect, you can pick up where you left off.
- If there are scheduled posts that have not been sent yet, please cancel them before disconnecting. This prevents scheduled posts from silently never going out.
- To disconnect X, use X's own settings (“Connected apps”).
- For Instagram and Threads, when you disconnect or request deletion on Meta's side, Ritomira receives a notification and deletes that account's data.
When you close your account
- Your account is suspended and all sessions are signed out as soon as we receive the request.
- Any paid subscription is cancelled at that point.
- Within 30 days of the request, we delete your account and connected-account information (access tokens, profiles, posts, metrics, and anything you entered or uploaded).
- Permissions granted to X and other networks are revoked.
- Teams you own are deleted along with the team.
The following is kept after your account is closed. Information remaining in system backups is deleted when the backup retention period ends.
- Contract, billing and payment records (for the period required by law, generally 7 years)
- A record of the closure request
- Records used to prevent abuse (converted to values that cannot identify you)
- Drafts and comments you wrote in other people's teams (the author is shown as “former member”)
Data deleted automatically
Data that is no longer needed is deleted automatically, without waiting for you to close your account. The main items are below. The full list is in Article 8 of the Privacy Policy.
| Data | Deleted after |
|---|---|
| Images and videos of posts that were published | 1 day after publishing (the post itself stays on the network) |
| Images and videos of posts that failed | 30 days after failure (you can retry until then) |
| Images and videos created with AI | 30 days after creation |
| Conversations with the AI agent | 1 year after the last update |
| Records of automatic Instagram DM sends | 180 days after creation |
How we build and operate the service
- Keeping secrets out of code: every change is automatically scanned before it is recorded so that keys and other secrets do not slip into the code.
- Checking dependencies: third-party components are regularly checked for known vulnerabilities.
- Defenses against attacks: checks against cross-site request forgery (CSRF), browser security headers, and limits on large numbers of requests in a short time.
- If something goes wrong: in the event of a personal data breach, we investigate promptly, notify those affected, and report to Japan's Personal Information Protection Commission.
Contact
For questions about security or data handling, or to report a problem you have found, please reach us via Contact.