The short version
- rtfx.pro hosts pages and files that you (usually through Claude) publish, and lets you decide who can open them: named people, your workspace, or share links you create.
- We use email addresses for accounts, invitations and passwordless sign-in. There are no passwords.
- We store what you publish — files, versions, sharing settings — because hosting it is the product.
- We keep an activity log for every artifact (who opened it when we know who they are, when, from roughly where, on what device). People who manage the artifact can see it. This is a feature, and it applies to you when you open somebody else's artifact too.
- The public pages and the artifact viewer run no analytics, no advertising and no third-party tracking. Neither does the dashboard. An artifact somebody publishes can contain its own scripts; that is up to its publisher.
- We do not sell personal data, share it with advertisers, or use it to train AI models.
Who is responsible
rtfx.pro is operated by Yogev Gabrielovitch, an individual sole proprietor based in Israel. Write to privacy@rtfx.pro with any privacy question, request or complaint. A postal address is available on request.
For your account, sign-in, security, billing and support we decide how and why data is processed (we are the "controller"). For the content customers publish — and the personal data inside it — the customer who publishes it decides what goes in and who sees it; we host it on their instructions. If you reached an artifact through somebody's link, they chose to share it with you, and they can see that you opened it.
This policy covers the hosted service at rtfx.pro. Self-hosted copies of the open-source software are run by their own operators under their own policies.
What we collect
| What | Details |
|---|---|
| Identity and workspaces | Email address; optional display name; role and status; the workspaces you belong to, their names and addresses; who invited you and when; when you were last active. It comes from you — or from a workspace owner who adds you, or somebody who shares an artifact with your address before you ever sign in. |
| What you publish | The files and their contents (stored in Cloudflare R2); title, description, address, size, version notes and who published each version and when. |
| Sharing settings | The email addresses an artifact is shared with and their role (viewer or editor); share links — stored only as a hash — with their name, creator, expiry, revocation and last use. |
| Activity log (view log) | For each open of an artifact: the artifact, version and file; time and outcome; your email if you are signed in (including when you came through a share link); which share link was used; IP address; the approximate country, region and city Cloudflare derives from it; device type, operating system and browser, and the browser's User-Agent text (up to 300 characters); the referring page (up to 500 characters). Link previews built by chat and social apps, and attempts to use an expired or revoked link, are logged too. Repeated opens of the same share link from the same IP address within a few minutes produce one entry. A log entry shows that a page was loaded — not that a person read it. |
| Chat | Messages written in an artifact's chat, with the author's email where known, their role and the version they were viewing. |
| Sign-in and integrations | One-time codes and magic links (stored hashed), attempts and expiry; API tokens (stored hashed) with their name, scopes and dates; the apps you connect over OAuth (such as Claude) and their authorisations; short-lived upload links. |
| Email delivery log | For every email we send — sign-in codes, invitations, share and read notices, access requests — the recipient, the kind of message, whether the sending provider accepted it or the send failed, and when. Not the message itself. |
| Billing | When you buy a plan we send your email and workspace id to Lemon Squeezy's checkout. From its notifications we store the resulting plan and a record that the notification was processed. We do not store card details, or Lemon Squeezy's customer or subscription ids. |
| Contact and operations | Messages you send through the contact form or by email; notes and an audit trail of actions taken by our administrators; rate-limit counters (hourly counts keyed by a hash of an email or IP address); and short technical logs from the platform. |
We do not collect passwords (there are none) or payment-card details (Lemon Squeezy handles payment). The product does not read your artifacts' contents for analytics, advertising or profiling; people with infrastructure access could technically reach stored files when that is needed to operate, secure or troubleshoot the service.
Why we process it
Where EU or UK data-protection law applies, these are our legal bases:
- To provide the service you signed up for (contract): your account, hosting what you publish, sharing it as you instruct, workspaces, and the plan you bought.
- Legitimate interests: verifying and admitting the people an artifact is shared with, sending them the invitations and notices that sharing involves, the activity log (people who share something need to know who opened it and to spot a leaked link), keeping accounts and the service secure, preventing abuse, fixing problems, and answering messages. We keep the activity log's IP addresses out of view after 90 days (see retention) because location and device are rarely needed after that.
- Legal obligations: where a law requires us to keep or disclose something.
Where we host personal data inside a customer's content, we act on that customer's instructions, and the customer is responsible for having a lawful basis to publish and share it.
What you have to give us
An email address is needed to have an account or to open something shared with you by name; without it we cannot sign you in. Content is needed only if you want us to host it. Display names, chat messages and contact-form messages are optional. Payment details go to Lemon Squeezy, not to us. Some technical data (such as your IP address) is unavoidable when your browser talks to any website.
Where data is processed
The operator is in Israel, which the European Commission recognises as providing adequate protection for personal data. Our service providers are based in the United States and process data on their global networks, so your data may be handled in the US and other countries. Where EU or UK law requires it, those transfers rely on the safeguards in the providers' data-processing terms, such as standard contractual clauses. Write to privacy@rtfx.pro for details of the safeguards that apply.
How long we keep it
- Artifacts stay until they are deleted. On the Free plan, each new publish keeps the files of the latest five versions and removes older versions' files (their notes and dates stay). Pro and Team keep every version.
- Deleting an artifact removes its files, versions, sharing settings, share links and activity log, and then erases its chat (if that last step fails, the chat can remain until we clear it). It does not remove entries about it in the email delivery log or the administrators' audit trail.
- Activity log entries stay until the artifact is deleted. IP addresses older than 90 days are no longer shown to anyone and are erased from storage in batches as the artifact keeps being used — so on an artifact nobody opens any more, an old IP address can stay in storage (unseen) until the artifact is deleted.
- Removing you from one workspace removes only that membership. Removing you from the service removes all your memberships and the artifacts shared with you by name, and revokes your API tokens. Neither does by itself delete your personal workspace, what you published or past activity — ask us at privacy@rtfx.pro to close your account and delete those.
- Sign-in codes work for 15 minutes; upload links for 30 minutes; connected-app access for an hour at a time, renewable for 30 days. Expired or revoked credentials stop working immediately, but their records are kept.
- Email delivery log, contact messages, audit trail and billing records are kept while the service runs, for security, support, accounting and disputes. Rate-limit counters expire after their hour and are removed during later checks.
Cloudflare and our other providers keep their own operational logs under their own terms.
Your rights
Depending on where you live, you can ask us for a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, or for a portable copy. Israeli law gives you rights to see and correct information held about you. Much of it you can do yourself: delete an artifact, revoke a token, or change who something is shared with.
For anything else, write to privacy@rtfx.pro. We may need to confirm it is you, and we will explain any legal reason we cannot do all of what you ask. If the data is inside content another customer published, we may need to involve them. You can also complain to Israel's Privacy Protection Authority or, in the EU or UK, to your local data-protection authority.
Security
- Every artifact is private when published, and access is checked on every request.
- Artifact files are served from a separate address (
a.rtfx.pro), so uploaded HTML cannot run alongside the dashboard or the API. - Sign-in uses one-time email codes instead of passwords; API tokens, share links and sign-in codes are stored only as hashes; connections use HTTPS.
No system is perfectly secure. Report a security problem to privacy@rtfx.pro (see also the repository's security policy) rather than testing it further. If a breach affects your personal data, we will notify you and the authorities where the law requires it.
Age
rtfx.pro is a tool for work and is not meant for children. You must be at least 16 to create an account. We do not verify ages; if you believe a child has an account, tell us at privacy@rtfx.pro and we will remove it.
Automated decisions
The service automatically checks sign-in, permissions, rate limits and plan limits — for example, refusing a publish over your plan's limit. We do not use automated decision-making or profiling that has legal or similarly significant effects on you.
Changes to this policy
The date at the top shows when this policy last changed. Before a material change — new kinds of data, a new purpose or a new provider — takes effect, we will tell account holders by email or in the dashboard. We will not start using your data for something new and tell you afterwards.