Privacy Policy — Pajtim

Plain-language summary: Pajtim has no account, cloud backend, advertising, analytics, or developer-operated data endpoint. Settlement details remain encrypted on each participating device and move only between the two nearby devices that their users deliberately pair and confirm.

1. Who provides Pajtim

Pajtim: Fair Settlement is provided by Saifullah Ahad (“we”, “us”). Website: https://saifullah.ai. Privacy and safety contact: [email protected].

2. What Pajtim does

Pajtim helps exactly two consenting adults describe several property, service, or obligation issues, privately place 100 priority points across them, and calculate one settlement proposal on both devices. Neither list is revealed until both lists are cryptographically committed. The participants may add a consenting witness mark and sign an identical record after both devices confirm the same result hash.

Pajtim is an arithmetic coordination tool. It does not provide legal advice, determine rights, process payments, or decide whether a record is enforceable.

3. Information stored on your device

• Participant and session details: party display names, device public keys and fingerprints, session/revision identifiers, pairing confirmation, and connection state.
• Settlement content: issue titles, descriptions, divisibility choices, optional photographs and voice notes, optional consenting witness name/mark, and optional balancing-payment text.
• Private priorities and evidence: draft and sealed 100-point valuations, random nonces, commitments, reveals, calculated allocations, signatures, and final record hash.
• Local settings: theme, limited-preview and reduced-motion choices, plus optional App Lock configuration. An App PIN is retained only as a salted SHA-256 hash; the plain PIN is not stored.

Complete session snapshots are stored as AES-256-GCM ciphertext in app-private storage using a key protected by Android Keystore. Issue media is kept in app-private internal storage. Android cloud backup and device-transfer extraction are disabled for Pajtim.

4. Permissions and system features

• RECORD_AUDIO is requested only if the setup party chooses to record an issue voice note. A denied permission can remain denied; all other settlement functions continue.
• INTERNET carries an encrypted raw TCP connection to the specific nearby phone chosen by the participants. Pajtim has no public-internet service or developer endpoint; Android does not offer a separate local-network-only permission.
• CHANGE_WIFI_MULTICAST_STATE supports short-lived Android Network Service Discovery on the same Wi-Fi network or hotspot.
• USE_BIOMETRIC and legacy USE_FINGERPRINT allow optional fingerprint or face App Lock. Android performs the biometric check and tells Pajtim only whether it succeeded; Pajtim never receives biometric data and does not accept the device credential as a fallback.

Pajtim does not request camera permission. When a participant chooses to photograph an issue, it opens the device's camera app and provides a scoped file location for one full-resolution result. Pajtim requests no broad photo-library, storage, contacts, location, notification, phone, SMS, or calendar access.

5. Nearby transfer and recipients

At bootstrap, the two chosen devices exchange a short session code, the chosen party name, public identity key, and ephemeral key-agreement material. The users compare a derived phrase aloud before continuing. All later frames are encrypted and signed, tied to the confirmed session and revision, and protected against replay, alteration, and out-of-order delivery.

Photos and audio are transferred only to the confirmed peer in bounded encrypted chunks. The developer does not receive session content, attachments, identifiers, telemetry, or crash logs. The only ordinary recipient of settlement data is the other participant whom the user pairs with and explicitly confirms.

6. Retention, deletion, and interrupted sessions

A session remains on each participant's device until that device's user deletes it, clears Pajtim's app data, or removes the app. Deleting a record removes its encrypted database row and associated app-private photos, audio, and witness mark from that device. Because there is no server, deletion on one phone cannot erase the separate copy already held by the other participant or any PDF that either person exported.

Ending before signature clears draft points, valuation secrets/reveals, unsigned results, signatures, and final hash; non-revealing commitment hashes may remain as interruption evidence. Revising the issue list invalidates the old valuation and signature material and requires both people to commit again.

7. Exports, feedback, and external apps

A signed PDF is created in temporary app cache and leaves Pajtim only when a user chooses a recipient through Android's share sheet. The receiving app and recipient control any copy sent to them.

Feedback and safety-contact actions open the user's chosen email app with a mailto: address. Pajtim does not send email itself. If the user chooses to send a message, their email provider and the developer receive only what that user includes, under their respective privacy practices.

8. Safety and children

Pajtim is intended only for consenting adults and is not directed to children. It refuses sessions involving violence, abuse, threats, coercion, a child's safety or sexual exploitation, criminal matters, inheritance shares, or another person's rights or property. Every shared issue has a Flag and end session action.

Child sexual abuse and exploitation (CSAE), including child sexual abuse material (CSAM), is prohibited. See the separate Pajtim Child Safety Standards for reporting and response information.

9. Service providers and international processing

Pajtim contains no advertising, analytics, social-media, crash-reporting, billing, cloud-storage, authentication, or push-notification SDK. There is no developer-operated server and therefore no routine developer transfer or international processing of settlement data. If a user sends an email or shares a PDF, the chosen external provider may process that user-directed content in other countries under its own terms.

10. Security limits

Pajtim uses Android Keystore-backed keys, AES-GCM encrypted local records, ephemeral ECDH session keys, signed frames, commitment-before-reveal, independent calculation, and two result signatures. No system can guarantee absolute security. A confirmed participant can read the information shared with them, can photograph the screen, and can retain or redistribute an exported record, so both people should include only information needed for the settlement.

11. Changes and contact

If Pajtim's behavior or legal requirements change, this page will be updated before the related release and will show a revised effective date. The current policy remains at https://privacy.saifullah.ai/pajtim.html.

Developer: Saifullah Ahad
Email: [email protected]
Website: https://saifullah.ai
Location: Dhaka, Bangladesh