Hojago Privacy Policy
This policy explains what information Hojago handles, where it lives, and why. It covers the Hojago hosted service (the Central Coordinator at api.hojago.com), the Hojago apps (the Hojago mobile app, the Hojago Station iPad app, and the web release pages), the Hojago site server that a customer runs on its own hardware, and this website.
1. Your documents stay on your own server
Print jobs and their contents (“Documents”) are captured and held on the customer’s own Hojago site server until they are released, printed, or expire. Geeksblock’s hosted service never receives or stores Document contents. It handles only the coordination information described below.
2. Who is responsible for what
- Hojago is licensed to organizations such as schools, parishes, and businesses. For the people who print at a customer organization, the organization is the data controller; Geeksblock processes their information only to provide Hojago to that organization, under its agreement with us.
- For our own administrator accounts, billing, support, and this website, Geeksblock is the controller, and this policy describes what we do.
3. What the hosted service handles
- Administrator accounts — name, work email, organization, role, and sign-in records. Where a password is used it is stored only as a salted hash; single sign-on customers keep their credentials with their own identity provider.
- People who print— a username or work email, a display name, and page counters. Usernames may be imported from the organization’s directory or created by an administrator. Where the organization uses release PINs, the PIN is stored encrypted (AES-256), never in plain text, so the office can look one up for a person who forgot it.
- Print-job coordination metadata — a job identifier, the document name, page count, copies, color mode, size, timestamps, status, cost, and the site and printer involved. This is what lets a person see their own held jobs and release one at the printer they are standing at. Document contents are not included (Section 1).
- Release records — who released or discarded which job, at which printer, and when. Organizations use these for accountability and cost tracking.
- Devices — for an enrolled Hojago Station iPad: a device name, the printer it is bound to, and a last-seen time. Its device credential is stored only as a hash. The station keeps nothing about the person who signed in once they are done.
- Service and security logs — request identifiers, IP address, device and browser type, timing, and error details, used to keep the service secure and reliable. Passwords, PINs, and session tokens are never written to logs.
- This website — if you request a demo, the details you enter in the form (name, organization, email, message).
Hojago contains no advertising and no analytics or tracking SDKs. Sign-in uses strictly necessary session cookies only.
4. How we use information
To operate Hojago: authenticate administrators and people who print; show a person their own held jobs and release them at the printer they are standing at; keep an organization’s usage and cost records; send the operational notifications and usage reports an administrator has asked for; provide support; keep the service secure; bill customers on paid plans; and meet legal obligations. We do not sell personal information, and we never use customer data, Documents, or student data for advertising or to train models.
5. Who we share it with
- Hosting — the hosted service runs on DigitalOcean in the United States (New York).
- Email delivery — for account, notification, and report emails.
- Legal and safety — when the law requires it, or to protect the rights, safety, or integrity of the service.
- A successor — if Geeksblock is acquired or merges, under this same policy.
We share customer data with no one else.
6. Security
Traffic is encrypted in transit (TLS). Passwords, API keys, session tokens, and device credentials are stored as hashes; release PINs are stored encrypted. Access to the hosted service is role-based and every change is logged. Hojago software is code-signed. Customers are responsible for securing their own site server, network, printers, and the Documents held there.
7. Retention
Coordination metadata and release records are kept while the customer’s organization is active on Hojago and are deleted with the organization’s account. Diagnostic error records are purged on a rolling schedule. Documents never reach our service; they are removed from the customer’s site server on release, print, or expiry, as the customer configures. An organization can ask us to delete its data at any time.
8. Schools and student data
Where a school uses Hojago, Geeksblock acts as the school’s service provider (a “school official” under FERPA) and uses student information only to provide Hojago to the school. We do not use it for any other purpose and do not disclose it except as described above. Schools are responsible for their own notices and consents.
9. Your choices
People who print should send access, correction, or deletion requests to their organization, which controls that data; we help organizations respond. For information Geeksblock controls (Section 2), contact us below; we respond within 30 days. Hojago Station iPads and the web release pages keep nothing about you once you sign out or your session ends.
10. Location
The hosted service is operated in the United States. If you use Hojago from elsewhere, your information is processed in the United States.
11. Changes
When we change this policy we update the effective date above and, for material changes, notify customer administrators. Every published version is archived and fingerprinted (SHA-256) in Geeksblock’s records.
12. Contact
Geeksblock LLC · 11455 SW 40th St #154, Miami, FL 33165 · privacy@geeksblock.com · +1 786 305 4635 · geeksblock.com
Canonical, fingerprinted copy: ks.geeksblock.com/legal/printflow/privacy-policy. Questions about support? See Support.