An App Blocker for Teams: A Benefit, Not a Punishment
Exploratory proposal. Organization sponsorship is not available. Pro is not publicly available; this is not a team checkout.
How sponsorship could work
The proposed app blocker for teams would be a company-paid benefit employees choose to use. Organization sponsorship is still exploratory; there is nothing to buy or enrol employees in today.
- A company would choose how many memberships it could sponsor.
- It would share invitations with employees who want the benefit.
- Employees would choose whether to join and how to use Zomok on their own phones.
Jump to interest registration. Registration is not open yet. There is no payment or commitment.
Help with a boundary employees choose
Someone might want social apps unavailable during a writing task and still need to show a colleague a saved post at lunch. A useful benefit would let that person choose the boundary and the exception. It would not make their manager the person who grants access.
This is a hypothetical example, not a promised productivity result or an account of a customer using team features. People may also decide they do not want app blocking. Participation should remain voluntary.
An employee digital wellbeing benefit should not become a punishment for enjoying a phone or taking a break. A company considering the idea should explain that declining the invitation would not create an activity report or a score.
The company pays; employees stay in control
The intended offering is sponsorship of personal Pro memberships. A company would set the number it is willing to sponsor and share invitations. Employees would decide whether to join and choose their own apps, hours and temporary-access preferences.
This does not describe implemented invitation codes, organization accounts or employee administration. Those would need design and verification before a launch. Pro availability and organization sponsorship are separate questions; neither is a current team service.
Free is available for personal Android use. iOS is planned. A proposed employer benefit must not assume that future platform support or all planned Pro controls already exist.
Manage memberships rather than phone activity
Under the proposed model, the employer would manage sponsored places, invitations, enrolment and billing. It would know whether a sponsored place is occupied. It would not remotely choose an employee’s blocked apps or approve a personal access window.
The current proposal is billing for enrolled sponsored accounts rather than unused capacity. For example, if a company allowed up to twenty memberships and twelve people enrolled, the proposed billing basis would be those twelve accounts. That is an illustration, not a quote or finalized payment arrangement.
Organization prices, payment arrangements, eligibility and renewal or cancellation details are unfinalized. Reinstalling or changing phones should not create a second membership for the same person, but the actual transfer rules still need design. Do not assume an interest registration reserves a price.
What an employer would not receive
The proposed organization service would provide no employer access to apps used, personal app selections, unlock histories, browsing, messages, screen-time reports, productivity scores or individual phone-activity reports. Employers would administer sponsorship rather than observe the phone.
An invitation being accepted could show that a place is occupied. It would not tell a manager that the person opened Instagram at lunch. That distinction must be reflected in any eventual product and its privacy terms.
Sponsorship would still need membership and billing records. The interest form would collect contact details. “Without monitoring” is a boundary for employer activity access, not a claim that no information would be processed. The current Privacy Policy does not by itself establish the full data practices of an unbuilt organization service.
Questions a company should settle before offering it
Would employees have to use it? The proposed benefit is voluntary. It is outside the idea’s scope to enforce a manager’s phone policy or provide remote restrictions.
Would employees pay? The proposed sponsorship model puts membership payment with the company. There is no current employee checkout, company price or payment request.
What about someone who leaves? Sponsorship administration and the effect of ending a place need clear rules before launch. No account-removal or continued-entitlement promise is made here.
Can a company test a team account now? No organization service is available. Personal Free use on Android is separate from signing up a company. Nobody needs to buy an unavailable Pro plan to express interest.
Register interest when the form opens
The proposed form asks for three things: the number of employees you might sponsor, company name and an email for updates. The ranges are 1–5, 6–20, 21–50, 51–200 and 201+. Do not send an employee list or phone-activity information.
Submitting the eventual form would request occasional updates about Zomok for Teams only. It would not be a purchase, preorder, binding commitment, guaranteed early-access place or promise that sponsorship will be built. A working unsubscribe/removal route must be available before public collection begins.
Interest registration is not open yet. We are finishing the private signup and email service. This page is not currently accepting contact details.