Reference

Open your privacy choices with jackbit

jackbit keeps privacy choices close to your account flow: data for login, wallet records for UPI, Paytm, PhonePe and cookie settings are described before you share them.

UPI data scopePaytm privacy checksPhonePe record handlingCookie choices
Explore the lobby Read FAQ
jackbit Open your privacy choices with jackbit
CONTACT PATHS

Check privacy contact paths before sharing data

You can reach us about privacy before or after you open your account. Use the same contact details connected to your profile so we can match the request without exposing your data…

Privacy email Send privacy requests from the email address linked to your account. Include your mobile number only when needed, and avoid sending payment screenshots unless we ask for them to confirm a specific record.
Signed-in chat Use the chat bubble after login for cookie choices, data access questions or correction requests. We may move sensitive matters to email so your identity can be checked with less exposure.
Security contact If you suspect account access by another person, contact us quickly and ask for a privacy security check. We will look at login records, device changes and recent profile edits.
HANDLING CHECKS

Browse our privacy handling checks

Our privacy work is tied to the way your account, wallet and device session operate. We separate data used for login, payment processing, security checks and service messages, then limit access inside…

Data collection

We ask for details needed to create your account, confirm access and handle wallet activity. This can include name, mobile number, email, region, device data and verification records.

Payment records

When you use UPI, Paytm, PhonePe or Google Pay, we store transaction references, status updates and linked account identifiers. We do not ask you to share PINs, passwords or app login codes.

Cookie controls

Cookies help keep you signed in, remember privacy choices and detect unusual sessions. You can adjust browser settings, but some account checks may not work properly without required cookies.

Security checks

We monitor login attempts, device changes and account edits to reduce unauthorised access. If a risk appears, we may ask for extra confirmation before privacy-sensitive changes are processed.

Retention periods

We keep personal data only for account operation, dispute handling, security analysis or legal record duties. When a record is no longer needed, we remove it or separate it from your identity.

Change requests

You can ask us to correct details, provide a copy of personal data or delete eligible records. Some payment and security logs must remain for legal or dispute reasons.

Discover answers about your privacy rights

These privacy questions cover the account actions you are most likely to need: access to your data, correction of wrong details, cookie choices, payment records and contact steps. For any request, use your registered email or signed-in chat so we can confirm that the request really comes from you before we act.

We collect details needed to create and secure your account, such as name, email, mobile number, region, device data and login activity. If verification is required, we may ask for identity details connected to that check.

We use payment records to confirm transaction status, match wallet activity and handle disputes. Records can include reference IDs, timestamps, payment method labels and status messages, but not your app PIN or banking password.

Yes. Send the request from your registered email or signed-in chat. We may ask for identity confirmation before sharing a copy, so your data is not sent to another person.

Yes. Tell us which detail is wrong and provide the corrected value through a verified contact path. Some fields may need an extra check if they affect payments, security or identity records.

Cookies keep your session active, remember privacy choices, support security checks and help us understand basic site performance. You can manage browser settings, though required cookies may be needed for account access.

Access is limited to team roles that need the data for account service, security, payment checks or legal duties. We use internal access controls and logs to track handling of sensitive records.

Yes. Access and eligibility depend on local law and are available where local law permits. Some records may need to be kept for legal, security or dispute reasons even after a deletion request.

Related Pages

About Us jackbit Login Rocketon Book of Dead