Terms of use

You may play the built-in sample or choose photos you have the right to use. You keep your rights in those photos. This project claims no rights in them beyond the processing needed for the local game or the optional AI analysis you trigger by selecting a file through the disclosed automatic-upload control, or hosting a puzzle you choose to publish.

Publish only photos you have permission to share. Publishing stores a photo until you delete the puzzle. Anyone with its link can view, download, and forward it. Sharing a link reuses the stored photo and does not create one copy per recipient. Deleting a puzzle revokes its link and removes its server data; it cannot revoke copies others already hold. Keep your own backup of important photos.

• Do not use images you lack permission to process.
• Do not submit illegal, infringing, or malicious material.
• Do not bypass validation, disrupt the service, or abuse the model endpoint.
• Confirm that you have the right to send a photo to the configured vision provider before using automatic upload.
• Prefer the fully local mode for photos containing sensitive people or information.

Automatic AI analysis requires a test token and server-side configuration supplied by the operator. On unlock, a same-origin readiness request checks the token and provider configuration without a photo, model call, or analysis-quota use. After unlock, the automatic upload control explains that selecting a file immediately triggers that processing. A valid cache builds the game locally; without one, the app uploads one photo copy. The server may retry qwen3-vl-plus once on selected transient failures, sending that same copy at most twice. Both attempts may incur provider charges; each has a 4,096-token output cap. The model returns subject candidates only; code selects one to three non-overlapping targets and installs a game without manual boxes or per-box review. Valid coordinates do not prove recognition accuracy.

Models can fail, time out, find too few usable subjects, or return invalid regions. The app rejects invalid results and keeps the current level, but it does not promise model availability or accuracy. Advanced manual selection remains an optional local mode that does not upload the photo. The operator's relationship with the configured provider governs provider terms and costs. The provider's data location and retention period have not been independently verified; they depend on actual configuration and provider policies.

Completion offers two local downloads: the orientation-corrected full-resolution working photo and a memory card. The sample uses a fixed caption; other photos use a neutral poetic line without unverified model drafts or subject labels. Downloads make no new model request and do not post directly to social platforms.

Manual mode needs only one usable subject box. Games may use bundled independent assets as distractors; these do not come from this upload or its inference request. Their individual sources and licenses remain unverified, so asset provenance acceptance is incomplete.

The software is provided “as is” and “as available,” without a promise that it will be uninterrupted, error-free, or fit for a particular purpose. Keep original backups of important photos. Do not use the game or model output for safety, identity, medical, legal, or other high-impact decisions. Source-code liability is governed by the root LICENSE, which limits MkSaaS's liability to a refund of the license fee.

The repository is governed by the MkSaaS License in the root LICENSE file, not the MIT License. It permits a licensee to build end products, but prohibits redistributing MkSaaS components or templates as a standalone template and prohibits a competing SaaS starter kit. It also permits revocation for material breach and is governed by Swiss law. If this summary differs from the license, the LICENSE text controls.

The source license does not change your rights in your own photos.

This repository is a deployable MVP and does not name the final operator, contact, or governing law. A public deployer must provide those details and update these terms and the privacy notice before adding accounts, payments, analytics, storage, or other processing.