Terms of service (draft)

1. Who provides the service

4keys is provided by [LEGAL ENTITY NAME], registered at [REGISTERED ADDRESS] under business registration number [BUSINESS REGISTRATION NUMBER], represented by [REPRESENTATIVE NAME]. Contact: [CONTACT EMAIL].

2. Access is by invitation

There is no sign-up form and no self-serve account creation. An account exists only after the operator invites an identity through Cloudflare Access; the first authenticated request creates the account record.

The operator can disable an account, which blocks every authenticated request from it. The stored account record is not removed by that action.

3. Your content stays yours

You keep whatever rights you already hold in the text you write, the media you upload, and the stories you publish. Using the service grants the operator only what running it requires: storing your content, serving it back to you, sending the direction text you submit to the model that carries it out, and serving a story you chose to publish to its readers.

You are responsible for having the right to upload and publish what you upload and publish.

4. Publishing makes a story public

Publishing a story writes an immutable snapshot and serves it to anyone who has the link. It is not private, not password-protected, and not restricted to invited people. Treat publication as making the story readable by the whole internet.

Revoking a publication stops it being served to new readers straight away. A copy a reader already fetched, or one held in an intermediate cache, may remain readable for up to five minutes afterwards. Revocation changes the stored status; the snapshot object itself is kept.

A reporting endpoint and an operator takedown route are both built, and both ship switched off. While they are off there is no in-product way for a third party to report a published story: the only channel is the contact on the support page, and removal means the owner revoking the story or the operator acting directly on the stored data. When the report path is enabled, a report records the story's address, one of seven fixed reasons, the day, and a one-way key derived from the reporter's network address — no message and no contact detail, because there is no field that could carry one.

[REVIEWER: decide whether the reporting and takedown paths are enabled before this document is published, and whether this section may promise a response time. It may not today.]

5. Limits as they are enforced

These are the limits the service actually applies. Exceeding one is refused at the moment of the request, not billed.

• 25 MiB per uploaded file.
• 200 uploaded files per project, and 1,000 per account.
• 2 GiB of uploaded media in total per account.
• 50 projects per account.
• 50 published stories active at once per account.
• 3 direction jobs running at once and 20 per day per account, unless the operator raises it for that account.
• Public reads and authenticated writes are rate limited.

6. What you may not do

You may not use 4keys to publish content you have no right to publish, to attack the service or its other users, to work around the limits above, or to attempt to read another account's projects, media, or unpublished work.

[REVIEWER: the categories of prohibited content, and who decides that something falls into one, are a policy decision the operator has not made.]

7. Deletion, and what it does not cover

Deleting a project hides it immediately, revokes any story it had published, and queues its content and media for permanent removal by a daily sweep 30 days later. That removal is final: uploaded media is not backed up.

There is no route that deletes a single uploaded file, no route that deletes your account, and no retention rule on stored jobs or audit records. The privacy draft states the same limits in more detail.

8. Availability

There is no uptime commitment, no support response time, and no service credit. The service is pre-production: it may be interrupted, changed, or withdrawn without notice, and features may be turned off.

Keep your own copy of anything you cannot afford to lose.

9. AI-assisted changes

A direction you submit is carried out by an AI model reached through a broker, or on a machine the operator runs. The result is a proposal you review, apply, or undo; nothing is applied to your project without your action.

Model output can be wrong. You are responsible for what you keep and publish.

10. Liability and governing law

[REVIEWER: limitation of liability, warranty disclaimer, and indemnity are omitted from this draft rather than guessed. They must be drafted for the operator's jurisdiction.]

These terms are governed by [GOVERNING LAW] and take effect on [EFFECTIVE DATE], once reviewed.