Zerk / Studio notes / privacy

Privacy Notice

A direct account of the creative data flows visible in the current app.

Effective date · October 10, 2026English editionDevelopment draft
01 / ZERK

Who this notice covers

This notice describes the data handling visible in the current Zerk iOS project and marks facts that still need confirmation.

Zerk is a gesture-driven AI visual studio with local creative spaces and an optional cloud generation action. The operator responsible for personal information must be identified before publication: [CONFIRM LEGAL OPERATOR NAME, CONTACT ADDRESS AND PRIVACY CONTACT ROLE].

This notice addresses app use; it does not describe data practices of a future website deployment beyond these two static pages. These HTML pages contain no analytics, tracking scripts, cookies, or remote assets.

02 / ZERK

Information kept on your device

The current app stores studio names, a local studio directory, visual works and source images, generated results and video files, gesture paths and recipes, favorites, drafts, preferences, and local exhibition or critique text in app storage. A password verifier for a local studio is held using the iOS Keychain. The app does not use the studio password as a remote sign-in credential.

The observed app has no Zerk-operated cloud library or remote studio account, and it does not automatically upload your creative files while you browse or edit. This is the limited sense in which Zerk does not collect creative content into its own server. It does not mean that no data is stored on your device or sent to an AI provider when you choose cloud creation.

Importing a photo or video copies a working version into app storage. Local access, export, backup, and deletion may also be affected by your device settings and operating system. [CONFIRM DEVICE BACKUP BEHAVIOR AND ANY ADDITIONAL LOCAL DATA].

03 / ZERK

Photos, camera, microphone and files

The app accesses a photo or video when you choose it through a system picker or Files; it uses the camera when you choose camera capture. It requests camera permission when necessary. Export and sharing use device controls and the destinations you select.

Settings offers an optional short voice-note recording that uses microphone permission. The current code indicates local recording rather than AI upload. [CONFIRM VOICE-NOTE STORAGE LOCATION, RETENTION AND DELETION PATH].

You can change device permissions in system settings. Denying a permission limits the associated feature but does not prevent you from using unrelated local parts of the app.

04 / ZERK

What is sent for AI creation

When you choose Create for a cloud transformation, Zerk sends a resized working image, gesture information, an edit mask, and a direction guide to OpenRouter over HTTPS. Image requests also include a pseudonymous source-node identifier. A video request uses the selected source image and transformation instructions. OpenRouter routes requests to model providers; generated media is returned and saved into the active local studio. No AI upload is initiated merely by drawing, browsing, or editing a draft in the observed code.

The provider’s logging, retention, training use, subprocessors, geographic processing locations, deletion options, and any model-provider terms cannot be established from this project alone: [CONFIRM OPENROUTER AND MODEL-PROVIDER DATA PRACTICES, RETENTION, TRAINING USE AND PROCESSING COUNTRIES]. Avoid sending sensitive personal information or someone else’s image without appropriate permission.

05 / ZERK

Faces in images sent to AI

A photo you select may contain a recognizable face. If you choose cloud AI creation with that photo, the face pixels in the working image are sent to OpenRouter and may be processed by a model provider to produce your requested image or video. The observed Zerk code does not perform face recognition, identify the person, or create a faceprint or biometric template for a Zerk-operated database.

The AI provider receives the selected image for processing, so a blanket claim that no user data is collected would be inaccurate. The app’s current requests do not enforce zero data retention or prohibit provider data collection; account-level settings and the applicable model providers’ practices have not been verified. [CONFIRM FACE-IMAGE HANDLING, PROVIDER RETENTION AND TRAINING SETTINGS].

Use images of other people only when you have the necessary permission, especially when a face is visible.

06 / ZERK

Why information is used

Local information supports studio access, the creative workspace, saving and reopening work, branching, export, and user preferences. Information sent for cloud creation is used to request and return the image or video result that you choose to generate. If you email support, the information in your message is used to handle your request.

Any additional purposes, such as diagnostics, measurement, fraud prevention, or marketing, require separate verification and disclosure before publication: [CONFIRM ANY ADDITIONAL DATA USES].

07 / ZERK

Service providers and sharing

The observed cloud AI action discloses the working image and creation instructions to OpenRouter. The provider may involve model providers to complete the request. If you use the device share sheet, you choose the receiving app or person, whose privacy practices then apply. We cannot confirm from source inspection whether other production services receive data: [CONFIRM ALL SDKs, SERVICE PROVIDERS AND DISCLOSURES].

The operator must confirm whether data is sold, shared for cross-context behavioral advertising, or used for targeted advertising before publishing a California-specific disclosure: [CONFIRM CALIFORNIA SALE, SHARING AND SENSITIVE-DATA PRACTICES].

08 / ZERK

International processing

Cloud AI processing can involve service providers in other countries. The actual countries, provider roles, onward transfers, and safeguards must be verified: [CONFIRM PROCESSING COUNTRIES AND CROSS-BORDER SAFEGUARDS]. Depending on where you live and which laws apply, additional transfer notices or protections may be required.

09 / ZERK

Retention and deletion

The app keeps a local studio until you remove its content or delete the studio. Items moved to Recently Deleted can be restored in the app; deleting an entire studio uses a permanent local deletion action. You should export work you want to keep before deletion. Local deletion does not establish removal from device backups or a third-party AI provider.

Exact retention periods and deletion procedures for provider requests, logs, support email, backups, and generated outputs need confirmation: [CONFIRM RETENTION SCHEDULE AND THIRD-PARTY DELETION PROCESS].

10 / ZERK

Your choices and privacy requests

You can choose whether to import media, use camera or microphone features, start cloud AI creation, share an export, or delete a local studio. You may write to us to request access, correction, deletion, withdrawal of consent where applicable, or information about handling of personal data. We may need to verify your identity and may respond as required by applicable law.

California residents may have rights under the CCPA/CPRA if Zerk’s operator is subject to that law. Individuals in Canada, Singapore, and Australia may have access, correction, complaint, or other rights under applicable privacy laws. The availability and scope of these rights depend on the law and the operator’s facts. [CONFIRM OPERATOR LEGAL STATUS, REQUEST METHODS, RESPONSE PROCESS AND APPLICABLE RIGHTS].

You may raise a concern with the relevant privacy regulator where local law allows. Contact us first if you would like us to investigate a concern.

11 / ZERK

Security and children

Zerk’s observed implementation uses local app storage, an iOS Keychain password verifier, and HTTPS for AI requests. No system can guarantee absolute security. The operator must verify its organizational safeguards and incident-response practices: [CONFIRM SECURITY CONTROLS AND BREACH PROCESS].

The permitted age and any treatment of children’s data are not established by the project: [CONFIRM AGE RULE, CHILDREN’S DATA PRACTICES AND PARENTAL REQUEST PROCESS].

12 / ZERK

Changes to this notice

We will update this notice when verified practices or legal obligations change. The date at the top identifies this draft. Before publication, confirm how material changes will be communicated: [CONFIRM CHANGE-NOTICE METHOD].

13 / ZERK

Contact and complaints

Send privacy questions and requests to the contact below. Include enough detail for us to understand your request, but do not send passwords, private images, or other sensitive data unless requested through a secure process. Ownership and monitoring of the supplied address should be confirmed before publication.

Official contact supplied for ZerkZerkten@163.com

You can also read the Terms of Use.