Privacy Policy
Effective November 6, 2026
Orikata Bio Public Benefit Corporation ("Orikata Bio PBC," "we," or "us") is the United States company that operates the services covered by this policy. Megure Labs and Orikata Bio are brands of Orikata Bio PBC, not separate legal entities. Contact us at casey@orikata.ai about this policy or your information.
What this policy covers
This policy covers megure.ai, orikata.bio, orikata.ai and their product, account and service subdomains, including noto.megure.ai and accounts.megure.ai. It covers our public websites, anonymous analysis tools, account registration and sign-in, hosted model services and billing where enabled, and communications with us. The anonymous alignment service is available through orikata.bio, orikata.ai and megure.ai without an account and has no payment checkout.
Information we receive
- Account information: your email address, account identifiers, profile information you provide, and authentication and session records. Our authentication provider, Clerk, processes this information to operate your account.
- Workspace and billing information: workspace names, membership and invitation records, billing account identifiers, subscription and payment status, and usage and credit records when those features are available. Payment details are collected through Stripe; we do not store full payment-card numbers.
- Google sign-in information: if you choose Google sign-in, Google supplies your Google account identifier, email address and verification status, and basic profile information such as your name and profile picture when available. Our requested Google permissions are limited to OpenID identity, email, and basic profile. Google authentication tokens may also be processed by Clerk to complete the connection.
- Communications: the contact details, messages, and other information you choose to send us by email or through support.
- Technical information: website and authentication requests can include IP address, browser and device information, requested URLs, timestamps, and security or error information. Our hosting and authentication providers process request information to deliver and protect their services.
Anonymous protein alignment
When you request an alignment, we process the sequences, structures, files, database identifiers, and options you supply, along with the resulting alignments, measurements, and downloadable files. Database identifiers can cause our service to fetch the requested data from its public provider. Submit only information you are authorized to provide for this processing. This feature runs existing tools and models; it does not train models on your submissions.
Cloudflare hosts the compute and private job storage. Cloudflare Turnstile checks a visitor before a guest session is created. A secure guest-session cookie lasts up to 24 hours, so verification is not required for every job. We use guest identifiers and daily hashed network identifiers to enforce usage limits and investigate abuse. The alignment application does not store the raw IP address in those counters; Cloudflare can still process network request information as described below.
Each job has a private retrieval credential. Anyone who has that credential or its result link can retrieve the job, so keep the link private. An account is not required to retrieve a result. Retrieval expires after seven days, and storage lifecycle rules schedule uploaded inputs and job outputs for deletion after seven days. Platform cleanup may occur after that expiry, and provider security logs and backups follow their own retention practices.
Hosted model jobs
When you request a model quote or run a model in an account workspace, we process your protein sequence, selected model and options, generated alignments and structures, result files, job identifiers, processing times, and usage charges. We use this information to provide the requested computation, show job history and downloads, verify usage charges, and investigate failures or abuse.
Cloudflare coordinates jobs and stores private inputs and results; Neon stores account, job, and billing records. Modal processes sequence-search and alignment stages, and Runpod processes model prediction stages. These compute providers receive the inputs and intermediate files needed for their part of your job. Account job results require workspace authorization, and Team members can access their workspace's shared jobs and results.
How we use Google information
We use Google identity information only to create and identify your account, authenticate you, maintain account security, and provide account-related support. We do not sell Google user data, use it for advertising or profiling for advertising, or use it to train AI or machine-learning models. We do not request access to your Gmail messages, Google Drive files, contacts, or calendars.
Orikata Bio PBC's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Any additional use or new Google permission would require a separate explanation and any required consent.
Other uses and service providers
We use account and technical information to provide our website and account features, respond to requests, investigate errors and abuse, communicate about accounts, and meet applicable legal obligations.
In a Team workspace, members can see each other's names and verified contact emails, shared jobs and results, and workspace billing and usage information. The owner manages membership, billing and workspace API keys. Joining an invitation requires an explicit acceptance using its verified email address.
For account billing, we use Stripe for payments and subscriptions and Metronome for usage-based billing. Billing services receive the billing identifiers and usage information needed for that role, such as the model or workflow used and its billable quantity or cost. Our usage events do not include protein sequences or result files.
We disclose information to providers when needed to operate these features: Clerk for authentication, account profiles, sessions, and authentication messages; Cloudflare for hosting, content delivery, and security; Google for Google sign-in and fonts; and providers that deliver email communications. Providers process information under their applicable service arrangements and policies. Clerk's own website privacy policy also covers its separate website and business operations; those are distinct from its role in managing an account with us.
We may disclose information where required by law or necessary to address fraud, security incidents, or protect legal rights. If the business is reorganized or transferred, information may transfer with it subject to applicable law and this policy. We do not sell personal information or share it for cross-context behavioral advertising.
Cookies and external resources
Account features use cookies and similar browser storage for authentication, session continuity, and security. Blocking or clearing these may prevent sign-in or sign you out. Fonts are served from our website. The public site does not include an advertising-tracking or third-party marketing-analytics integration.
Retention, deletion, and your choices
We keep account and profile information for as long as needed to provide your account and the purposes described here. Support and security records may be kept as needed to address requests, prevent abuse, resolve disputes, or satisfy legal obligations. This policy does not promise a fixed retention period for all records.
For signed-in model jobs, we retain job records, inputs, and results as needed to provide job history and downloads and to reconcile usage and investigate issues. The seven-day retrieval period described above applies to anonymous alignment jobs. You can request deletion of account job data using the contact process below; billing, security, and provider backup records may have different retention needs.
To request access, correction, or deletion of your information or account, email casey@orikata.ai. We may need to verify your identity before acting. Following an account-deletion request, we delete or de-identify information no longer needed for these purposes; limited records may remain where necessary for legal or security purposes or in provider backups until their normal deletion cycle.
You can also remove Orikata's Google connection in your Google Account connections settings. Revoking Google access does not itself delete an existing Orikata account or all information already received. Contact us to request that deletion. You can use email verification instead of Google sign-in.
Depending on applicable law, you may also have rights to obtain a copy of your information, object to or restrict certain processing, withdraw consent, or complain to a privacy regulator. Contact us to exercise applicable rights.
Security and international processing
We use HTTPS for website and account connections and rely on our hosting and authentication providers' security controls. No system can guarantee absolute security. We are based in the United States, and information may be processed there and in other countries where our providers operate. Their data-protection laws may differ from those in your country.
Children
Our website and accounts are intended for scientific, professional, and research audiences and are not directed to children under 13. Contact us if you believe a child has provided personal information so we can investigate and take appropriate action.
Changes
We will update this page and its effective date when practices change. For material changes affecting existing users, we will provide appropriate notice and obtain consent where required before using information for a new purpose.