Privacy
Pokazhu is developed by Mikhail Kislyakov. Questions about data processing: hrkislyakov@gmail.com.
What data the app needs
- Members sign in with Sign in with Apple or verified email and password and use one profile: the same person can create and read guides. For Apple sign-in, the server stores the Apple user identifier, sign-in service data and a protected token for revoking authorization. The app's account database does not store the name or email provided by Apple. An address that the user explicitly enters for email registration or linking is stored separately as a verified sign-in method.
- A person can belong to one active group. The server stores membership, invitations, guide creation rights and selected recipients. The group owner controls membership and permission to create new guides; this does not give the owner access to another person's private materials. The app does not request access to the phone's address book.
- First-time setup requires a saved name; a profile photo is optional. The name and photo are stored on the server and shown to group members. You can save a personal label for another member: only you see the label you set. Profile data is cleared when the account is deleted. Choosing a photo does not grant access to your entire photo library; profile photos are not sent for AI processing. The interface language is saved on the device.
- When a guide is opened online, the app sends the guide, published revision and viewing session identifiers. Retrying the same event does not increase its count. Authors see opening counts for their own guides without a list of readers; advertising identifiers are not used. Statistics start when this feature is enabled, do not reconstruct earlier or undelivered offline views, and do not represent unique people.
- The author chooses the text, photos, videos and audio within videos to send. The server processes source materials, extracted frames, transcripts when audio processing is available, clarifications and corrections; it stores drafts, completed steps and published versions.
- A help request to an author contains a reference to the guide and step, along with the message supplied by the user. It is available to that author. A separate conversation with the Poki AI helper, when enabled, stores messages, selected answers, the followed path and personal guide changes for the current reader; it is not sent to the author as a help request.
- If notifications are permitted, a push token and technical device data are sent. Purchases involve processing Apple transaction identifiers and details, and the available allowance. Apple does not provide card numbers or payment details to the app.
- Technical request, job and error identifiers are used to operate the service and investigate errors. During a network connection, the server receives the IP address and technical request parameters. Passwords, access tokens and the content of materials should not be sent to support or included in diagnostics.
Email, passwords and service messages
For email registration, the server stores the entered address, its verification status and a password hash with an individual salt, calculated using scrypt. The password is not stored as plaintext or sent by email. Email can be added to an existing Apple profile from that profile after reauthentication and verification of the code in the message. Both methods open the same profile, group and guides. Email and password belong to the service account rather than a particular platform: signing in on another supported device opens the same profile. Matching addresses alone do not merge accounts; other group members do not see the email address.
After a registration, email-linking or password-reset request, a service message is delivered through Resend. It receives the recipient address, message text containing a one-time code and technical delivery information. Messages are sent from the auth.kislyakov.tech domain; the selected sending region is Virginia, United States. Data may be processed and stored outside the user's country, including in the United States. The provider's retention and processing rules are governed by its privacy policy, terms and data processing addendum; zero retention is not promised. Sign-in messages do not contain guide materials or the account password.
A code is valid for 15 minutes from the request. Temporary verification and delivery data are kept in a protected server record; the address, code to be sent and operation data are held in an encrypted queue. Delivery may be retried after a temporary failure only until the code expires or is used. After use or expiry, housekeeping clears the content; a delivered message may remain in the user's mailbox and with mail providers under their rules. A successful password reset revokes previous app sessions, so the user must sign in again.
External AI processing and consent
To prepare a guide, selected materials or frames, text and, if the corresponding route is enabled, audio extracted from them are sent from the server through OpenRouter to an external AI provider. The main configured provider is DeepInfra. Below the create button, the app explains this transfer and links to the terms and this policy. Tapping the button records consent before materials are transferred; new AI processing does not start without consent. Selecting attachments or saving from the Share menu keeps them on the device until you tap the create button. On-device text-to-speech on iPhone does not require sending the text to OpenRouter.
In settings, open “Privacy” → “Withdraw consent”. Withdrawal stops new transfers for AI processing, but does not undo completed requests or recall data already sent to the provider. Use account deletion to delete app data.
The connection to OpenRouter passes through a server in Germany in encrypted form; the transport proxy does not decrypt the content of requests.
Routing prohibits data collection by the provider (data_collection: deny). This setting is not a promise of zero retention by everyone involved in the transfer. External services' rules and technical retention are governed by their terms: OpenRouter and DeepInfra. External services may process data outside your country. Do not send materials for which this transfer is not permitted.
Step illustrations
With active Pro and no author-provided photos or video, the app may find or draw useful step illustrations. Separate “Step illustrations” consent is required before the first request. This processing is optional: a guide can be created with text alone. Installing from TestFlight does not itself grant Pro.
The main OpenRouter and DeepInfra route analyzes the text steps. A separate OpenRouter image route sends Krea a short description of the necessary objects and action. Wikimedia Commons receives a short image search phrase. These two routes do not receive source files, profile photos or conversation history. Descriptions are checked for obvious personal details, but complete anonymity of arbitrary text cannot be guaranteed. Avoid including unnecessary personal information in materials.
The main text route’s data_collection: deny setting does not automatically cover the image API or Commons. Zero retention and no training are not promised for these separate routes; OpenRouter, Krea and Wikimedia rules apply. Connections pass through the server in Germany; external services may process data in other countries.
Drawn images are labelled “AI illustration” and may be conceptual diagrams rather than exact app screens. Search accepts only images with a verified CC0 or Public domain designation; the source and licence are retained with the guide. Images undergo an automatic step relevance check and normal author review before publication. AI can make mistakes. You can withdraw the separate consent in privacy settings to stop new requests; this cannot recall data already sent. Finished images are retained and deleted with their guide; Pro expiry alone does not remove them.
Poki: conversation and automatic search
Poki is an AI helper whose availability depends on group access and service configuration. Before first use, the recipient personally accepts separate current consent for conversation processing. The published guide text, applied personal version, selected answers, followed steps and a bounded message history are sent through OpenRouter to the configured provider, DeepInfra. This text-only version does not send the source recording, private author drafts, other readers' conversations or images. Poki does not observe the screen or control other apps.
If search is enabled, before its first use the recipient separately accepts disclosure of transfer to the Parallel search service through OpenRouter. The AI then decides automatically when current public information is needed, without confirmation of each query. The server checks a separate short query; only that query, with generic search instructions, is sent for search, without conversation history, the complete guide, images or access credentials. The short query and sources appear in the conversation. Checks reject detectable personal details and copied conversation, but cannot guarantee that every query is fully anonymous.
Search is separate processing: DeepInfra retention and training controls do not cover it. The search service may retain queries and use data for improvement and training; zero retention and no training are not promised for search. See Parallel customer terms and Parallel privacy policy. A separate agreement or selected European search mode for this integration has not been confirmed here. Withdrawal of the relevant consent stops new transfers and delivery or application of results that require it; it cannot recall a query already sent.
Changes affect only the current reader's personal version after an explicit “Apply to my guide” action; the last applied version can be undone. The published original and other readers' versions remain unchanged. AI help availability depends on group access and service settings; personal consent is required regardless of access. A public share link alone does not grant group AI features.
Pro purchases are unavailable in the first public release, and upcoming features are marked “Soon”. Existing gift access is stored separately from Apple purchases. Access is based on current server entitlements and verified StoreKit purchases; installing from TestFlight alone does not grant Pro. For service checks of Apple-signed proofs, the server may retain a protected identifier hash tied to the profile and its expiry, rather than the signed document itself. This record prevents another profile from reusing the proof and is not itself a permanent gift.
Who can access guides
Source materials and drafts are available to their author. When publishing, the author chooses the whole group or specific members. A targeted guide is visible to its author and selected recipients; other members, including the group owner, do not automatically receive access. A whole-group guide is available to group members. An excluded member loses access to others' guides and group AI but retains a read-only archive of their own guides; materials they already published remain available to the previous recipients. Revoking permission to create new guides does not by itself prevent editing the author's existing guides while they remain in the same group and the relevant allowances are available.
If public publishing is available to the author and they create a link or code, anyone possessing it can open the corresponding reviewed version in the app. This does not expose source materials or other guides. Previously issued links remain valid until the author revokes them; restricting new Pro features does not by itself revoke a link. The author can revoke access; a copy already downloaded to another device cannot reliably be recalled while that device is offline.
Optional Pro interest statistics
Only after a separate “Allow” choice, the app stores Pro impressions, description views, taps on locked features and “I want Pro” on our server. Declining does not restrict app functionality. You can change your choice in Settings → Privacy.
To count distinct users, events are linked to the technical account ID and the exact consent record. We store an event ID, server receipt time, event type, placement and feature from a fixed list, app version and build, interface language, actual access cohort (free, gift or subscription), and verified Apple receipt environment or an “unverified” label. This data is linked to your account; it is not anonymous. The signed receipt is checked only to classify the environment and is not stored in the statistics; this check never grants Pro.
Events do not include names, email addresses, group or guide IDs, text, photos, video, audio, IP addresses, advertising identifiers or installation identifiers. There are no external analytics SDKs or advertising tracking. The developer's closed report shows aggregate counts only. Users who decline are absent from the statistics; test and gifted access are separated from the main funnel.
Events are kept for up to 90 days. Turning statistics off stops collection and deletes the account's stored events from our server; deleting the account also removes them. The choice record is retained so it can be respected on later sign-ins. “I want Pro” only records interest: it does not start a subscription, charge money or subscribe you to messages.
Retention and deletion
Poki conversation text, search queries, sources and unapplied proposals expire after 30 days without session activity and are cleared by housekeeping; expired content is not delivered as a current conversation. Applied personal steps may remain while the original guide remains accessible. Deleting the conversation clears it and personal changes; original access revocation or source/profile deletion closes or clears the corresponding personal state. Technical cost and completed-operation records are retained separately from conversation text.
Source materials have a retention period of 30 days after processing is completed. Derived materials and guides are stored until deleted. Service records of consent, access, purchases and deletion are used to operate the service and verify the corresponding operations.
Any member can request deletion in the app: “Settings” → “Delete account”, reauthenticating with Apple or the current password, if configured. After accepting the request, the server revokes access, clears the email address, password hash and associated temporary codes, and queues the remaining data cleanup. Completion requires a confirmed protected deletion record in a separate log. If Apple is linked to the profile, its authorization must also be revoked, even when deletion was confirmed with a password. Leaving or being removed from a group differs from deleting an account: the archive of your own guides remains after removal, but not after account deletion.
In the current deployment, the deletion log is stored on the same server, separately from the main database; external backup is not enabled. If a required service is temporarily unavailable, the request remains pending: revoked access does not mean the files have already been physically deleted. You can contact support about the request's status, quoting its technical reference number.
Downloaded guides are stored on the device for offline viewing. Access changes take effect after contacting the server; immediate deletion on a completely disconnected device is not possible. Deleting an account does not cancel an Apple subscription — subscriptions are managed separately in Apple settings.
Keeping materials safe and user choices
The service uses one main server. External backups have been postponed: recovery of all materials is not guaranteed if the server is lost. Keep your own copies of important source recordings.
The camera and microphone are used with system permission. For imports, the user selects a specific file. Notifications are optional for viewing guides and connecting. The app has no advertising tracking. These pages do not use cookies, external fonts or analytics scripts.
Contacting support
If you contact us by email, the sender's address and the contents of the message are used to reply; correspondence is processed by Gmail. Do not attach personal recordings or secrets unnecessarily. For a data deletion or correction request, include the technical request reference number if you have one; your account password or one-time verification code is not needed.
If the data processed or AI providers change, this page and the information in the app must be updated. A significant change to AI processing requires up-to-date consent.