Transparency Report
About this report
This report documents how CometFare is operated. It covers the volume and outcome of moderation activity, requests received for user data, the data the service retains, and the third parties that process it. It is published so that this information is a matter of public record rather than internal knowledge.
Figures are compiled per calendar year and published after the reporting period closes. Counts cover the reporting period; descriptive values reflect the state of the service on the update date shown above. Where a figure has not yet been compiled, this report states that rather than providing an estimate.
This report describes operational practice. Where it appears to conflict with the Terms of Service or the Privacy Policy, those documents are binding. Any such conflict is an error, and should be reported to the operator.
Who runs CometFare
CometFare is operated by a single individual. The service maintains no moderation department, retains no trust and safety vendor, and operates no on-call rotation. All reports, appeals, refunds, and incidents recorded in this report were handled by that individual. This context is relevant to the response times published below.
AI use
CometFare's use of AI splits in two, under opposite rules. In engineering it is used heavily, and this section sets out how. In art it is banned outright. Why one and not the other is explained below.
Neither is a feature of the product. AI is used to build CometFare. It does not run inside it. Nothing you write here is sent to a language model. There is no assistant, no automated moderation, no generated replies, and no summarising of your conversations. No user data is used to train any model, by CometFare or by any third party. The application servers hold no connection to any AI provider.
User content is never sent to an AI model.
Sector one: engineering
CometFare is written with AI assistance under human direction. AI writes code, reviews it, documents it, plans changes, and tracks down defects. It does not make product decisions, sign off its own output, or deploy anything. Every change is read and released by the operator.
Providers
Every AI system used to build CometFare comes from Anthropic, through Claude Code, its software engineering tool. No models from any other provider are used at any stage, including those of OpenAI, Google, and Meta, and no open-weight models run locally. Development runs under Anthropic's commercial API terms, which keep submitted content out of model training.
Models used
| Model | Identifier | Assigned role |
|---|---|---|
| Claude Fable | claude-fable-5-1 claude-fable-5 | Planning |
| Claude Opus | claude-opus-5-5 claude-opus-5 claude-opus-4-6 | Building, checking and fixing |
| Claude Sonnet | claude-sonnet-5-5 claude-sonnet-4-6 | Small changes |
Model responsibilities
Each model gets the kind of work it is best at. The harder the job, the more capable the model that handles it.
Extent of AI involvement in engineering
More than 50% of the codebase was produced with AI assistance. That covers the website, the backend service, and the desktop and mobile apps.
This is published because users are entitled to know how the software they rely on is made. AI assistance says how the code was drafted, not what standard it is held to. All of it is reviewed, tested, and released by the operator, who is accountable for whether it is correct and whether it is secure. A defect that arrives through AI-assisted work is the operator's responsibility on exactly the same terms as any other defect.
Sector two: art and visual assets
Generative AI is not used for any artwork on CometFare. No background, icon, texture, character, interface illustration, or promotional image on this service came out of an image model. The ban is absolute: no concept drafts, no reference material, no upscaling, outpainting, inpainting, or retouching, and no exception for assets nobody would ever see at full size.
Distinction
AI assistance holds up in engineering because code is functional and checkable. It either behaves correctly or it does not, that correctness can be tested, the person releasing it can read every line, and none of it claims to be an act of authorship. The claim made about a piece of code is that it works, and anyone can check that claim.
None of that carries over to art. Image generation models are built on the work of artists who were never asked, credited, or paid, and what comes out is presented as authorship while doing none of the work authorship consists of. No test exists that a generated image passes. That argument covers code and nothing else.
How the artwork is produced
All artwork on CometFare is made in Blender. Scenes are built, textured, lit, and composed by hand, then rendered to a finished image. Most production renders use Cycles, Blender's own path tracer. A smaller number were rendered with Octane, a third-party GPU renderer driven from inside Blender.
Verifying this. Blender stamps its own render metadata into the images it produces, and those fields survive in the full-quality source images this site serves: the .blend scene file, the date and duration of the render, the camera, and for path-traced images the Cycles sample count. An image model writes none of it, because there was no scene and no render to describe.
Two caveats if you check. Compressed copies can lose the metadata during conversion, so read a full-quality source. And Octane renders carry the Blender scene stamp without the Cycles sample fields, which means a different engine, not a missing render.
Moderation
Covers reports submitted through the in-app reporting flow.
Reports are submitted by users against a message, a profile, a habitat, or a reply, and are reviewed manually. Each report is recorded under one of ten categories. The breakdown below uses the application's own category names.
Outcomes
A closure with no action does not indicate a failure of the process. A substantial proportion of reports concern conduct that is disagreeable but permitted under the Terms, or duplicate a report on which action has already been taken. That figure is published separately rather than being consolidated into the other outcome figures.
Appeals
All suspensions may be appealed, including permanent suspensions. An appeal is reviewed by the same individual who issued the suspension. This is an acknowledged limitation of a single-operator service, and it is the reason the overturn rate is published rather than retained internally: it constitutes the only external measure of that process.
Legal and government requests
This section covers any demand from law enforcement, a court, a regulator, or a private party for user data or for the removal of content. A request is recorded on receipt, irrespective of whether it was subsequently complied with.
Handling procedure
- Valid legal process is required. An informal request for user data, including one made by email, does not meet that standard and is refused.
- Disclosure is limited to the narrowest set of data the request compels. Account data is not disclosed in full by default.
- The affected user is notified, unless a court has specifically prohibited notification.
- Where a request is judged to be overbroad or otherwise improper, it is contested before any disclosure is made.
A recorded count of zero is a substantive result rather than a placeholder. Where a period closes at zero, that zero is published, so that any later period in which it is not zero is evident by comparison.
What we store, and for how long
CometFare retains user content until it is deleted. The service operates no rolling expiry window for messages, and message records are not removed from the database on a schedule. Users for whom this is material should take it into account when deciding what to submit to the service.
Encryption limits
CometFare messages are not end-to-end encrypted. Traffic between a user's device and the service's servers is encrypted in transit, and the database is encrypted at rest by the hosting provider. Message content is nonetheless readable by the service, and therefore by the operator, and therefore by any party able to lawfully compel the operator to produce it.
This is stated directly because the alternative would be more damaging than the limitation itself: implying a degree of privacy that the architecture does not provide. Direct messages are private in the sense that other users cannot read them. They are not private from the service.
Who else your data touches
CometFare depends on external providers to operate. The following third parties process some portion of user data in the course of delivering the service. Each receives only the data its function requires, as set out beside it.
| Provider | Function | Data processed |
|---|---|---|
| Cloudflare | Hosting, network, and database | Substantially all data the service stores or serves |
| Paddle | Payments and subscriptions | Billing details and payment method. Card numbers are not received by CometFare |
| Resend | Outbound email, including sign-in codes | Email address and the contents of those messages |
| ImageKit | Image storage and delivery | Uploaded images, including avatars, attachments, and profile art |
| Agora | Voice and video calls | Call audio and video for the duration of a call |
| Spotify | Listening activity displayed on a profile | None unless the integration is connected by the user. Disconnecting ends processing |
The addition of a provider to this list constitutes a change to this report and is recorded with a date in the change log below.
Payments
Voyager is the paid tier of the service. Payments are processed by Paddle, which acts as merchant of record. Card details are entered on Paddle's infrastructure and are not received or stored by CometFare. The service holds the existence of a subscription, its billing cycles, and the outcome of each cycle.
Security incidents
Any incident that exposed user data, or that there is reason to believe may have done so, is recorded here with a date. This includes incidents identified internally and incidents with no confirmed impact. An empty log means no such incident has occurred. It does not mean incidents have gone unrecorded.
Security vulnerabilities should be reported to larisah@cometfare.com in advance of any public disclosure. Reports made in good faith will not be met with legal action.
Availability
Uptime is reported live rather than summarised once a year in this document. An annual average conveys little about the duration or impact of any individual outage. Current availability and recent incidents are published on the status page.
Changes to this report
Every revision of this report is recorded below, most recent first. Corrections are recorded on the same basis. Where a published figure is found to be inaccurate, the correction is entered as its own dated entry rather than being amended in place without record.
Version history
Every released version of CometFare, most recent first. A version ending in zero and zero is a major release: a new app, a rewritten engine, a new subsystem, or a change to how data is stored. Those are highlighted below, and each one ships with a new launcher artwork.
Dates are the date the work was released, not the date it was written.
No versions have been published yet.