Privacy policy

Last updated 25 September 2026

Who we are

Content Fork is a service operated by Rocksolid Solutions Pte. Ltd., a company registered in Singapore. It fetches an article from a URL, rewrites it, and hands it back for you to edit and publish.

This policy covers the website and customer console at content-fork.com, the service those talk to, and the WordPress plugin that connects a site to it.

What we hold

We keep as little as the service needs to work, to bill for it, and to explain what happened when something goes wrong.

• Your account. The email address and account identifier your sign-in provider gives us. Creating an account happens the first time you sign in.
• Your site keys. A SHA-256 hash of each key, never the key itself. Alongside it we store the label you gave it, when it was created, the domain it was first used from, and whether it has been revoked.
• Your forks. The article URL you submitted, the settings you chose, the status, the timings, the model and prompt versions used, and the credits charged. A fork that succeeds also stores the article it produced — title and body — because that is the record of what you paid for and the history you can look back at.
• Your payments. The pack bought, the amount, the currency, the provider's reference, and the timestamps. Not the card: see below.
• Campaign attribution. If you arrive through a campaign link, we keep its opaque reference and the landing page. If you then sign in or create an account, we associate that reference with your account identifier to measure whether the campaign led to an account. The reference does not contain your email address.
• Failed runs. When a fork fails we keep a trace — the page as it was fetched, the prompt we sent, and the reply we received — in a private bucket, so a failure can be explained and fixed. A run that succeeds deletes its own trace.

What we never see

• Card details. The payment form belongs to our payment provider and loads in their own frame. The number you type is sent to them and never reaches our servers.
• Your WordPress content. The plugin sends the URL you submitted, your fork settings, your site key, and your site's hostname. It does not send your posts, your pages, your users, or your database.
• Your password. Sign-in is handled by our identity provider. We never receive a password.

Why we hold it

• To run the fork you asked for, and to show you its result and history.
• To bill you in credits and keep a record of what was charged.
• To diagnose failures and answer support questions.
• To keep an account from being used beyond what it has paid for.
• To measure responses to relevant business outreach and understand whether campaign links lead to account sign-ups.

How long we hold it

Account details, site keys, fork history and payments are kept while your account exists. There is no automatic expiry on any of them, deliberately: your fork history is also the record of what you were charged, and a record that deletes itself is not a record.

• Site keys stop working as soon as you revoke them, and can be removed from your account at any time.
• Failed-run traces are the one thing kept past its use. They are not expired automatically; we clear them by age as part of housekeeping. Ask us and we will clear yours sooner.
• Campaign attribution events are deleted automatically after 365 days.
• Ask us to close your account and we will delete the account, its keys, your fork history and the articles stored with it. Payment records are the exception: accounting requirements mean we keep those, and the ledger that shows a purchase is the same shape of record.

Who else processes it

We use third-party providers to run the service. Each receives only what its job needs — nothing more — and each is bound by contract to use it only to provide their service to us. The categories are:

• Hosting and storage — the infrastructure the service and your data sit on, in the Singapore region.
• Payment processing — when you buy credits. Your card details go to this provider and never to us.
• Article retrieval — fetches the URL you submitted, so that the page can be rewritten.
• AI models — perform the rewrite. The article is sent to them as part of the request, and a second provider stands behind the first when it is unavailable.
• Stock photographs — searched when you choose a photograph for a fork.

We do not sell your data, and we do not share it with anyone for advertising or profiling. Where a provider processes data outside your country, we rely on their safeguards for that transfer.

We name the categories rather than the companies so that replacing one does not invalidate this page. If you need the specifics — for a privacy review, or a due-diligence questionnaire — ask us and we will tell you which providers received your data, and what each was given.

Cookies and browser storage

This site uses first-party browser storage to keep an opaque campaign reference for up to 30 days when you arrive through a campaign link. It records the landing page and, if you sign in during that period, associates the reference with your account identifier. The related event records are kept for up to 365 days. We do not use third-party advertising or analytics cookies, and no third-party analytics vendor is connected to the site.

The customer console keeps your sign-in token in the browser tab's own storage, not in a cookie. Your WordPress site is unaffected either way: the plugin holds no cookies of ours and stores only the key you pasted into it.

Your choices

• Revoke a key yourself, at any time, on the Site keys screen. It stops working immediately.
• Ask for a copy of what we hold about your account.
• Ask us to delete your account and its data, as described above.
• Ask which providers received your data, and we will tell you which, and what each was given.

How it is protected

Traffic to and from the service is encrypted. Site keys are stored only as hashes, so a copy of the database does not yield a working key. Card details never reach us. Access to production data is limited to the people who operate the service.

Changes to this policy

When this policy changes, the date at the top changes with it. If a change materially affects what we do with your data, we will say so in the console rather than leave it to be noticed here.

Contact

Questions, corrections and requests go to support@content-fork.com.