Publisher: XLII Studio
Product: mOck - AI Driven Metadata Builder
Effective date: 30 July 2026
1. What mOck does
mOck currently works with the Shutterstock Contributor page to make photo submission easier. It helps contributors generate and enter metadata such as descriptions, keywords, categories and image type within that workflow.
2. Data mOck handles
To provide its core functionality, mOck may access information visible in supported contributor pages, including image previews, asset identifiers, existing metadata fields and metadata generated for those assets.
mOck also stores extension configuration locally in the browser. Depending on your configuration, this can include provider settings, model names, cache data and credentials supplied by you.
3. How data is used
Page and image content is used only to perform the user-requested metadata generation and workflow actions. XLII Studio does not operate an intermediary service that receives or stores your contributor images, generated metadata or AI requests.
4. AI providers and custom endpoints
When you choose a remote AI provider or remote user-configured endpoint, mOck sends the image/content required for metadata generation directly to that provider or endpoint. Third-party providers process data under their own terms and privacy policies.
When you configure a local provider such as Ollama or LM Studio, supported requests can remain on your own machine. A 9Router endpoint may be local or remote depending on the URL you configure.
5. Local storage and cache
mOck uses browser extension storage for settings and workflow configuration. XLII Studio does not maintain a separate user account or cloud database for mOck. You can remove locally stored extension data by clearing the extension data or uninstalling mOck.
6. API credentials
API keys or access tokens you enter are stored in browser extension storage so mOck can connect to your selected provider. They are used only for the provider connection you configure.
7. Sale, advertising and profiling
XLII Studio does not sell mOck user data. mOck does not use contributor content or AI requests for personalized advertising, retargeting, creditworthiness decisions or unrelated profiling.
8. Human access
Because XLII Studio does not operate an intermediary image/AI-processing backend for mOck, XLII Studio does not routinely receive or provide human access to your contributor images or AI requests.
9. Security
Remote endpoints containing user data should use secure HTTPS connections. Localhost connections may use local HTTP when required by software running on your own machine.
10. Chrome Web Store Limited Use
mOck's use of information received from Chrome APIs and website content is limited to providing and improving its single user-facing purpose: generating, organizing and entering image metadata in a supported contributor workflow.
11. Changes
This policy may be updated when mOck's functionality or data practices change. The effective date will be updated when material changes are made.
12. Contact
For privacy questions, contact support@xlii.studio.