Privacy at Dyk

Operator and contact

Dyk is operated by Peter Mamrukov in Israel. For privacy, access, correction or deletion requests, contact peter.mamrukov@gmail.com.

Information we process

• Account: depending on sign-in, a provider identifier, name, email, Telegram ID, username or profile label. Dyk has no account password.
• Family: membership and roles, task-recipient names, parent/child role, language, reminder settings and prompts.
• WhatsApp: connection/chat identifiers, names, state and timestamps. For imported chats the core database can store message text or captions, sender name or identifier, message ID, source and time. The core importer does not save media file contents, although WhatsApp connection infrastructure processes data needed for the linked device.
• Derived/service data: tasks, summaries, actions, dates, reasoning, translations, source excerpts, Dyk-assistant messages, task actions, notification preferences and delivery status.
• Security: hashed session/invitation tokens, authentication challenges, rate limits, errors and timestamps. Some UI preferences stay in browser local storage.

Private family or school chats can contain health, religious, financial or other sensitive details. If such details appear in an imported message, they can be processed with that message.

Google and Yandex

When enabled, Google sign-in requests basic OpenID profile and email information. Yandex sign-in requests basic account information and email. Dyk uses them to authenticate, create or explicitly link a Dyk account and show an account label. They are not used for advertising, and accounts are not merged merely because profile details look similar.

Purposes and AI

We process data for authentication, family access, WhatsApp connection, importing chosen conversations, tasks, summaries, translations, source evidence, requested notifications, abuse prevention, diagnostics and service operation.

For task extraction, summaries or translation, Dyk can send message text and relevant context - such as sender/chat names, recipient names/profiles and existing tasks - to the AI service configured by the operator. Dyk is not a zero-knowledge service. AI can be wrong, so verify important dates, payments, permissions and urgent changes in the original message.

Sharing

Data is shared only as needed to operate Dyk, including hosting/database and WhatsApp connection infrastructure, the configured AI service, your chosen sign-in provider, Telegram when enabled and an email provider when email features are enabled. We do not sell personal data or use private WhatsApp content for advertising.

Family access

Family owners/admins can manage sources and may see the connected chat list and open chats available to that family. Ordinary membership does not by itself expose another member's private Dyk-assistant conversation.

Retention and deletion

Dyk does not yet have one automatic retention period for all imported and derived data. Turning off a group, leaving a family or unlinking a sign-in method does not itself delete all prior data. A complete self-service account deletion flow is not yet available. Until it is, request access, correction or deletion at peter.mamrukov@gmail.com. Identity verification may be required, and deletion can require handling active systems and applicable backups.

Security

Dyk uses HTTPS, secure HTTP-only production cookies, CSRF/same-origin checks, hashed session and invitation tokens, rate limits, parameterized database queries and family/user authorization boundaries. Private pages are no-store/noindex.

Security work is ongoing. After WhatsApp messages enter Dyk, the system must not be described as end-to-end encrypted or zero-knowledge. Encryption at rest, backup protection, least-privilege database access, secret protection, retention and complete deletion are tracked security work and require verification before stronger claims are made.

International processing and children

Dyk is operated from Israel. Providers may process data in other countries depending on the production configuration. Tasks can concern children without a child account, and chats can contain information about people who never created a Dyk account. The person connecting a source is responsible for using Dyk only where entitled and limiting access to trusted people.

Your choices

You choose the available sign-in method, chats followed for tasks, invited family members and optional notification channels. For privacy requests contact peter.mamrukov@gmail.com. We may update this policy when data flows, providers or controls change.

Short explanation of chats and family access

Choose an available sign-in method. No Dyk password to remember.