Rechtliches
Privacy Policy
This policy explains what we collect, why we collect it, who else sees it, how long we keep it, and what you can require us to do about it. It describes the system as it is actually built, including the places where our answer is less tidy than we would like.
- Gültig ab
- Zuletzt aktualisiert
- Version
- 1.15.0
1. Who we are and how to reach us
Opus Rank ("we", "us") is the controller of the personal information described in this policy. That means we decide what is collected and why, and we are the party accountable for it. Every route to us is by email — the addresses below are monitored, and a request sent to one of them reaches a person.
| Purpose | Contact |
|---|---|
| Privacy and data-subject requests | [email protected] |
| Legal notices | [email protected] |
| Account and billing questions | [email protected] |
Where we act as a processor rather than a controller — principally for the article content you create, which is yours and which we handle on your instructions — the terms of that relationship are set by our Terms of Service. If you need a data processing agreement for your own compliance programme, ask at [email protected].
We have not appointed a representative in the European Union or the United Kingdom under Article 27 GDPR. We are telling you rather than leaving the question open: if you are in either territory and want to exercise a right, write to [email protected] and it will be handled on the same terms and within the same deadlines set out below. Your right to complain to your own supervisory authority is unaffected.
2. What we collect
We collect only what the service needs to function. The categories below correspond to actual tables in our database rather than to a general description of a category of software.
| Category | What it contains | Source |
|---|---|---|
| Account identity | Your name, email address, and either a one-way bcrypt hash of your password or, if you sign in with Google, the profile picture URL Google returns. We never store a password in a form we can read. | You, at sign-up |
| Sign-in tokens | If you sign in with Google, the OAuth access, refresh and identity tokens that keep that connection working. | Google, on your authorisation |
| Workspace and project context | Your project name, website domain, business description, target audience, and default language, country and tone. This is free text you write, and it often describes your business rather than you personally. | You |
| Website analysis | If you ask us to analyse a website during onboarding or when you add a project: the address you entered, the addresses of the public pages we read and whether each could be read, and the suggested answers we drafted from them. We do not keep the pages themselves or the text on them. | Your website, at your request |
| Content and inputs | Every article, every saved version, autosaved drafts, the target keywords and briefs you supply, rewrite instructions, the exact text you select for an AI edit, and the prompts you write for generated images. | You |
| Keyword research | If you research a keyword: the keyword you entered, the country and language you chose, and the monthly search volume, cost-per-click and keyword difficulty returned for it, saved to your project’s history with the time you ran it. | You, and our keyword-data provider |
| Generation records | The queued job for each generation, including the full resolved brief it was built from and the output it produced. | Generated by the service |
| Usage and credit records | An append-only ledger of every credit reservation, charge, refund and adjustment: which feature, what it cost, and the resulting balance. | Generated by the service |
| Billing records | Your subscription status, plan, billing period, amount and currency, plus the customer and subscription identifiers our payment provider assigns you, and the webhook events it sends us. | Our payment provider |
| Publishing credentials | If you connect a publishing destination — a site on WordPress, Webflow, Ghost, Medium, Shopify or Framer, a Notion workspace, or a webhook endpoint of your own — the credentials or access token for it, and for a webhook the endpoint address and its signing secret. All of it is encrypted with AES-256-GCM before it is stored and decrypted only at the moment you publish. A webhook signing secret is shown to you once, when it is created or rotated, and never again. | You |
| Publishing records | For each publication, the destination, the resulting URL and post identifier, and the exact payload sent to your platform. For destinations that support updates, the link between each article and the item it became there, so publishing again updates that item rather than creating a second one. A history of who connected, configured or disconnected a destination and of every publish, update and unpublish with its outcome. For webhook endpoints, a log of each delivery attempt: its time, the response status code and how long it took — never the content sent or the reply received. | Generated by the service |
| Security and anti-abuse records | Sign-up and sign-in events, password resets, rate-limit trips, the outcome of bot-protection checks on our sign-up, sign-in, password-reset and contact forms, and account risk state. Where IP addresses are recorded at all they are stored as a salted one-way hash, not as addresses. | Your browser, indirectly |
| Support and administration records | Notifications we send you, and an append-only audit trail of any action a member of our staff takes on your account, including the written reason for it. | Generated by the service |
| Contact form messages | If you write to us through the contact form: your name, your email address, the topic you chose, your message, the language of the page you sent it from, and whether a member of our staff has marked it handled. You do not need an account to send one. | You |
There is no file or image upload feature, so nothing arrives that way. We do not fingerprint devices, store user-agent strings, or use tracking pixels. We do not buy, rent or receive personal information about you from data brokers, and we do not enrich your record from third-party sources. We do not ask for your date of birth, your address, or your card details — card details go to our payment provider and never reach our servers.
3. Why we use it, and on what legal basis
For people protected by the GDPR or UK GDPR, the table below sets out our purposes and the Article 6 basis for each. For everyone else it is still an accurate statement of what we do and why.
| Purpose | Categories used | Legal basis |
|---|---|---|
| Creating and running your account, and letting you sign in | Account identity, sign-in tokens | Performance of a contract (Art. 6(1)(b)) |
| Generating, storing, versioning and exporting your content | Workspace context, content and inputs, generation records | Performance of a contract (Art. 6(1)(b)) |
| Suggesting answers for your business or project profile from a public website, when you ask us to during onboarding or when you add a project | Website analysis, workspace context | Performance of a contract (Art. 6(1)(b)) — you asked for it, and you review and confirm every suggestion before it is saved |
| Looking up search data for a keyword you choose, and keeping it in your project’s history | Keyword research | Performance of a contract (Art. 6(1)(b)) |
| Publishing to a platform you have connected | Publishing credentials, publishing records, content | Performance of a contract (Art. 6(1)(b)) |
| Metering credits, taking payment, and handling refunds and disputes | Usage and credit records, billing records | Performance of a contract (Art. 6(1)(b)); legal obligation for tax and accounting records (Art. 6(1)(c)) |
| Verifying your email address before issuing free credits | Account identity, security records | Legitimate interests (Art. 6(1)(f)) — preventing the same person claiming a welcome grant repeatedly |
| Rate limiting, abuse prevention, and account risk decisions | Security and anti-abuse records, account identity | Legitimate interests (Art. 6(1)(f)) — keeping the service available and affordable for legitimate users |
| Service notifications about your account, jobs and billing | Account identity, notifications | Performance of a contract (Art. 6(1)(b)) |
| Answering a message you send through the contact form | Contact form messages | Legitimate interests (Art. 6(1)(f)) — replying to an enquiry you started; performance of a contract (Art. 6(1)(b)) where it is about your account |
| Diagnosing faults and keeping the system reliable | Generation records, security records | Legitimate interests (Art. 6(1)(f)) — operating a service that works |
| Responding to legal claims, and to your privacy requests | Any of the above, as relevant | Legal obligation (Art. 6(1)(c)); legitimate interests in establishing or defending claims (Art. 6(1)(f)) |
| Aggregate analytics on the public marketing pages | Device and usage signals only, no account data | Consent (Art. 6(1)(a)) — see the Cookie Policy. Not currently in use. |
Where we rely on legitimate interests, the balance we struck is this: the processing is limited to what a security or reliability decision actually needs, it uses hashed rather than raw identifiers wherever a hash will do, none of it is used to profile you commercially, and none of it restricts what you can read or export from your own account. You can object to it at any time on the basis described below, and we will stop unless we can show compelling grounds that override your interests.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law. We have not done so in the preceding twelve months. There is no advertising technology in this product and no data flows to an ad network.
4. What happens when you generate content
Content generation is performed by third-party large language models reached through OpenRouter, a routing service that forwards each request to the model provider that will serve it. That provider may be Anthropic, OpenAI, Google or Black Forest Labs, and which one handles a given request is determined at the moment of the call by our internal routing catalogue and the plan you are on.
What leaves our servers as part of a generation request:
- Your brief — the target keyword, working title, target audience, brand notes, tone, language, country and word count you supplied.
- Your project context — the website domain, business description and usual audience saved on the project the article belongs to.
- The content itself — for a rewrite, a section edit or an AI edit, the existing article text, or the exact passage you selected.
- Image prompts — for a generated image, the prompt you wrote plus the article context used to compose it.
- Headings and titles — for keyword clustering and internal-link suggestions, short text fragments sent to an embedding model.
- Your website's public text — only if you ask us to analyse a website during onboarding or when you add a project: text from its homepage and up to four of its other public pages, such as its about and services pages, used to suggest answers you then review. We read only pages its robots.txt file allows, identify ourselves when we do, and never sign in to anything.
What does not leave our servers as part of a generation request:
- Your name, your email address, your account or workspace identifier, or any billing information. None of these appear in any prompt we construct.
- Your publishing credentials, which are only ever decrypted at the moment you publish and are sent only to your own platform.
We record what each generation cost — the model called, the token counts, the price and whether it succeeded — so that we can bill you accurately and investigate failures. We do not store the prompt or the completion text in those records. The article itself is stored, because it is the thing you asked us to make.
We do not control how OpenRouter or the model providers behind it retain request data or whether any of them use it to train models. Their terms govern that, they can change them, and we would be misrepresenting our position if we made a commitment on their behalf. If your content is confidential or regulated, treat sending it to a generative model as a disclosure and decide accordingly. Their current policies are the authoritative source, and we encourage you to read them.
5. Cookies and similar technologies
We use cookies that are strictly necessary to authenticate you, keep you signed in, and protect forms against cross-site request forgery. These are exempt from consent because the service cannot work without them.
We set nothing for analytics, measurement or advertising without your prior, affirmative consent. Our Cookie Policy lists every cookie by name, purpose and lifetime, describes the analytics tools we plan to introduce, and explains how to grant or withdraw consent and how to control cookies in your browser.
Separately from cookies, your browser stores your light-or-dark appearance preference in local storage. It never reaches our servers and identifies nobody.
6. Who else sees your data
We disclose personal information to the processors below, each under a written contract that limits them to acting on our instructions and requires appropriate security. We do not disclose personal information for anyone else’s independent commercial purposes.
| Recipient | What they receive | Why |
|---|---|---|
| OpenRouter and the model providers it routes to (Anthropic, OpenAI, Google, Black Forest Labs) | Your brief, project context, and the content being generated or edited | Generating and editing content — see the section above |
| DataForSEO | The keyword you research, with the country and language you chose — never your name, email address, or an account or workspace identifier | Returning the search volume, cost-per-click and keyword difficulty for that keyword |
| Dodo Payments | Your email address and the billing details you give them directly at checkout | Taking payment, managing subscriptions, handling refunds and disputes as merchant of record |
| Only what an OAuth sign-in requires, and only if you choose that method | Sign-in, and serving your profile picture to your own browser | |
| Our email provider | Your email address, name and the contents of service emails, and — when you use the contact form — your message, forwarded to our own support inbox | Sending verification links and account notifications |
| Cloudflare (Turnstile), where enabled | Your IP address and technical signals from your browser, when you use our sign-up, sign-in, password-reset, verification-email or contact forms | Telling people apart from automated abuse of those forms. We receive only whether the check passed |
| Our object storage provider | Generated images and their file metadata | Storing images so your publishing platform can fetch them |
| Our error-reporting provider, where enabled | Technical diagnostics from a failure, which may incidentally include an identifier | Diagnosing faults |
| Analytics providers — Ahrefs, Google, Microsoft | Device and usage signals from the public marketing pages only | Aggregate measurement. Not currently in use, and never without your consent — see the Cookie Policy |
We will also disclose personal information where we are legally required to — a valid court order, subpoena or regulatory demand — and where it is necessary to establish, exercise or defend legal claims, or to protect the rights and safety of others. Where we are permitted to tell you about such a demand, we will.
If we are ever involved in a merger, acquisition or sale of assets, personal information may transfer as part of it. We will give you notice before that happens and before your information becomes subject to a different privacy policy.
One case is worth stating plainly because it is under your control rather than ours: when you publish an article to your own site, you send that content to the platform you connected, on your instruction. From that moment it is governed by your relationship with that platform and by your own privacy policy, not by this one.
7. International transfers
We are established in the United States. The service runs on a single dedicated server running the application, its database and its object storage. Our processors operate in the United States and in other countries.
This means that if you are located in the European Economic Area, the United Kingdom or Switzerland, your personal information will be transferred outside that territory, to a country that may not have been the subject of an adequacy decision.
Where that happens, we rely on one of the following:
- Standard Contractual Clauses adopted by the European Commission, together with the UK International Data Transfer Addendum where the UK GDPR applies, incorporated into our contracts with the recipient.
- An adequacy decision, where one covers the destination country.
- The EU–US, UK–US or Swiss–US Data Privacy Framework, where the recipient is certified under it.
- A transfer necessary for the performance of our contract with you, which is the basis on which content you explicitly ask us to send to a model provider or to your own publishing platform is transferred.
We carry out transfer impact assessments where the Clauses require it, and we apply supplementary measures — encryption in transit throughout, encryption at rest for credentials, and minimising what is sent in the first place. To ask which mechanism covers a particular transfer, or to request a copy of the relevant clauses, email [email protected].
8. How long we keep it
The periods below are the ones our systems actually apply. Where a sweep exists, it runs automatically; where none exists, the table says so.
| What | How long | What happens then |
|---|---|---|
| Articles you delete | 30 days in trash | Permanently destroyed, along with every version, draft, AI-edit record, generated image and publication record attached to them. You can restore or destroy one sooner yourself. |
| Projects you delete | 30 days in trash | Permanently destroyed, along with every article, connection (including its stored credentials), brand voice, plan, schedule and generated image in them. An owner or admin can restore one sooner; the workspace owner can destroy one sooner. |
| Articles you have not deleted | For as long as your account is open | Kept, because they are the thing you are paying us to hold |
| Earlier versions of an article (each save, generation, rewrite and accepted AI edit) | The 3 most recent earlier versions, each for at most 30 days | Deleted by a daily sweep, never within an hour of being replaced. The current version is kept for as long as the article is, and so is any version sent to one of your publishing destinations. Nothing is removed from an article in trash until the article itself is destroyed. |
| AI usage records (model, tokens, cost) | 180 days | Deleted by a daily sweep, whether the call succeeded or failed. The credit record of what an article cost is not affected. |
| Rate-limiting records | At most 1 hour | Deleted automatically when the limit window they belong to lapses. These briefly contain an IP address or email address in the clear, which is the one place we do not hash — see the security section. |
| Email verification links | 24 hours until the link expires | The link record is deleted when it is used or when it expires, whichever comes first. What is retained is the date your address was verified, on your account — that is the proof, and it is all of it we keep. |
| Password reset links | 60 minutes until the link expires | The link record is deleted when it is used, when a newer link replaces it, or when it expires, whichever comes first. What is retained is the new password, stored only as a one-way hash, and a record that a reset happened. |
| Sign-in session | 30 days | You are signed out and must sign in again |
| Domain-ownership proofs | 180 days | The proof lapses and must be re-established before publishing to that domain |
| Domain verification tokens | 30 days after the token is used, replaced or expires | Deleted by a daily sweep. While a token is waiting to be placed we keep it encrypted so you can see it again; once it is used, replaced or expires we keep only a one-way fingerprint of it. |
| Domain ownership history (verification checks, which free account a website is registered to, and any change our staff make to either) | 730 days | Deleted by a daily sweep. Each website can have one free account, and this history is how we enforce that fairly. The record that your account currently holds a website is kept for as long as it does. |
| Generation job records (what was requested, the result, any error) | 30 days after the job finishes | Deleted by a daily sweep. The article a job produced is not affected, and neither is the credit record of what it cost. A job still needed to show the state of a topical-map topic or an autopilot run is kept until that is no longer the case. |
| Autopilot run history and archived autopilot topics | 365 days after the run finishes or the topic is archived | Deleted by a daily sweep. Topics you have used or skipped are kept, because they are what stops the same keyword being written twice. |
| Notifications | 180 days | Deleted by a daily sweep once any email they carry has been sent or given up on. A notification still waiting to be emailed is kept until it has been. |
| Team invitations | 90 days after the invitation is accepted, withdrawn or expires | Deleted by a daily sweep. |
| Website analyses you did not go on to confirm | 30 days after the analysis | Deleted by a daily sweep. An analysis whose suggestions you confirmed is kept with the project it set up, as the record of where those answers came from, and goes when the project does. |
| Generation credit limit checks (who started a generation, its credit cost, and whether the plan’s hourly or daily limit allowed it) | 90 days | Deleted by a daily sweep. The limit itself is worked out from the credit record, not from these, so deleting them changes nothing you can do. |
| Monthly usage counts for metered features | 13 months, including the current one | Deleted by a daily sweep. |
| Earlier internal-link suggestions for an article | 90 days once a newer set exists | Deleted by a daily sweep. The most recent set for each article is kept for as long as the article is. |
| Keyword research history (each keyword you researched, where, and the figures returned) | 365 days | Deleted by a daily sweep, and sooner if you delete a result or its project is permanently deleted. |
| Keyword search data we keep so the same keyword is not looked up twice | 7 days | Deleted by a daily sweep. It holds a keyword, a country, a language and the figures returned for them — nothing that identifies you or your workspace — and answers anyone who researches the same keyword in that period. |
| Keyword-data request records (what each lookup cost and whether it succeeded) | 180 days | Deleted by a daily sweep. They never contain the keyword. |
| Contact form messages | 180 days | Deleted by a daily sweep, whether or not we have finished answering. A reply we send you stays in your own mailbox, and anything that becomes part of your account record is kept under that record’s own period. |
| Webhook delivery log (when each delivery to your endpoint was attempted, its status code and duration) | 30 days | Deleted by a daily sweep. The log never contains the article that was sent or what your endpoint replied. |
| Publishing history (who connected, configured or disconnected a destination, and every publish, update and unpublish with its outcome) | 365 days | Deleted by a daily sweep, and with your workspace if you delete it. The link between an article and the item it became on a destination is kept for as long as both exist. |
| Administrative audit trail (every action a member of our staff takes on an account, with their written reason) | 90 days | Deleted by a daily sweep. While it is kept, no entry can be altered or removed by anyone — the database refuses it — and only the sweep can remove an entry once its period has passed. |
| Credit ledger, billing records and payment events | Indefinitely | Retained as financial records. The ledger is append-only by design, so entries cannot be altered after the fact. |
| Security and risk records (sign-up and sign-in signals, rate-limit and bot-protection outcomes, verification results, account risk decisions) | 180 days | Deleted by a sweep that runs every fifteen minutes, and sooner if the records reach their storage limit, oldest first — never a record less than a week old. Repeated failed attempts from the same source are kept as one record with a count per hour. They contain hashed identifiers rather than addresses, and never a password, a security-check token or a code. One exception: while an account or workspace is under a restriction, the latest record explaining that restriction is kept for as long as the restriction lasts. |
| Shopify notifications received (a fingerprint of each message, never its contents) | 30 days | Deleted by a sweep that runs every fifteen minutes, and sooner if the records reach their storage limit, oldest first — never a record less than three days old, which is how we recognise a notification Shopify sends twice. |
| AI-edit records and publication payloads | For as long as the article they belong to | Destroyed with the article when it is permanently deleted. No separate sweep exists for these today, so we do not claim a shorter period. |
When you close your account we delete or irreversibly anonymise personal information that we have no continuing basis to keep. Some records survive that deletion by design: the credit ledger, and the administrative audit trail for the rest of its 90-day period, are append-only and hold no foreign key to your account precisely so that a deletion cannot silently rewrite a financial or accountability record. Where erasure of the ledger is required by law, we have a separate operator-run process that destroys it, described in the rights section below.
9. How we protect it
The measures that matter most:
- Passwords are hashed with bcrypt and never stored in a readable form. We cannot tell you your password because we do not know it.
- Publishing credentials are encrypted with AES-256-GCM before storage. The key lives outside the database, so a database backup on its own does not yield them, and they are never sent to your browser.
- Verification tokens are stored as SHA-256 hashes, so a database dump does not hand anyone a working link.
- IP addresses, where recorded for security purposes, are salted and hashed. If that salt is not configured, addresses are not recorded at all rather than recorded in the clear.
- Everything is served over TLS, with HTTP Strict Transport Security, a restrictive Content Security Policy, and clickjacking and MIME-sniffing protections.
- Access is re-verified on every request. An identifier supplied by a browser is treated as a filter, never as permission — asking for someone else’s article returns "not found", because the query is re-derived from your session.
- Staff access is capability-based and audited. Every administrative action on a customer account is written to an append-only log, inside the same transaction as the change, with the operator’s written reason, and kept for 90 days.
Our rate limiter records the key it is counting against, and for sign-up and sign-in that key contains your IP address or your email address in the clear. Each record expires with the limit window it belongs to — at most 1 hour, and usually a few minutes. We are telling you because it is true, not because we think it is ideal — hashing that key is on our list.
No system is perfectly secure, and we do not claim otherwise. If we become aware of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours where the GDPR requires it, and we will notify you directly without undue delay where the risk to you is high.
If you believe you have found a security vulnerability, please report it to [email protected] rather than disclosing it publicly. We will not pursue action against good-faith research that respects the boundaries in our Acceptable Use Policy.
10. Your rights over your data
Depending on where you live, some or all of the following rights apply to you. We extend them to everyone as a matter of practice, regardless of location.
- Access — a copy of the personal information we hold about you, and confirmation of how we use it.
- Rectification — correction of anything inaccurate, and completion of anything incomplete.
- Erasure — deletion of your personal information where we no longer have a basis to keep it.
- Portability — the information you gave us, in a structured, commonly used, machine-readable format, or transmitted directly to another provider where technically feasible.
- Restriction — a pause on processing while a dispute about accuracy or legitimate interests is resolved.
- Objection — an objection to processing we carry out on the basis of legitimate interests, which we will honour unless we can demonstrate compelling grounds that override your interests.
- Withdrawal of consent — where we rely on consent, you can withdraw it at any time, without affecting anything done before you did.
- Complaint — the right to complain to your data protection authority. In the UK that is the Information Commissioner’s Office; in the EEA it is the authority in your country of residence, work or the alleged infringement.
To exercise any of these, email [email protected] from the address on your account, or tell us how else to verify you if you cannot. We will respond within one month, and will tell you before that month is up if a complex request needs an extension of up to two further months. There is no charge unless a request is manifestly unfounded or excessive, in which case we will explain why before doing anything.
You can edit your projects and articles at any time, restore or permanently destroy trashed articles yourself, and export any article as Markdown, HTML or plain text at no cost. Export is deliberately free and stays available even when an account is under review or a payment has failed — getting your own work out must never be the thing a restriction prevents.
Two limits worth being straight about. First, we do not yet offer a one-click account deletion button or a single download containing your entire account; both are handled by writing to us, and we do them properly when you ask. Second, erasing your account does not remove content you have already published to your own website — that is on your platform, under your control, and we have no way to reach it.
11. If you are in the United States
This section addresses the California Consumer Privacy Act as amended by the CPRA, and the comparable laws of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana and other states with equivalent statutes.
The categories of personal information we collect, the sources they come from, our purposes, and the categories of third party we disclose to are all set out above. In the preceding twelve months we have collected the categories listed in "What we collect" and disclosed them for the business purposes listed in "Who else sees your data".
Your rights under these laws:
- To know what personal information we have collected, used and disclosed, including the specific pieces.
- To delete personal information we collected from you, subject to the statutory exceptions — chiefly records we must keep for accounting, security or legal-claims purposes.
- To correct inaccurate personal information.
- To a portable copy of the information you provided.
- To opt out of sale or sharing for cross-context behavioural advertising. We do not sell or share personal information and have not done so, so there is nothing to opt out of. If that ever changes, we will provide a "Your Privacy Choices" control before it does, and we will honour Global Privacy Control signals.
- To limit the use of sensitive personal information. We do not collect sensitive personal information as that term is defined, and we do not use any information for inferring characteristics.
- To non-discrimination — we will not deny you service, charge you a different price, or give you a lower quality of service because you exercised a right. We offer no financial incentive in exchange for personal information.
Submit a request at [email protected]. We will verify you by matching the request against the email address on your account. An authorised agent may act for you with written permission, which we will ask to see, and we may still ask you to confirm directly. If we deny a request you may appeal by replying to our decision; we will respond to an appeal within 45 days and tell you how to contact your state attorney general if you remain unsatisfied.
California residents may also request the information described in the "Shine the Light" law, Civil Code §1798.83, about disclosures to third parties for their own direct marketing purposes. We make no such disclosures.
12. If you are in mainland China
Where the Personal Information Protection Law of the People’s Republic of China applies to you, we process your personal information on the basis of your consent and of the necessity of doing so to perform the contract you have entered into with us.
You have the rights to know, to access and copy, to correct and supplement, to delete, to restrict or refuse processing, to request an explanation of our processing rules, to withdraw consent, and to have your personal information transferred to another handler you nominate. Your next of kin may exercise these rights in respect of a deceased person.
Our servers and our processors are outside mainland China, so using this service necessarily transfers your personal information abroad — including, when you generate content, to AI providers in the United States and elsewhere. By creating an account and generating content you give your separate consent to that transfer. You can withdraw it at any time by writing to us, but be aware that withdrawing it means we can no longer provide the service.
To exercise a PIPL right or withdraw consent, email [email protected].
13. Automated decisions and profiling
We do not carry out automated decision-making that produces legal effects concerning you or similarly significantly affects you, within the meaning of Article 22 GDPR.
Our anti-abuse system records signals and can mark an account for review, but the states that actually restrict an account are set by a person, and every such action is logged with a written reason that is shown to you. Content generation is automated by definition, but it produces a draft for you to review; it makes no decision about you.
We do not build commercial profiles of you, and we do not use your content or your usage to target you with anything.
14. Children
Opus Rank is a business tool intended for adults. It is not directed at children, and you must be at least 18 years old to create an account.
We do not knowingly collect personal information from anyone under 18. We do not currently operate an age gate at sign-up, so this is a contractual requirement rather than a technical one — which is exactly why we ask you to tell us. If you believe a child has provided us with personal information, contact [email protected] and we will delete the account and its data.
15. Changes to this policy
The effective date, last-updated date and version number at the top of this page reflect the current text. They change only when the text changes.
Where a change materially affects how we handle your personal information — a new purpose, a new category of recipient, or a materially different retention period — we will notify you by email or through the application before it takes effect, and where the law requires your consent we will ask for it rather than assume it.
Superseded versions are retained in our source control history and are available on request.
16. Contact us
For anything in this policy, including a request to exercise a right, email [email protected]. That mailbox also takes formal legal notices. For account and billing questions, [email protected] is the faster route.
If you are in the EEA or the UK and you are not satisfied with how we have handled your request, you have the right to complain to your supervisory authority. We would rather you came to us first, but that right does not depend on you doing so.