Privacy Policy

Request Didloo account deletion

You can request deletion of your Didloo account and associated personal data without reinstalling the app. Email your request and registered phone number with country code to our support contact. We verify account ownership before acting. Never email a password or verification code.

Email an account deletion request

In the app, use You → Accounts → Delete Account. Uninstalling or signing out does not delete an account. Read Retention and deletion for retained records and recipient copies.

1. About this policy

1. 1.1 Didloo is operated by AVYCORE TECH PRIVATE LIMITED. This Privacy Policy explains how information is handled when you create a Didloo account and use messaging, calls, groups, profiles, business features, AI tools, referrals, credits and earnings features that are available to you. Read the sections relevant to the features you choose to use.
2. 1.2 Personal information includes information that identifies you directly, such as your phone number, and information that can be associated with your account, such as a device session, profile or transaction. Information you share with another person may also become part of their records.
3. 1.3 This policy describes the app experience and your choices. Availability of a feature may vary by device, app version or region. A separate notice shown for a particular feature should be read alongside this policy before you submit information.

2. Account and registration information

1. 2.1 Didloo processes the phone number and country code you provide to request a verification code, verify access to the number and associate an account with you. Verification requests and authentication sessions are needed to sign you in and protect account access.
2. 2.2 Profile information may include your display name, profile picture, about text and account type. You can provide additional business information if you choose a business profile. Only submit accurate information and pictures you have permission to use.
3. 2.3 Changes to your phone number or profile require processing the updated details. An account identifier connects your profile with conversations, settings and other account records; changing a visible name does not automatically remove those records.

3. Messages and attachments

1. 3.1 The service processes message text and the attachments you send so that conversations can be delivered, displayed and synchronized. Attachments can include images, videos, audio, documents, shared contacts, drawings and other supported content.
2. 3.2 Message records can include the sender, conversation, timestamps, delivery state, replies, edits and other information needed to show the conversation. Message and media history may be retrieved from service infrastructure when you open a chat or use another device.
3. 3.3 Recipients can save, copy, forward, photograph or otherwise keep content you share. Removing content from your own view does not necessarily remove a recipient copy, a download or an externally saved file. Consider the sensitivity of information before sending it.

4. Voice and video calls

1. 4.1 Calls use microphone access and video calls also use camera access. Call setup processes participant and session information, connectivity details and call events so devices can establish a connection and display call status.
2. 4.2 Network services involved in connecting a call may process technical connection information. Call availability and quality depend on your connection, your device and the other participants. Declining microphone or camera access limits the corresponding call feature.
3. 4.3 Call history and conversation events may include participants, time and call outcome. Another participant may capture content using their device or another tool. Obtain any consent required before recording or sharing a conversation.

5. Contacts and address book synchronization

1. 5.1 If you grant contact access and choose synchronization, Didloo reads contact names and phone numbers and sends the selected address book information to the service to match contacts with accounts and make it easier to find people you know.
2. 5.2 Your address book can contain information about people who do not use Didloo. Only synchronize information you are entitled to share for this purpose. Contact names saved by you may differ from the names those people use on their own profiles.
3. 5.3 You can decline contact synchronization during onboarding or revoke contact permission in device settings. Revoking device permission stops future access from that permission; it does not automatically erase information already synchronized with the service.

6. Camera, microphone, photos and files

1. 6.1 Camera permission enables taking pictures or videos and video calls. Microphone permission enables voice recording and audio calls. Access is controlled through your operating system, and you can change permission choices in device settings.
2. 6.2 Photo, media or file access lets you select attachments, create a profile picture or save supported media. Depending on the operating system, a system picker may give access only to the items you select instead of your entire library.
3. 6.3 Media can reveal faces, surroundings, documents and embedded information. Review files before uploading them. If you deny a permission, other features may still work, while the feature requiring that permission may be unavailable.

7. Verification messages

1. 7.1 A verification code is used to confirm access to the phone number you register. Supported devices may offer automatic verification-code reading or a consent-based SMS prompt to make entry easier.
2. 7.2 Automatic code entry depends on the operating system and your choices. You can enter a code manually when automatic entry is unavailable. Never disclose a verification code to someone who claims they need it to fix or verify your account.
3. 7.3 Verification requests may be subject to rate limits and security checks. Phone numbers, request identifiers and verification outcomes are processed to complete authentication and reduce repeated or abusive requests.

8. Device and session information

1. 8.1 The app and service process technical information needed for operation, such as session credentials, device connections, push notification registration, app settings and network requests. Service systems may receive IP addresses and request timestamps.
2. 8.2 Linked devices have their own sessions and may access account conversations and other synchronized data. A device name helps you recognize a session but is not proof of who is using that device.
3. 8.3 Keep your devices protected and review linked sessions regularly. Signing out or removing a linked device limits its future account access, but cannot recall content already downloaded, copied or saved on that device.

9. Notifications and background activity

1. 9.1 Push services process device registration information to deliver message and call notifications. Depending on your app and device settings, a notification preview may display a sender name or message information on the lock screen.
2. 9.2 Background synchronization may refresh contacts, conversation information or incoming call state when permitted by your operating system. Timing depends on battery settings, network conditions and device restrictions.
3. 9.3 You can adjust notification previews and permissions through app or device settings. Disabling notifications affects alerts; it does not necessarily stop messages from being delivered to your account.

10. Privacy settings and visibility

1. 10.1 Privacy controls let you manage supported visibility choices such as read receipts, last seen and online status. The current app applies reciprocal behavior to these controls, so disabling a setting may also hide that information about other people from you.
2. 10.2 Profile information, group membership and content you post can be visible to people who interact with you through the relevant feature. Choose a display name, avatar and business description with that audience in mind.
3. 10.3 Privacy settings do not prevent another user from retaining information they already saw. They also do not replace device security, careful sharing or any permission required when you include another person in content.

11. Groups and shared spaces

1. 11.1 Group features process membership, roles, group details and messages to operate shared conversations. Your participation and messages may be visible to other members according to the group experience.
2. 11.2 Administrators and members may add people, change group details or share content where their role allows it. Review group participants before sharing private information and avoid posting personal information about someone without permission.
3. 11.3 Leaving a group does not automatically remove historic content or copies retained by others. Group administration decisions are separate from your own account and device privacy choices.

12. Business profiles and interactions

1. 12.1 If you use a business profile, information you enter may include a business name, description and contact or action details. This information helps users recognize and interact with the business.
2. 12.2 When you contact a business, that business receives the information you send and may process it under its own practices. Ask the business about its handling of orders, customer records and any information requested outside Didloo.
3. 12.3 A displayed profile, badge or business description should not be treated as a guarantee about a business transaction. Avoid sending identity documents, payment credentials or confidential records unless they are necessary and the recipient is trusted.

13. AI features and generated content

1. 13.1 When you use an AI feature, your prompts and any submitted reference content must be processed to generate the requested result. Processing may involve the service and the provider supporting that particular AI feature.
2. 13.2 Do not place passwords, verification codes, payment credentials or unnecessary personal information in a prompt. Obtain permission before submitting someone else's images, voice, documents or confidential content.
3. 13.3 Generated content may contain personal information from what you submit or infer details incorrectly. Review results before sharing them. Any provider-specific retention or training notice shown for an AI feature should be checked before use.

14. Credits, rewards, referrals and earnings

1. 14.1 Credit and earnings features process balances, eligible activity, referral associations and transaction records to show available benefits and administer the relevant program. Program availability and eligibility depend on the feature rules shown in the app.
2. 14.2 Reward-related activity can include completion or viewing events and other information necessary to determine whether an action qualifies. Attempts to manipulate eligibility may be investigated using related account and activity records.
3. 14.3 If a feature requests payment or payout information, provide it only through the indicated trusted flow and review that flow's notice. Do not send bank credentials or verification codes in an ordinary chat to arrange a reward or payout.

15. Diagnostics and service operation

1. 15.1 The app can send navigation events identifying a screen you opened for service diagnostics. The navigation recording function sends a screen label; it does not include the screen's form contents, message text or contact details in that event.
2. 15.2 Technical errors, request status and operational records can help diagnose failures, prevent abuse and maintain reliability. Information in a support report you choose to submit may include additional details you provide yourself.
3. 15.3 When describing a problem, share only what is needed to investigate it. Remove private messages, other people's phone numbers and sensitive images from screenshots unless they are essential to the request.

16. Why information is processed

1. 16.1 Information is used to establish your account, authenticate sessions, deliver messages and calls, synchronize supported features and apply the settings you choose. Different features require different information; optional permissions are not a requirement for every part of the app.
2. 16.2 Related records may also be needed to maintain security, investigate misuse, resolve a failed transaction or respond to a request concerning your account. Processing should be tied to the purpose of the feature or the applicable obligation.
3. 16.3 Where consent or another legal basis is required, the relevant requirement applies to that processing. A device permission is a technical access choice and does not by itself describe every subsequent use of information already submitted.

17. Other users and service providers

1. 17.1 Information is shared with the recipients, group members or businesses involved when you use a communication feature. Your own forwarding, posting or uploading choices determine much of the audience for the content.
2. 17.2 Infrastructure, notification, connectivity, media and AI providers may process information needed to support the features they operate. An external page or service you open may collect information independently under its own notice.
3. 17.3 Information may also need to be disclosed in response to a valid legal requirement or to address security incidents and misuse. Such handling is subject to applicable law; this policy does not promise that all information can always remain undisclosed.

18. Storage and local copies

1. 18.1 Account records and submitted content may be stored on service infrastructure, while the app can retain settings, sessions, conversation information and media locally to operate efficiently. Storage can therefore exist in more than one place.
2. 18.2 Saving an attachment to your gallery or downloading a file creates a copy outside the app's conversation view. Your device backup, photo synchronization or another application may handle that copy under separate settings.
3. 18.3 Use storage controls to manage supported local data and review your operating system's backup settings. Clearing a cache or uninstalling the app is different from requesting removal of server-side account records.

19. Retention and deletion

1. 19.1 Information may be retained while needed to provide the feature, maintain an active account, resolve an outstanding issue or satisfy an applicable legal requirement. Different kinds of records can have different retention needs.
2. 19.2 To request deletion of your Didloo account and associated personal data, use You > Accounts > Delete Account in the app, or email avycoretech@gmail.com without reinstalling the app. Include your registered phone number with country code and state that you want your Didloo account deleted. Never send an OTP or password. We verify account ownership before acting on a request.
3. 19.3 Deletion does not necessarily remove information held independently by recipients or third parties. Records subject to a legal preservation requirement or an unresolved security or transaction issue may need separate handling. This policy does not specify an unverified deletion deadline.

20. Your choices and requests

1. 20.1 You can review and change supported profile details, privacy controls, device permissions and linked sessions. Where available, use the account controls to request account deletion and follow the instructions displayed for that action.
2. 20.2 Depending on the law applicable to you, you may have rights concerning access, correction, erasure, withdrawal of consent, grievance handling or other personal-data requests. These rights depend on applicable conditions and are not identical in every jurisdiction.
3. 20.3 A request may require verification of account ownership to protect your information from unauthorized disclosure or changes. Provide only the information reasonably needed for verification and keep verification codes private.

21. Security and your responsibilities

1. 21.1 Protect your phone, SIM, device passcode and account sessions. Use the official app distribution channel and avoid sharing access with people you do not trust. Inform the appropriate service contact if you suspect unauthorized account use.
2. 21.2 Communication and storage systems have security risks. This policy does not make an unsupported promise that every feature is end-to-end encrypted or that data can never be accessed, lost or disclosed.
3. 21.3 Phishing links, fake profiles and malicious attachments can appear in user content. Verify unusual requests through another trusted method and do not install software or make payments solely because someone contacted you through Didloo.

22. Children and age-related protections

1. 22.1 Users must meet the eligibility conditions in the Terms & Conditions and any applicable age requirements. The service is not intended to bypass requirements concerning children's personal information or parental authorization.
2. 22.2 Do not create an account for a child or submit a child's personal information unless the applicable eligibility and authorization requirements are satisfied. Parents and guardians should supervise the sharing of children's images and contact information.
3. 22.3 If you believe information about a child has been submitted without required authorization, raise the concern through the official contact published for the service. Avoid repeating the child's sensitive information in a public conversation.

23. External links and regional differences

1. 23.1 Links in messages, business profiles and generated content can lead to external websites. Those websites may use cookies, collect device information or ask for additional information under their own privacy practices.
2. 23.2 Information may be handled in locations where the infrastructure or provider supporting a feature operates, subject to applicable requirements. This policy does not specify a data-storage country that has not been verified.
3. 23.3 Additional protections or restrictions may apply based on your location. Applicable legal rights take precedence over wording that cannot lawfully limit them, and a feature may be restricted where its requirements cannot be met.

24. Updates and privacy questions

1. 24.1 This policy may be revised when features or handling practices change. Review the latest version and any specific notice presented before using a newly introduced feature. The displayed revision date helps distinguish versions.
2. 24.2 For privacy questions, account deletion requests, support or complaints, contact AVYCORE TECH PRIVATE LIMITED at avycoretech@gmail.com. Include only the information needed to understand your request; never send passwords or verification codes.
3. 24.3 Privacy and grievance requests are handled by AVYCORE TECH PRIVATE LIMITED through the contact above. We may verify account ownership before providing information or acting on a request. Any applicable statutory rights remain available.