1. Scope and operator
This policy applies to the Datagram Prog mobile application and the Datagram Prog pages on amir-os.com. The operator is Amir Abu Tabak, operating under Amir‑OS Group. Privacy and support contact: amirabotbk@gmail.com.
Datagram Prog is a developer-tool application. Many data flows occur only because the user deliberately connects to a server, repository, API or database they choose. Mentioning a feature here does not mean that every user uses it or that all listed data is collected automatically.
2. Local workspace and on-device data
The local file workspace, code snippets, imported files, Git working copies and local SQLite databases are stored in the app’s device storage unless the user chooses a function that transfers or synchronizes them. SQLite databases created in Database Studio stay in the local Datagram Prog workspace.
Local compiler history is designed to store execution metadata such as language, time, exit status and size information rather than the user’s source code or standard output. API Client history stores request metadata rather than authorization headers or request bodies.
3. Credentials and secure storage
Saved connection profiles can contain SSH passwords, SSH private keys and passphrases, Git HTTPS tokens, and remote database credentials. Datagram Prog stores these sensitive profile values using platform secure storage rather than the ordinary project workspace.
SSH private keys are centralized in the app’s Key Vault so the same key can be referenced by multiple profiles without creating unnecessary workspace copies. Known Hosts stores SSH server fingerprints and blocks a changed fingerprint until the previous trust is explicitly removed.
4. SSH, SFTP, FTP and tunnel connections
When you connect to a host, the device sends the connection information and the data required by that protocol directly to the server you configured. SSH and SFTP are encrypted protocols. Plain FTP does not encrypt the protocol traffic and is explicitly identified in the app; SFTP should be preferred where available.
SSH tunnels forward traffic according to the profile you configure. In the current release, local and Dynamic SOCKS5 listeners are restricted to loopback, and remote forwarding requests remote loopback. Mobile operating-system background suspension can interrupt live tunnels.
5. Cloud Compiler
Source code and optional standard input are sent to the Datagram Prog Cloud Compiler only when the user presses Run. The public runner issues short-lived signed sessions; the free plan uses a pseudonymous installation-derived subject so server-side usage limits can be enforced without placing a reusable runner secret in the application binary.
Each run is executed in a short-lived isolated container selected by the server. Job containers run without network access, use a read-only root filesystem, run as a non-root user, and have bounded CPU, memory, process count, input, output and execution time. Temporary source input is removed after the run.
The runner records limited usage information needed to enforce daily, short-window and concurrency limits, such as a pseudonymous subject, plan and execution timestamp. The current free allowance is shown in the app and can change with the service policy. Compiler results are returned to the device.
6. Database Studio
SQLite files are local to the app workspace. For PostgreSQL and MySQL, the device connects directly to the database host that you configure; Amir‑OS Cloud Compiler is not a database proxy and does not receive those database queries merely because Database Studio is used.
Remote profiles default to TLS and read-only safety. Server credentials are stored in platform secure storage. If a user disables TLS for an intentionally local or tunneled server, transport security depends on that network or tunnel. SQL results are displayed on the device. CSV exports, when available, are saved into the local Datagram Prog workspace.
7. Git and API Client
Git HTTPS credentials are stored separately in secure storage and are not embedded into remote URLs. The current Git Client accepts clean HTTPS remotes for network operations. Repository data is exchanged with the Git host selected by the user.
API Client sends the method, URL, headers and optional body that the user enters to the selected endpoint. Remote cleartext HTTP is blocked by default; local development addresses can use HTTP. API history is metadata-oriented and is not intended to retain authorization headers or request bodies.
8. Premium subscriptions and store verification
When Premium products are available, purchases are processed by Apple or Google. Amir‑OS does not receive payment-card credentials. To verify an entitlement, the app can send the store’s server-verification proof or purchase token to the entitlement service. The service validates eligible products and can issue a short-lived runner token. Store proofs are not copied into the runner token.
The exact available plan, price, billing period, renewal terms and trial or promotion are those displayed by the applicable app store before purchase.
9. Website, infrastructure and operational data
The product website does not require an account and does not intentionally include advertising trackers. Web hosting and network infrastructure necessarily process connection information such as IP address, request path and security events to deliver and protect the service. Cloud services can also produce operational logs needed to diagnose failures, abuse or security incidents.
We do not claim that internet infrastructure keeps zero logs or that every third-party server a user connects to follows this policy. A server, API, Git provider or database chosen by the user is governed by that operator’s own policies.
10. Retention and security
Local app data remains on the device until the user removes it, removes the app, or the operating system applies its storage behavior, subject to backups the user controls. Cloud usage/security records are retained only as reasonably necessary for service limits, operations, fraud prevention, security and legal obligations. The runner usage database is designed to keep short operational windows rather than source-code archives.
We use HTTPS for the public runner and this website, secure-storage APIs for sensitive mobile profiles, and restricted administrative access. No system can guarantee absolute security.
11. Privacy rights
Depending on your location and applicable law, you may have rights to access, correct, delete, restrict or object to certain processing, receive portable data, or withdraw consent where consent is the legal basis. EU/EEA users may have GDPR rights and the right to complain to a competent supervisory authority. U.S. rights differ by state. Legal exceptions and proportionate identity verification may apply.
12. Contact and changes
For a privacy request, email amirabotbk@gmail.com or use the Datagram Prog contact page. Identify Datagram Prog and the type of request, but do not include unnecessary secrets.
This policy may be updated as features, service providers, store products or legal requirements change. The date at the top identifies this version. Mandatory local law prevails where it provides greater rights.