PhrendlyCamWhat We Collect
A category-by-category guide
What PhrendlyCam collects
Different parts of PhrendlyCam need different information. Browsing publicly available pages is not the same as creating an account, starting a call or buying coins. This guide separates those activities so you can understand what may be handled and why.
Open in browser · Guest matching · Trial access included
The main categories at a glance
The table summarizes common categories rather than claiming that every visitor generates every record. Actual information depends on which features you use, your browser choices and whether you create an account or make a purchase.
Some information comes directly from you, some is generated by your device or session and some comes from providers involved in sign-in, hosting, analytics or payments. The privacy policy explains broader use, sharing and retention.
| Activity | Possible information | Main purpose |
|---|---|---|
| Browse or open the site | IP address, device, browser, logs, cookies | Delivery, security and reliability |
| Create or use an account | Email, display name, profile choices, sign-in records | Authentication and account operation |
| Match or communicate | Messages, matches, follows and timestamps | Provide and remember interactions |
| Block or report | The relevant account, event and report details | Safety, review and abuse prevention |
| Receive rewards or buy coins | Eligibility, package, amount and provider reference | Rewards, payment and transaction support |
Information you choose to provide
Account and profile information may include your email, display name, preferences and the content you choose to present. Messages and reports include what you write or submit. You control what personal details to put into a conversation, but other members may receive what you choose to send them.
Do not provide passwords, verification codes or complete payment-card details in a message or support request. A support request normally needs the account reference, the problem and relevant timing—not your credentials.
Device, browser and permission choices
Technical records can include IP address, approximate region, operating system, browser version, language, referring page and error or event logs. Cookies or local storage may keep a session, remember preferences or support security and analytics.
Camera and microphone permissions are controlled by your browser. Choosing text avoids the need for camera or microphone input; choosing voice or video requires the corresponding permission. You can change those permissions in browser settings. Technical access is not a reason to record or publish another person’s conversation.
Purchases, retention and your requests
A coin or package transaction may involve the selected item, amount, currency, time, status and a payment-provider reference. Payment providers handle their own card or account information under their policies. Transaction records may be needed for support, fraud prevention, accounting or legal obligations.
Retention varies by category and purpose. Account closure does not necessarily erase every safety, transaction or backup record immediately. You can request access, correction or deletion through the Contact page, subject to verification and applicable exceptions. Review the service terms for the related account and coin rules.
Keep the thought going
Read the next useful note
Before you press send
A few honest answers
Does every visitor create an account record?
No. Public browsing and account use involve different information. Account records depend on whether and how you sign up or sign in.
Does PhrendlyCam receive my full card number?
Payment-card details are handled by the relevant payment provider. Do not send a complete card number through chat or a support request.
Can I use the site without camera access?
Yes. Choose text or voice when you do not want video. Your browser controls camera and microphone permissions.
How do I ask what information is connected to my account?
Use the current Contact route and identify the account and request. Ownership may need verification, but you should never submit a password or verification code.
Say it to a real person
Understand the category before you share the detail.
Use browser permissions and account controls, and make a specific request when you need information about your own records.