PicElite Support and Privacy Request Guide
1. How PicElite can help
PicElite provides support paths for:
- account and sign-in problems;
- email verification;
- password recovery;
- profile correction;
- account deletion;
- privacy questions and requests;
- content safety reports;
- copyright or other rights concerns;
- advertising privacy questions;
- technical application problems.
Different requests may use different channels where that improves security or privacy.
2. Public support contact
Until separate operational inboxes are established, PicElite uses:
General Support: picelite.in@gmail.com
Privacy and Grievance: picelite.in@gmail.com
Copyright and Removal: picelite.in@gmail.com
Urgent Safety: picelite.in@gmail.com
Place of establishment: Thrissur, Kerala, India
The responsible proprietor/Grievance Officer name remains:
Fazil PJ
Using one inbox for multiple roles does not change the privacy or response requirements applicable to each request type.
3. Information you should never send to support
Do not send PicElite support:
- your password;
- one-time passwords or OTPs;
- authentication tokens;
- password-reset links;
- Google account credentials;
- private cryptographic keys;
- unnecessary identity documents;
- protected prompt text unless PicElite specifically provides a secure and necessary complaint path.
PicElite support should never ask you to send your password.
4. Sign-in and password problems
For email/password accounts, PicElite may provide Firebase Authentication password-reset email functionality.
Where available, use the in-app password recovery or password/security function instead of sending a password to support.
For Google sign-in issues, some problems may need to be resolved through your Google account or device configuration.
PicElite cannot see or recover your Google password.
5. Email verification
If PicElite requires email verification and you have not received the verification email:
- confirm that the account email is correct;
- check spam or filtered mail;
- use any available resend function;
- contact support if the issue continues.
Support may need enough information to identify the account but must not ask for your password.
6. Profile correction
Eligible registered consumers may use PicElite's Edit Profile feature for supported private profile fields.
The backend remains authoritative for age eligibility.
PicElite may reject a replacement date of birth that is invalid, impossible, in the future, or does not satisfy the registered-account age requirement.
For a correction that cannot be completed through the app, use the privacy request channel.
7. Privacy requests
Depending on applicable law, a person may be entitled to request applicable:
- access or information about processing;
- correction;
- completion;
- updating;
- deletion or erasure;
- withdrawal of consent where consent is the applicable basis;
- grievance handling;
- other rights provided by applicable law.
Submit privacy requests through:
Email: picelite.in@gmail.com
PicElite may need to verify that the requester is entitled to act for the account or personal data involved.
Verification should use the minimum information reasonably necessary.
8. Account deletion
Registered users may initiate account deletion through PicElite's in-app account settings.
PicElite must also provide an external web request path so a person can request account deletion without reinstalling the application.
Public account-deletion resource:
The separate Account Deletion Web Notice explains the intended process.
9. Content safety reports
Where you can access the affected model, use PicElite's in-app Report function for ordinary content safety concerns.
This allows the application to attach the correct model identifier without requiring you to send protected content to support.
For an urgent safety issue that cannot reasonably be reported in-app, use:
Email: picelite.in@gmail.com
Do not send passwords or unrelated sensitive information with a safety report.
10. Copyright and rights complaints
Copyright or other intellectual-property concerns should use PicElite's published Copyright and Removal process:
Copyright contact:
Email: picelite.in@gmail.com
General support should route rights complaints to the copyright process rather than attempting to resolve ownership informally.
11. Advertising privacy
PicElite is advertisement-supported and does not provide a general ads-off preference.
Where the advertising provider requires privacy choices, PicElite may expose a provider-backed privacy-options entry point.
Questions about provider-specific advertising choices may require reference to the applicable Google or platform privacy controls.
Acceptance of PicElite's Terms is not advertising consent.
12. Technical support
For technical problems, useful information may include:
- PicElite app version;
- device model;
- Android version;
- a brief description of what happened;
- approximate time of the problem;
- non-sensitive screenshots where appropriate.
Do not include:
- passwords;
- authentication tokens;
- protected prompt text;
- unnecessary DOB or sex information;
- precise location;
- unrelated personal data.
13. Request verification and fraud prevention
PicElite may verify a request before changing or disclosing account-related information.
Verification is intended to protect the account holder and may involve an existing authenticated session, verified account email, or another approved method.
PicElite must not require more personal information than reasonably necessary for the request.
Support staff must not bypass backend account authorization merely because a person claims ownership of an account.
14. Response and escalation
PicElite:
- records an actionable request through the approved channel;
- routes it to the appropriate support, privacy, copyright, safety, or account workflow;
- requests clarification only where necessary;
- avoids unnecessary personal-data collection;
- responds within periods required by applicable law;
- retains request records only for their applicable purpose and retention period.
Where Rule 3(2) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 applies to PicElite and the complaint, the current rule requires acknowledgement within 24 hours and ordinary resolution within 7 days.
Certain complaints covered by that rule require faster action, including specified removal complaints with a 36-hour period and specified complaints concerning intimate, nudity, sexual-act, or impersonation material with a 2-hour period.
Those shorter periods apply only where the relevant legal rule applies to the particular complaint.
15. Complaints and grievances
Privacy or service complaints may be submitted to:
Fazil PJ
Email: picelite.in@gmail.com
Place of establishment: Thrissur, Kerala, India
PicElite provides an internal grievance route through the contact above.
Where applicable law provides a regulator, appeal, Board, court, or other complaint route, use of PicElite's internal route does not remove any non-waivable right to use that route.
For privacy information and available rights, see the Privacy Policy.
16. Accessibility
Public support, privacy, copyright, and account-deletion information should be reasonably accessible without requiring a registered PicElite account unless authentication is necessary to perform a protected account action.
A person who has uninstalled PicElite must still be able to find and use the published external account-deletion request method.
17. Records and retention
PicElite may keep support records reasonably necessary to:
- resolve requests;
- prevent abuse;
- demonstrate completion;
- comply with legal obligations;
- protect rights and security.
PicElite retention schedule:
- ordinary closed technical/general support request: 12 months;
- formal privacy-rights or external account-deletion request: 3 years after closure;
- copyright/removal complaint: handled under the Copyright and Removal Policy, with a 3-year post-closure baseline;
- serious security/fraud case records may follow the separate approved security-case retention schedule.
After the applicable period, identifiable request content should be deleted unless a documented legal/security hold applies.
Support records must not become a storage location for passwords, protected prompts, authentication tokens, or unnecessary private-profile information.