666p1 Privacy Policy: How We Handle Your Information
At 666p1, the way we collect, store and use your personal information is governed by this Privacy Policy. Every account action you take — from verifying your identity to completing a Raast or Bank Transfer transaction — is covered here. Read through to understand what data we hold, why we hold it, and how you can manage it.
Account data protected
Raast & Bank Transfer privacy covered
Your rights clearly stated
Contact route available
POLICY POSTURE
What This Policy Covers and How It Works
This Privacy Policy applies to all personal data we receive when you create an account on 666p1, log in, submit a support request, or carry out a transaction using Raast, Bank Transfer or Debit Card. We collect only the information that is necessary to run your account and process your requests — nothing beyond what your account flow requires. When you register, we collect identification details, contact information and payment method references. When you make a deposit or withdrawal via Bank Transfer or Raast, we retain a record of that transaction in your account wallet history. These records are used to verify your identity, resolve account queries and comply with obligations that apply where local law permits. We do not sell your personal data to third parties for marketing purposes. Where we share data with service providers — such as payment processors handling your Debit Card or Raast payment — those processors operate under data-handling agreements and may not use your information for any purpose outside the service they perform for us. You can review the data we hold on your account at any time through your account dashboard after login. If you find an error, you can raise a correction request via our support channel. This policy is subject to the laws of the jurisdiction where access is permitted, and availability depends on local law and eligible regions.
Raast
Raast payment references are stored as part of your transaction record and used solely for account verification and dispute resolution.
Bank Transfer
Bank Transfer details you submit are retained in your wallet history and are not shared outside the scope of processing your transaction.
Debit Card
Debit Card data is handled through our payment processor under a data-handling agreement; we do not store full card numbers on our own servers.
POLICY BOUNDARIES
Where This Policy Applies and What It Does Not Cover
This policy draws a clear line between what we govern and what falls outside our control. Understanding the scope helps you know exactly where to direct a data question — to us, or to the relevant third-party service.
Account Access
Any personal data you submit during account creation, login or identity verification on 666p1 falls fully within this policy. This includes your name, contact details and any documents you upload for account purposes.
Transactions
Payment records for Raast, Bank Transfer and Debit Card deposits or withdrawals processed through our platform are covered. We retain these records in your account wallet and use them only for account management and verification.
Site Content
Data generated by your browsing behaviour on 666p1 — pages visited, session duration, device type — is collected through cookies and analytics tools. This data is used to improve site performance and is governed by this policy.
Third-Party Services
Links or integrations that take you away from 666p1 — including external payment gateways or third-party authentication services — are governed by those third parties' own privacy policies. We are not responsible for data practices outside our platform.
YOUR CHOICES
Practical Steps You Can Take Under This Policy
You hold meaningful rights over the personal data we store. The most direct way to act on them is through your account dashboard, which you can access after login. Inside the dashboard, your transaction history — including records for Raast and Bank Transfer — is visible at any time. If any detail looks wrong, the correction process starts there: locate the relevant record, then raise a support ticket referencing the specific entry. For data held outside the dashboard — such as identity documents submitted during verification — you can request a summary through our support channel. We aim to respond to data enquiries within the timeframe required by applicable law, which varies depending on the region and local regulations in effect where your account was opened. Where local law permits account deletion, you can submit that request through the same support route. We will confirm receipt and outline the steps involved before any action is taken on your account.
Review Your Records
Log in and open your account dashboard to see the full transaction history, including all Raast, Bank Transfer and Debit Card entries. No separate request is needed to view these.
Correct Account Details
If your name, contact number or payment reference is recorded incorrectly, raise a support ticket. Quote the specific field and the correct value so our team can action the change without delay.
Ask a Data Question
For any question about what data we hold, why we hold it or how long we retain it, contact us through the support channel shown on your account page. Queries are handled in line with applicable local law.
Request Account Changes
Where local law and our terms permit, you may request modification or removal of certain data. Submit the request via support; we will confirm next steps and the applicable process before anything is changed.
REACH OUR TEAM
How to Contact Us About This Policy
If this Privacy Policy raises a question you cannot answer through your account dashboard, our support team is the right place to send it. Use the channel that works for you — live chat inside your account, or the email route shown on the contact page. For payment-related privacy queries involving Raast or Bank Transfer records, have your transaction reference ready so we can locate the correct entry quickly.
Live Chat
Open your account and use the live chat option to reach support directly. For privacy questions, describe the specific data concern and include any relevant account reference.
Email Support
Send your data query to the support email address listed on the contact page of 666p1. Include your registered contact detail and a clear description of the request.
Account Dashboard
Many data and privacy actions — viewing records, checking transaction history for Raast, Bank Transfer or Debit Card — can be handled directly inside your account without contacting support.
DATA HANDLING PRACTICE
How 666p1 Manages Data, Cookies and Retention
We apply a consistent set of data practices across account registration, payment processing and site usage. Cookies on 666p1 are used for session management and site performance analysis; you can adjust cookie preferences through your browser settings at any time. Account data is retained for as long as your account remains active and for a further period required by the applicable rules in the region where access is permitted. Payment records — including those linked to Raast, Bank Transfer and Debit Card — follow the retention period set by relevant financial regulations, which varies by jurisdiction. When data is no longer required, it is deleted or anonymised in line with those obligations.
Cookie Management
Cookies on 666p1 handle session state and usage analytics. You control cookie settings through your browser. Disabling certain cookies may affect how some account features behave during your session.
Account Security
Access to your personal data is restricted to account-level authentication. If you suspect unauthorised access, change your credentials immediately and notify support through the live chat or email route.
Data Retention
We keep your data for the period required by applicable local law and our operational need. Once that period ends, data is either deleted or anonymised. The current retention state is shown in your account dashboard after login.
Policy Updates
When this Privacy Policy changes, the updated version is published at 666p1/privacy-policy/ with a revised effective date. Continued use of the account after a policy update indicates acceptance of the revised terms.
COMMON POLICY QUESTIONS
Privacy Policy Questions We Hear Most
Below are the questions we receive most often about how 666p1 handles personal data. If your question is not answered here, use the support channel to send it directly.
What personal data does 666p1 collect when I open an account?
We collect the information you submit during registration — name, contact details and any identity documents required for verification. When you make a deposit or withdrawal via Raast, Bank Transfer or Debit Card, a record of that transaction is added to your account wallet history.
Does 666p1 share my data with third parties?
We share data only with service providers directly involved in running your account — for example, payment processors handling your Raast or Debit Card transaction. These providers operate under data-handling agreements and cannot use your data for any other purpose.
How can I see what data 666p1 holds on me?
Log in and open your account dashboard. Your transaction history and registered account details are visible there. For data held outside the dashboard, such as submitted identity documents, raise a request through the support channel and we will provide a summary.
How do I correct an error in my account data?
Open a support ticket and quote the specific field that is incorrect along with the correct value. Our team will review and apply the correction. For payment-related records linked to Bank Transfer or Raast, include the transaction reference to speed up the process.
How long does 666p1 keep my personal data?
Retention periods depend on the applicable local law in the region where your account is active. Account data is kept while your account is open and for a further period required by regulation. Payment records follow the financial retention rules in the relevant jurisdiction.
What happens to my data if I close my account?
Where local law permits account closure, we retain your data for the minimum period required by applicable regulation after the account is closed. Once that obligation ends, the data is deleted or anonymised. Submit a closure request through the support channel to start the process.