SwishrJobs
§

Privacy

Short, because the service collects very little.

What is stored

  • The job request: the capability requested, the requester name you supply, and the validated inputs.
  • The quote and the acceptance, including the name supplied as the authorizer.
  • The deliverable, its verification result, and the job history.
  • An audit log of consequential actions: who, what, when, and the outcome.
  • When payment is configured, a payment ledger: the payer address, the amount, the network, the nonce, the settlement transaction hash, and the confirmation evidence. No key that can spend funds is stored.

What is not stored

  • No passwords, because there are no accounts.
  • No card, bank, or invoice data. When payment is configured, an x402 payment carries only a public blockchain address, a signature, and a nonce; no name, card, or billing address is collected.
  • No credentials you might paste into an input. Inputs are validated against a declared shape, and unexpected fields are rejected rather than kept.
  • No third-party analytics or advertising trackers on this site.

Where it is stored

Job records and the audit log are files on the server that ran the job. They are not replicated to a database. Retention is currently indefinite because no deletion policy is implemented; that is a known gap, not a promise.

Do not submit personal data

The service is designed for technical work: code, structured data, documents. Do not submit personal data or anything confidential. The service is not built to protect it.

Contact

Open an issue at github.com/Mahmoudaly187/swishrjobs.