Effective Date: August 11, 2026
Welcome to P to C - QuickShare.
This Privacy Policy explains how information, uploaded files, transfer metadata, technical data, and advertising-related data are handled when you use the P to C - QuickShare Android application, its associated file-transfer website, and its phone-to-phone file-transfer features, collectively referred to as the “Service.”
By accessing or using the Service, you acknowledge the practices described in this Privacy Policy.
The Service allows you to select one or more files from your Android device and upload them temporarily to our server so that they can be downloaded on another phone or computer using a temporary transfer code.
Depending on the files you select, uploaded content may contain personal, confidential, sensitive, copyrighted, or otherwise protected information.
We do not intentionally:
Inspect uploaded file contents for advertising purposes
Build advertising profiles from uploaded file contents
Sell uploaded files or their contents
Use uploaded files to train artificial intelligence systems
Make uploaded files publicly searchable
You are responsible for reviewing files before uploading them and ensuring that you have the legal right, authority, and permission to upload and share them.
To create, manage, secure, resume, complete, and deliver file transfers, we may temporarily process and store information such as:
File name
File size
File type or MIME type
Upload progress
Uploaded and downloaded byte counts
Temporary file identifiers
Temporary upload identifiers
Six-digit transfer codes
Hashed private sender session tokens
Hashed temporary computer authorization tokens
Hashed read-only mobile receiver tokens
Temporary authorization identifiers
Upload, completion, access, download, and expiration timestamps
Transfer and file status
Download or received status
Download count
Error and retry information
Private tokens are intended to be stored on the server in hashed form where supported by the Service’s current implementation.
When the App or website communicates with our server, certain technical information may be processed automatically, including:
IP address
Request date and time
Browser type
Device type
Operating-system information
Requested server endpoint
Request headers
Error and diagnostic information
Security and rate-limiting information
Information about unsuccessful transfer-code attempts
IP addresses or derived identifiers may be processed temporarily to:
Prevent transfer-code guessing
Detect excessive requests
Prevent abuse and unauthorized access
Investigate technical failures
Protect the Service and its users
Detect attacks or malicious activity
Our hosting or infrastructure provider may also maintain standard server, access, security, and diagnostic logs under its own policies and retention practices.
The Service does not currently require user account registration.
We do not directly ask for or require:
Your name
Email address
Phone number
Contact list
Precise GPS location
Account password
Payment information
Social-media account information
Government identification information
However, files you voluntarily select may themselves contain personal or sensitive information. You should review files carefully before uploading them.
The App uses third-party advertising and measurement technologies, including the Google Mobile Ads SDK and the Meta/Facebook SDK.
Depending on SDK configuration, device settings, user choices, available identifiers, and applicable law, these technologies may automatically collect, receive, or process information such as:
IP address
Android Advertising ID, where available
App Set ID or other device identifiers
App identifier and package information
App installation or activation events
App launches or sessions
Ad impressions and interactions
User interactions such as taps or video views
Device and operating-system information
App and SDK performance information
Diagnostic information
Event date and time
Advertising-attribution and campaign-measurement information
Approximate or general location inferred from an IP address
Information used for advertising, analytics, measurement, security, and fraud prevention
We do not intentionally send uploaded file contents, file names, transfer codes, private transfer tokens, or file-recipient information to Google or Meta for advertising or campaign-measurement purposes.
When the sender opens the App, the server generates:
A temporary six-digit transfer code visible in the App
A private session token used between the sender’s App and the server
The private sender session token is not intended to be disclosed to receiving devices.
The sender can select one or more files, and the App uploads the selected files temporarily to the server. Large files may be uploaded in multiple parts or chunks to support progress tracking, retrying, and resuming interrupted uploads.
Files may be transferred using the following methods.
The sender uploads files from the Android App.
The receiver opens the official P to C - QuickShare website on a computer or another browser-supported device and enters the sender’s active six-digit transfer code.
The website may then display the associated file list and allow available files to be downloaded.
A computer user may enter an active transfer code on the official website and receive a temporary, limited authorization token.
The computer can then upload files to the phone associated with that transfer session.
The Android App may periodically check the server for incoming files and allow the user to download them to the device.
The computer’s temporary authorization is separate from the Android App’s private session token.
A receiving user can open P to C - QuickShare on another Android device and enter the sender’s active six-digit transfer code.
After the code is verified, the server may issue the receiving App a temporary, read-only mobile receiver token.
The read-only mobile receiver token is designed to allow the receiving App to:
View files associated with the transfer
Download available files
Report that a file was received
The receiving App is not intentionally given the sender’s private session token and is not authorized to upload files on behalf of the sender through the read-only token.
A transfer code functions as a temporary access credential. It is not equivalent to an account password.
Anyone who obtains a correct and active transfer code may be able to request access to the associated transfer through the official website or another installation of the App.
You should:
Share transfer codes only with intended recipients
Avoid posting transfer codes publicly
Avoid sharing transfer codes in public groups or social-media posts
Confirm that the receiving person is trusted
We are not responsible for access caused by a user voluntarily sharing a transfer code with an unintended recipient.
Uploaded files are stored temporarily on our server to provide online transfer between devices.
Under the current configuration:
A transfer code and active sending session are normally valid for approximately 30 minutes
Successfully completed files may remain available for download for up to 24 hours
Temporary computer authorizations may expire earlier than the uploaded files
Temporary mobile receiver authorizations may expire earlier than the uploaded files
Downloading a file does not necessarily cause its immediate deletion
A file may remain available so that another authorized recipient can download it
Expired files and associated metadata may be removed through automatic cleanup processes
Automatic deletion may not occur at the exact second that the retention period ends. However, expired files are not intended to remain available through the Service.
Files and transfer information may be deleted earlier because of:
Storage limitations
Security concerns
Suspected abuse
Illegal or prohibited content
Technical failure
Server maintenance
Service changes
Administrative action
A valid deletion request
Retention periods may change in future versions. Information displayed in the current App or website may take priority where applicable.
We do not guarantee permanent storage, backup, restoration, or recovery of uploaded files.
The Service must not be used as a backup, permanent cloud-storage, or archival service. You should keep your own original copy of every important file.
The App, website, and server use HTTPS where configured to encrypt file data and technical information while they are transmitted over the internet.
Security measures used by the Service may include:
Random temporary transfer codes
Private sender session tokens
Temporary computer authorization tokens
Read-only mobile receiver tokens
Hashed token storage
Request validation
Authorization checks
Rate limiting
Chunk validation
File and identifier validation
Temporary storage
Automatic expiration
Restricted direct access to server storage folders
Download access controls
Security logging
For phone-to-phone transfers, a separate read-only receiver token is used so that the sender’s private App session token is not intentionally exposed to the receiving phone.
However, P to C - QuickShare is not represented as an end-to-end encrypted service.
Files must be received, stored, and processed temporarily by our server to provide the online file-transfer functionality.
No method of internet transmission, electronic processing, or storage is completely secure. We cannot guarantee absolute protection against:
Unauthorized access
Code sharing
Account or device compromise
Hosting-provider incidents
Network interception outside our control
Software vulnerabilities
Technical failure
Data corruption
Accidental loss
Malicious attacks
You should avoid uploading highly sensitive files unless you understand and accept the risks of temporary server-based transfer.
To support, promote, measure, and maintain the App, we use third-party advertising and measurement technologies, including Google AdMob and the Meta/Facebook SDK.
The App uses Google AdMob to display advertisements, including banner and interstitial advertisements.
Depending on the SDK version, device configuration, user settings, consent choices, advertising settings, enabled features, and applicable law, the Google Mobile Ads SDK may automatically collect, share, or process information such as:
IP address
User-resettable Android Advertising ID, where available
App Set ID or other device and account identifiers
App launches
Taps
Ad impressions
Ad interactions
Video views
Device and operating-system information
App and SDK performance information
Diagnostic information
Approximate or general location estimated from an IP address
Information used for advertising delivery
Information used for analytics and measurement
Information used for fraud prevention and security
Google states that data automatically collected by the Google Mobile Ads SDK is encrypted in transit. The specific information processed may depend on the SDK version, enabled advertising features, device configuration, user settings, consent choices, and the way the App uses the SDK.
Google processes information according to its own terms and Privacy Policy:
https://policies.google.com/privacy
The App uses the Meta/Facebook SDK to support app-install advertising, advertising attribution, campaign measurement, and App Events.
When automatic App Event logging is enabled, the Meta SDK may automatically log events such as app installation or activation and app launch or session events. Depending on SDK configuration, device settings, user choices, available identifiers, and applicable law, Meta may receive or process information such as:
App installation or activation events
App launches, sessions, and other automatically logged App Events
Android Advertising ID, where available
App identifier and package information
Device and operating-system information
IP address
Event date and time
Advertising-attribution and campaign-measurement information
App interactions and diagnostic information
Information used for analytics, measurement, security, and fraud prevention
The App does not use Facebook Login. We do not intentionally send users’ uploaded files, file contents, file names, transfer codes, private transfer tokens, or recipient details to Meta for advertising or campaign-measurement purposes.
Meta processes information according to its own terms, Business Tools terms, and Privacy Policy:
https://www.facebook.com/privacy/policy/
Where required, including for certain users in the European Economic Area, United Kingdom, or Switzerland, the App may display a consent message or privacy choices before requesting personalized advertisements or using advertising-related identifiers.
The App may use Google’s User Messaging Platform or another eligible consent-management solution to collect and manage applicable privacy choices.
Depending on the user’s choices, provider configuration, available identifiers, and applicable law, advertisements and measurement may be:
Personalized
Non-personalized
Limited
Restricted from using certain identifiers
Users may control or reset their Android Advertising ID through their device’s privacy settings. Where a privacy-options entry point is required and made available in the App, users may use it to review or change applicable advertising choices.
Google, Meta, and their advertising or measurement partners process information under their own privacy policies, terms, consent systems, and data-retention practices.
Depending on your Android version and the features being used, the App may use the following permissions or capabilities.
Internet and network access are used to:
Create transfer sessions
Generate transfer codes
Authorize receiving devices
Upload files
Download files
Check file availability
Check upload and download status
Retry interrupted transfers
Detect whether an internet connection is available
Communicate with the server
Display advertisements
Request advertising consent information
Send applicable App Events and advertising-attribution information to Meta
The App uses Android’s system file picker to let you select specific files.
The App does not require unrestricted access to every file on your device for its normal sending functionality.
The App receives access to files that you deliberately select through the Android system file picker, subject to Android’s storage and permission systems.
Android’s Storage Access Framework allows users to choose specific documents and files through a system-controlled picker.
When receiving files, the App may write downloaded files to the device’s shared Downloads area.
Downloaded files may normally be stored in a folder such as:
Downloads/P to C QuickShare
The exact location may depend on:
Android version
Device manufacturer
Storage configuration
File type
System storage framework
Files saved to shared storage may remain on the device after the App is removed unless the user deletes them separately.
On older Android versions, storage permission may be requested when required to save received files.
The App should request only the storage access needed for its user-facing file-transfer functionality.
Notification permission may be used to display:
Ongoing upload progress
Ongoing download progress
Upload status
Download status
Completion notifications
Transfer failures
Retry information
Other transfer-related messages
Foreground-service and data-sync capabilities may be used to continue large or long-running uploads and downloads.
While a transfer is active, Android may display an ongoing system notification showing transfer progress or status.
The App declares access to the Android Advertising ID for advertising, app-install attribution, campaign measurement, analytics, security, and fraud-prevention purposes where that identifier is available and its use is permitted.
The Google Mobile Ads SDK and Meta/Facebook SDK may access or process the Advertising ID and applicable App Events as described in Section 5.
Users may reset or delete the Advertising ID through Android privacy settings. Device settings, user choices, provider configuration, limited-ad modes, and applicable law may restrict or prevent use of the Advertising ID.
We do not sell uploaded files or their contents.
Information may be processed, disclosed, or shared only in limited circumstances, including:
Files and related metadata may be made available to a recipient who enters the correct and active transfer code through:
The official website
Another installation of P to C - QuickShare
An authorized computer-to-phone transfer session
A receiving device may receive:
File names
File sizes
File types
File status
Expiration information
File contents selected by the sender
An unintended person who obtains a valid transfer code may also be able to request access. Users are responsible for protecting their transfer codes.
Our hosting, server, network, storage, security, or infrastructure providers may process files and technical data as necessary to:
Store files temporarily
Deliver files
Process requests
Maintain servers
Detect abuse
Investigate errors
Protect the Service
Google AdMob, Meta, and their advertising or measurement partners may collect, receive, or process advertising-related and technical information for:
Advertising delivery
App-install attribution
Campaign measurement
App Events
Ad personalization, where permitted
Non-personalized advertising
Analytics
Measurement
Consent management
Frequency control
Security
Fraud prevention
We do not intentionally share uploaded file contents, file names, transfer codes, private transfer tokens, or recipient details with these providers for advertising or campaign-measurement purposes.
Information may be disclosed where reasonably necessary to:
Comply with applicable law
Respond to a valid legal process
Respond to a court order
Respond to a lawful government request
Investigate fraud
Investigate abuse
Address security threats
Protect users
Protect our legal rights
Prevent harm
Enforce applicable terms or policies
Information may be transferred in connection with:
A merger
Acquisition
Business sale
Restructuring
Financing
Change of ownership
Transfer of Service assets
Where appropriate, reasonable safeguards should apply to such a transfer.
Third-party providers process information under their own terms and privacy policies.
You must not use the Service to upload, transfer, receive, or distribute:
Files you do not have permission to share
Illegal or prohibited content
Malware
Viruses
Ransomware
Spyware
Harmful software
Files intended to damage a device or network
Content that violates another person’s privacy
Copyright-infringing content
Content that violates intellectual-property rights
Stolen data
Fraudulent material
Content that violates applicable law
Content that could cause harm to another person
You are responsible for:
Selecting the correct files
Protecting your transfer code
Sharing the code only with intended recipients
Confirming that received files are safe before opening them
Keeping backup copies of important files
Ensuring that your use complies with applicable law
We may restrict, delete, or block transfers where we reasonably believe the Service is being abused.
The Service does not currently require user accounts. Therefore, there is no account profile available for deletion.
Uploaded files and transfer metadata are normally deleted automatically after the applicable expiration period or through server cleanup processes.
Downloading or marking a file as received may not immediately delete the server copy. The file may remain available until:
Its normal expiration
Earlier administrative deletion
A security-related deletion
A successful deletion request
Automated cleanup
To request earlier deletion, contact us and provide, where available:
The six-digit transfer code
The approximate upload date
The approximate upload time
The file name
A brief explanation of the request
Do not send your private sender session token, computer authorization token, or mobile receiver token by email.
Providing the requested details does not guarantee that we can identify or delete a transfer.
We may be unable to locate a transfer where:
The transfer code has expired
The session record has already been deleted
The file has already been automatically removed
The information provided is incomplete
Multiple transfers used similar file names
Files already downloaded to another user’s phone or computer cannot be remotely deleted by us from that recipient’s device.
Advertising and measurement information processed by Google or Meta is subject to those providers’ own privacy controls, retention practices, and request procedures. Users may also:
Reset or delete the Android Advertising ID through device privacy settings
Review applicable advertising choices presented by the App
Manage Google advertising settings where available
Manage Meta advertising preferences where available
Deleting an expired transfer from our server does not automatically delete information independently processed by Google, Meta, a hosting provider, or a recipient under that party’s own policies.
The Service is intended for a general audience and is not designed or marketed specifically to children under the age of 13.
We do not knowingly require children to provide:
Names
Email addresses
Phone numbers
Contact lists
Account-registration information
However:
Files selected by users may contain personal information
Technical information may be processed by the server
Google AdMob may process technical and advertising-related information as described in this Privacy Policy
The Meta/Facebook SDK may process App Events, device information, and advertising-attribution information as described in this Privacy Policy
Users below the minimum age required by applicable law should use the Service only with the involvement and supervision of a parent or legal guardian.
Parents or legal guardians who believe a child has provided personal information through the Service may contact us to request review or deletion.
Where an app targets children or includes children in its declared audience, additional Google Play Families and advertising requirements may apply. Google Play also places restrictions on SDK use in child-directed services.
Our hosting provider, Google, Meta, advertising or measurement partners, and other service providers may process information in countries different from the country where the user is located.
Privacy, data-protection, government-access, and retention laws may differ between jurisdictions.
Where required, providers may use contractual, organizational, legal, or technical safeguards for international processing.
By using the Service, you understand that information may be processed in countries outside your own, subject to applicable law.
The App or website may contain links to third-party services, including:
Google Play
Google privacy information
Meta privacy information
Advertising content
External websites
We do not control the privacy, security, content, or availability of third-party websites or services.
Visiting or interacting with a third-party service is subject to that provider’s own:
Privacy policy
Terms
Security practices
Data-retention practices
The Service is provided as a temporary file-transfer tool.
We do not guarantee:
Continuous availability
Error-free operation
Permanent storage
Successful delivery
Successful upload
Successful download
Recovery of deleted files
Recovery of expired files
Compatibility with every file type
Compatibility with every device
Protection against every security risk
Transfers may fail because of:
Internet interruption
Server failure
Device shutdown
Storage limitations
Permission denial
File corruption
Hosting limitations
Software errors
Maintenance
Security restrictions
Always keep the original copy of important files.
The information in this Privacy Policy is intended to describe the App’s actual data practices.
Google Play requires developers to complete and maintain a Data safety declaration that covers data handled by both the App and integrated third-party SDKs, including the Google Mobile Ads SDK and Meta/Facebook SDK. The developer is responsible for keeping those declarations complete, accurate, and consistent with the App’s actual data practices and this Privacy Policy.
The App’s Google Play Data safety information may be updated when:
App functionality changes
Server practices change
Permissions change
Advertising SDKs change
App Events or advertising-attribution practices change
Data collection changes
Data-sharing practices change
We may update this Privacy Policy when:
App features change
Phone-to-phone functionality changes
Server practices change
Storage or retention periods change
Security practices change
Advertising services change
App Events or campaign-measurement practices change
Permissions change
Third-party SDKs change
Legal requirements change
Google Play requirements change
The updated Privacy Policy will be published with a revised effective date.
Continued use of the Service after an update means that the revised Privacy Policy applies to your subsequent use of the Service, subject to applicable law.
You should review this page periodically.
For privacy questions, file-deletion requests, security concerns, or questions about this Privacy Policy, contact:
Email: sajibrasma@gmail.com