Reference

Open your privacy choices clearly

Before you open your account, this Privacy Policy explains how stkmtk handles account details, wallet records, device data, cookies and support messages.

India account dataCookie choicesUPI recordsPaytm contextPhonePe references
stkmtk Open your privacy choices clearly
REQUEST PATHS

Switch to privacy support channels

Your privacy request should reach the team that can verify the account and act on it without exposing more data than needed.

Privacy inbox Write to our privacy inbox from the email linked to your account. Include your username, the request type, and any payment reference you want us to check, so we can match it safely.
Signed-in chat After you sign in, use chat to ask where your privacy request stands. Our team may verify your account before discussing data, because chat must protect wallet records and login history.
Access recovery If you cannot access your account, send a privacy request from your registered email. We will ask for limited checks before changing contact data or sharing records, especially when payment activity is involved.
ACCOUNT CARE

Browse our account data controls

This policy area is handled by separating what we need for your account from what we need for security, payments, cookies and support.

Account details

We store the name, email, mobile number and sign-in data you provide so your account can be identified and protected. Changes to those details may require confirmation before our team applies them.

Payment references

UPI, Paytm and PhonePe activity may create reference IDs, timestamps and wallet status records. We use those records to match payments, answer your queries and resolve account-level disputes.

Cookie choices

Cookies help keep you signed in, remember basic preferences and detect unusual access patterns. You can change browser cookie settings, but some account and security functions may not work as expected.

Security checks

Device signals, IP address, session timing and failed login attempts help us detect account misuse. We use those signals for protection, fraud checks and support investigations linked to your account.

Retention rules

We keep records only for as long as they are needed for account operation, payment matching, dispute handling or legal duties. When retention is no longer required, records are deleted or anonymised.

Correction requests

You can ask us to correct inaccurate account details. For wallet-linked data, we may need to preserve transaction references while updating the profile fields that are wrong or out of date.

Open privacy questions before your account

These answers explain how this Privacy Policy works when you create an account, use payment methods, manage cookies or contact support. They are written for India account access and should be read with the rule that availability depends on local law. If your request needs account-specific action, contact us from your registered email.

It covers account details, sign-in records, device signals, cookie data, wallet references and support messages connected with your account. It also explains why we collect them and how you can request access or correction.

Payment methods can create reference numbers, timestamps and wallet status records. We use them to match your account activity, answer payment questions and keep records required for disputes or legal duties.

Yes, you can request a copy through the privacy contact path. We will verify your account first, then share data we can provide without exposing security methods or another person’s records.

You can ask us to update inaccurate account fields such as contact details. If a payment record is involved, we may keep the transaction reference while correcting the profile data that needs repair.

Cookies help with sign-in, language choices, session security and basic site measurement. You can manage them in your browser, though blocking certain cookies may affect account access and security checks.

Retention depends on why the record exists. Account, payment and support records may be kept for operation, dispute handling or legal duties, then deleted or anonymised when those reasons no longer apply.

Use the privacy inbox from your registered email, or ask signed-in chat to route your request. We may verify your identity before acting, especially when wallet records or access changes are involved.