Overview
Mulberry is a paired-device app for two people who share a private drawing canvas that can appear on your device wallpaper (lock screen or home screen): as a live wallpaper on Android, and through a Shortcuts automation you set up on iPhone and iPad. On Mac, the shared canvas can appear on your desktop and in the menu bar. This policy is written for an India-only launch. If Mulberry later becomes available outside India, this policy will be updated before that expansion.
1. Who this policy applies to
This policy applies to people in India who install, access, or use Mulberry. It also applies to information processed when you sign in, pair with another Mulberry user, draw on a shared canvas, send reactions, set up the wallpaper or the Mac desktop overlay, receive push-based canvas updates, use support channels, or request account deletion.
Mulberry is designed for a private two-person experience. It is not designed for public posting, group collaboration, advertising, or broad social networking.
Mulberry is not intended for users under 18 years old.
2. Summary
Mulberry collects account, profile, pairing, device, sync, analytics, diagnostic, and canvas information so the app can authenticate you, pair you with one other user, sync the shared drawing canvas, improve reliability, and show the canvas on your wallpaper or Mac desktop.
The shared canvas is visible to both paired users. Your device-local wallpaper background is intended to stay on your device and is not part of the shared drawing state sent to the Mulberry backend.
Mulberry uses Google Sign-In, and Sign in with Apple on iPhone, iPad, and Mac, for authentication, Firebase Cloud Messaging (delivered through Apple Push Notification service on iPhone, iPad, and Mac) for background canvas update signals and notifications, Firebase Crashlytics for crash diagnostics, PostHog for product analytics, which receives data only through the Mulberry backend, Canny for in-app feedback, Supabase for database services, and Fly.io for backend hosting. Product analytics are linked to your account, including your email address and display name, so Mulberry can understand how the app is used.
Mulberry does not sell your personal information. Mulberry does not share your personal information for targeted advertising. Mulberry does not use shared canvas content for advertising or AI model training.
3. Information we collect
3.1 Account and authentication information
You can sign in to Mulberry with Google on Android, iPhone, iPad, and Mac, or with Apple on iPhone, iPad, and Mac. Mulberry does not receive or need your Google or Apple account password.
3.1.1 Sign in with Google
When you sign in with Google, Mulberry receives information needed to authenticate your account. This may include:
- Your Google account identifier.
- Your email address.
- Your Google display name, if provided by Google.
- The address of your Google profile photo, if provided by Google.
- A Google ID token used for sign-in verification.
- Mulberry access and refresh tokens created by the Mulberry backend.
- Account and session identifiers created by Mulberry.
Mulberry uses the Google ID token to verify your identity. The Mulberry backend stores your Mulberry user identifier, Google subject identifier, email address, the address of your Google profile photo, profile row, and Mulberry session tokens. Signing in with Google keeps your account's email address up to date with your Google account.
On Mac, Google Sign-In opens in your web browser. When you finish signing in, Google returns you to Mulberry through a temporary address that exists only on your Mac for the length of the sign-in.
3.1.2 Sign in with Apple
When you sign in with Apple, Apple shows you what it will share with Mulberry before you continue. Mulberry may receive:
- An identifier for your Apple Account that Apple creates for Mulberry. It is not your Apple Account email address.
- An email address. Apple lets you share your own email address, or hide it with Hide My Email. If you hide it, Mulberry receives a unique relay address, and Apple forwards messages sent to that address to your own email address.
- Your name, if you choose to share it. Apple shares it only the first time you sign in to Mulberry with Apple.
- An identity token and a one-time authorization code, used for sign-in verification.
- Mulberry access and refresh tokens created by the Mulberry backend.
- Account and session identifiers created by Mulberry.
Mulberry verifies the identity token with Apple, and exchanges the authorization code with Apple for a refresh token. The Mulberry backend stores your Mulberry user identifier, Apple identifier, the email address Apple shares, Apple's refresh token and the Mulberry app it was issued to, profile row, and Mulberry session tokens. Mulberry keeps Apple's refresh token only so it can ask Apple to revoke Mulberry's access when you delete your account. If you share your name, Mulberry uses it as your starting display name, which you can change. Apple does not share a profile photo.
On iPhone, iPad, and Mac, Sign in with Apple runs in a system sheet provided by Apple. You can see or stop Mulberry's use of Sign in with Apple, and manage Hide My Email, in your Apple Account settings.
3.1.3 Using both Google and Apple
If you sign in with Google and with Apple using the same email address, and Google or Apple has verified that address, Mulberry signs you in to the same Mulberry account rather than creating a second one. A Hide My Email relay address does not match an existing account. If an email address already belongs to a Mulberry account that uses a different Google or Apple account, Mulberry asks you to sign in the way you did before.
You can also add Google or Apple as a way to sign in from the Sign In section of Mulberry's settings on iPhone, iPad, and Mac. Mulberry then stores that provider's identifier with your account, and for Apple, Apple's refresh token, as described above.
3.2 Profile and onboarding information
During onboarding or account setup, Mulberry may collect:
- Your display name.
- Your partner's display name.
- Profile photos you choose to upload for yourself or your partner.
- Your relationship anniversary date.
- Whether onboarding is complete.
- Whether your wallpaper, or on Mac the desktop overlay, has been set up.
This information is used to personalize the paired experience and to help both users understand invite and pairing flows.
3.3 Pairing and invite information
When you create, redeem, accept, or decline an invite, Mulberry may collect and store:
- Invite identifiers.
- Six-digit invite codes.
- Invite status, such as pending, redeemed, accepted, declined, or expired.
- Invite expiration timestamps.
- The user identifiers for the inviter and, after redemption, the recipient.
- Pair session identifiers for accepted pairings.
- Timestamps for invite creation and consumption.
Invite codes are used to connect exactly two users into a private pair session. Anyone with a valid invite code may be able to start the pairing flow, so you should share invite codes only with the person you intend to pair with.
3.4 Shared canvas and drawing information
Mulberry stores and synchronizes drawing data that you or your paired partner create on the shared canvas. This may include:
- Strokes, stroke identifiers, colors, brush widths, and point coordinates.
- Text and stickers placed on the canvas, with their position, size, rotation, color, and font.
- Reactions you send to your paired partner, such as hearts or hugs: the kind of each reaction, when you sent it, and how many of each are waiting for your partner.
- Drawing operations such as adding strokes, appending points, finishing strokes, deleting strokes, and clearing the canvas.
- Client operation identifiers, operation batches, and timestamps.
- Server-assigned revision numbers.
- Actor user identifiers showing which paired user created an operation.
- Canvas snapshots used for recovery and synchronization.
- Cached local render state used to draw the current canvas, your wallpaper, and the Mac desktop overlay.
The shared canvas may reveal personal information if you or your paired partner draw, write, or display it there. Do not put information on the shared canvas that you do not want your paired partner, Mulberry systems, or authorized service providers to process.
Mulberry does not use shared canvas content for advertising or AI model training.
3.5 Device, app, analytics, and technical information
Mulberry may collect technical information needed to operate, secure, diagnose, and improve the app, including:
- App environment, such as development or production.
- Device platform (Android, iOS, iPadOS, or macOS), device type (Android phone or tablet, iPhone, iPad, or Mac), and app build number.
- Your device's time zone, such as Asia/Kolkata, and when it changes, so times on the shared canvas can be shown in your local time.
- Firebase Cloud Messaging registration tokens on Android, iPhone, iPad, and Mac.
- On Mac, a random identifier created for each Mac installation, whether the desktop overlay is showing, the name of the display it is on, and its sync state.
- A random identifier the app creates once for each installation, so analytics events from before you sign in can be linked to your account. It is not an advertising identifier, and it stays until you delete the app.
- Token registration, last-seen, and revocation timestamps.
- Sync status, last applied server revision, pending operation data, and last sync error stored locally.
- App configuration values required to reach the Mulberry API.
- Crash, error, and diagnostic information through Firebase Crashlytics. On iPhone, iPad, and Mac, Mulberry does not attach your account to crash reports.
- Product analytics events in PostHog, sent only through the Mulberry backend. Some are recorded by the backend, such as canvas activity, invite and pairing events, reactions sent, and the days and weeks a pair is active. Others are sent by the app, such as the onboarding and pairing screens you see, your steps through wallpaper, Shortcut, and Mac desktop overlay setup, and the notifications you open. Analytics events never include what is drawn, written, or placed on the shared canvas.
- A PostHog profile linked to your account, with your email address, display name, sign-in method, device types, and app build. While you are paired, your profile and your pair's record in PostHog also include both partners' display names and email addresses.
- Whether your wallpaper setup or Mac desktop overlay is working and whether doodles are shown on it. Mulberry shares this with your paired partner so they know whether you can see their latest drawings.
- Backend operational logs, kept on Fly.io, where the backend runs.
Production logs are not intended to include device identifiers, user identifiers, or canvas payloads. Backend logs may include operational details needed to run the service, such as timestamps, route names, status codes, and error categories.
Analytics and diagnostic providers may process technical information according to their own systems and privacy policies. Mulberry uses these tools to understand whether the app is working, identify crashes, improve reliability, and prioritize product fixes.
3.6 Local wallpaper and device storage information
Mulberry lets you choose a private background image for the live wallpaper. That background image is intended to stay on your device. Mulberry stores a local copy of the selected or bundled background so the live wallpaper can render after the app is closed.
Local app storage may also include:
- Access and refresh tokens.
- Cached profile and pairing state.
- Pending invite details.
- FCM token registration state.
- Local Room database records for strokes, points, operations, canvas metadata, and cached snapshot paths.
- Local DataStore preferences.
- Cached images used by the wallpaper renderer.
On iPhone and iPad, Mulberry keeps sign-in tokens in the iOS Keychain and stores cached account and canvas state, drawing tool settings, sticker artwork, and rendered wallpaper images in the app's own storage. Your chosen wallpaper background, the cached shared canvas, and downloaded sticker artwork are excluded from iCloud and device backups.
On Mac, Mulberry keeps sign-in tokens in the macOS Keychain and stores cached account and canvas state, sticker artwork, and app preferences, such as the desktop overlay's display and position, the Quick Draw keyboard shortcut, and whether Mulberry opens at login, in the app's own storage. To greet you when you sign in again, the Mac also remembers the name and profile photo address of the last account signed in to it. This stays after you log out and is erased when you delete your account. The cached shared canvas and downloaded sticker artwork are excluded from Time Machine and other backups.
Mulberry excludes local app data from Android cloud backup and device transfer where technically possible. If you manually export, copy, screenshot, record, or otherwise share local app data outside Mulberry, that external sharing is outside Mulberry's control.
3.7 Information from support communications
If you contact Mulberry for support or privacy requests, Mulberry may collect your name, email address, message contents, diagnostic details you choose to provide, and any other information needed to respond.
If you use Send feedback in the app, your feedback goes to Canny, a feedback service. Mulberry signs you in to Canny with your Mulberry account identifier, display name, email address, and, if you sign in with Google, your Google profile photo, so Canny stores your feedback, votes, and comments with those details.
3.8 Information we do not intentionally collect
Mulberry does not intentionally collect payment card information, government identification numbers, precise GPS location, biometric identifiers, health data, or contacts.
On Mac, Mulberry does not record your screen or your keystrokes. The Quick Draw keyboard shortcut is registered with macOS, which tells Mulberry only when that shortcut is pressed.
Mulberry does not intentionally collect the private contents of your Google or Apple account beyond the information provided through Google Sign-In or Sign in with Apple for authentication.
Mulberry does not intentionally collect the device-local wallpaper background through the backend. If you choose a personal photo as your local background, it is intended to remain on your device.
Mulberry does not intentionally include device identifiers, user identifiers, or canvas payloads in production logs.
4. How we collect information
Mulberry collects information in these ways:
- Directly from you when you sign in, complete onboarding, create or redeem an invite, draw on the shared canvas, choose a wallpaper background, request account deletion, or contact support.
- Automatically through the app and backend when Mulberry authenticates sessions, syncs canvas operations, registers FCM tokens, refreshes canvas state, records analytics events, including events the app sends about the screens and setup steps you use, records crash diagnostics, or records operational logs needed to run the service.
- From your paired partner when that person creates shared canvas operations or participates in the pairing flow.
- From service providers such as Google Sign-In, Sign in with Apple, Firebase Cloud Messaging, Apple Push Notification service, Firebase Crashlytics, Canny, PostHog, Supabase, and Fly.io when they provide authentication, hosting, logging, analytics, diagnostic, feedback, database, or push-delivery functionality.
5. How we use information
Mulberry uses information for the following purposes:
- To create and authenticate your Mulberry account.
- To verify Google Sign-In and Sign in with Apple tokens.
- To sign you in to one Mulberry account when you use both Google and Apple.
- To maintain Mulberry access and refresh sessions.
- To save and update your profile and onboarding state.
- To create, redeem, accept, decline, expire, and manage pairing invites.
- To connect exactly two users into a private pair session.
- To send, receive, order, replay, and reconcile shared canvas operations.
- To maintain server-side canvas snapshots for sync recovery.
- To render and cache the shared canvas locally on your device.
- To update your wallpaper with the latest canvas: the live wallpaper on Android, or the wallpaper image the Mulberry Shortcut sets on iPhone and iPad.
- To show the shared canvas on your Mac desktop and in the menu bar.
- To show you and your paired partner summaries of your time together on the shared canvas, such as your drawing and reaction activity over a year, in your local time.
- To show your paired partner's reactions over the canvas, on iPhone in the Dynamic Island and on the Lock Screen while they are fresh, and on Mac at the top of your screen.
- To register and unregister Firebase Cloud Messaging tokens.
- To send minimal push signals so backgrounded devices can catch up to the latest canvas revision.
- To identify crashes, errors, performance issues, and reliability problems.
- To understand product usage, such as where people stop during onboarding, pairing, and wallpaper setup, and to measure feature health.
- To troubleshoot reliability, sync, authentication, and pairing problems.
- To protect the service from misuse, fraud, unauthorized access, or abuse.
- To comply with legal obligations and enforce applicable terms.
- To respond to support, privacy, security, or legal requests.
- To collect and respond to feedback you send through Canny.
- To process account deletion and other privacy requests, including asking Apple to revoke Mulberry's Sign in with Apple access when you delete your account.
Mulberry does not use shared canvas content for third-party advertising, targeted advertising, or AI model training.
7. Push notifications and background sync
Mulberry uses Firebase Cloud Messaging to help backgrounded devices catch up when the shared canvas changes. Push payloads are intended to contain limited routing and revision metadata, such as:
- Message type.
- Pair session identifier.
- Latest canvas revision.
- Snapshot revision.
- Actor user identifier.
- Reaction counts for each kind of reaction.
Push payloads are not intended to contain full drawing content. When a device receives a canvas update signal, the app may contact the Mulberry backend to fetch missed canvas operations or the latest canvas snapshot.
Firebase Cloud Messaging is provided by Google. Google may process device, token, delivery, and diagnostic information according to Google's terms and privacy policies.
On iPhone, iPad, and Mac, Firebase Cloud Messaging delivers through Apple Push Notification service, provided by Apple. Some notifications, such as pairing changes and reminders, show a short title and message. Mulberry may also schedule local notifications on your device, such as the wallpaper update signal your Shortcut responds to and reminders while doodles are hidden from your wallpaper.
On iPhone, when your paired partner sends reactions, Mulberry may show them as a Live Activity on your Lock Screen and in the Dynamic Island, with your partner's name, a small copy of their profile photo, and the reactions. You can turn off Live Activities for Mulberry in iOS Settings.
On Mac, push signals tell Mulberry about canvas changes and reactions so it can fetch them from the Mulberry backend, and some notifications, such as pairing changes and reminders, show a short title and message. Mulberry also checks the Mulberry backend for changes while it is running, and may show local notifications created on your Mac, such as when your partner joins you. You can turn notifications off in macOS System Settings.
8. Legal basis and lawful use in India
Mulberry is intended for users in India. Mulberry processes personal data to provide requested app functionality, maintain account and pairing services, keep the shared canvas synchronized, secure the service, diagnose issues, understand product health, respond to requests, and comply with applicable Indian law.
Where consent is required, Mulberry will rely on your consent. You may withdraw consent by stopping use of optional features, changing device or app settings where available, deleting your account, or contacting subha60kundu@gmail.com. Withdrawal of consent may prevent Mulberry from providing some or all app features.
Mulberry does not appoint a Data Protection Officer, EU representative, or UK representative because Mulberry is operated from India and is intended for India-only availability.
10. Third-party services
Mulberry currently uses:
- Google Sign-In, with Android Credential Manager on Android and your web browser on Mac, for account authentication.
- Sign in with Apple on iPhone, iPad, and Mac for account authentication.
- Firebase Cloud Messaging for push update signals and notifications.
- Apple Push Notification service for notifications on iPhone, iPad, and Mac.
- Firebase Crashlytics for crash diagnostics.
- Canny for in-app feedback.
- PostHog for product analytics and feature usage insights, sent through the Mulberry backend.
- Supabase for database services.
- Fly.io for backend hosting and operational logs.
These services may process information in India and other countries where they or their infrastructure providers operate. Their processing is governed by their own terms and privacy policies in addition to Mulberry's instructions where applicable.
12. Data retention
Mulberry generally keeps personal data only as long as needed to provide the app, maintain security and reliability, comply with legal obligations, or resolve support and privacy requests.
Unless a longer period is required by law or needed for an active dispute, security incident, fraud investigation, or legal obligation, Mulberry uses the following retention approach:
- Account and profile data, including your Google or Apple identifier, Apple's refresh token, and the time zones your devices report, are retained while your account is active. When you delete your account in the app, they are deleted from Mulberry's database straight away. Copies in backups or provider records are deleted or anonymized within 30 days.
- Access and refresh sessions are retained while active. Revoked, expired, or replaced sessions are deleted or anonymized within 30 days.
- Device and FCM tokens are retained while active. Revoked or inactive tokens are deleted or anonymized within 30 days.
- Invite records are retained while active and for up to 30 days after expiry, acceptance, decline, or cancellation.
- Pairing records are retained while the pair session is active. After pair deletion or account deletion that ends the pair, they are deleted or anonymized within 30 days.
- Canvas operations, sent reactions, and snapshots are retained while needed to provide synchronization, ordering, replay, recovery, and paired canvas functionality. After account deletion, pair deletion, or canvas deletion that removes the relevant pair data, they are deleted or anonymized within 30 days.
- Your PostHog profile, with your email address and display name, is retained while your account is active and deleted when you delete your account.
- Analytics events, diagnostic, and operational log data are retained for up to 30 days where Mulberry controls the retention period.
- Firebase Crashlytics keeps crash reports for up to 90 days under its own retention settings. Crash reports from iPhone, iPad, and Mac are not linked to your account.
- Support and privacy request emails are retained for up to 30 days after the request is resolved, unless a longer period is required by law or needed to protect rights, safety, or the service.
- Local app data remains on your device until you log out, clear app data, remove local backgrounds, uninstall the app, delete your account, or the app deletes or overwrites cached data.
Third-party service providers may keep some operational records under their own retention settings and legal obligations. Mulberry configures provider retention to align with the 30-day approach where practical.
13. Account deletion
13.1 How to delete your account
- On iPhone and iPad: open Settings in Mulberry and tap "Delete your account", below Log Out.
- On Mac: open Mulberry's Settings, choose Account, and click "Delete your account", below the Sign In section.
- On Android, or if you no longer have access to a signed-in device: email subha60kundu@gmail.com from the email address you use with Mulberry. Mulberry may ask for reasonable verification and will complete verified requests within 30 days.
Mulberry asks you to confirm before deleting. Deletion cannot be undone.
13.2 What deletion removes
When you delete your account in the app, Mulberry deletes the following from its database straight away:
- Your account, profile, and sign-in sessions on every device.
- Profile photos you uploaded, unless your paired partner's own profile still uses that photo.
- Device and push tokens.
- Pending invites.
- Your pairing, including the shared canvas, its operations and snapshots, your streak and activity history together, reminders, and reactions.
Mulberry also deletes your PostHog profile, which holds your email address and display name.
The device you delete your account from also erases its own copy of your Mulberry data, such as the cached canvas, rendered wallpaper images, and account settings. If you signed in with Apple, Mulberry asks Apple to revoke Mulberry's Sign in with Apple access. If you signed in with Google on iPhone or iPad, Mulberry also asks Google to revoke Mulberry's access to your Google account. On Mac, you can remove Google access yourself in your Google Account's security settings. Other devices where you were signed in are signed out when they next connect to Mulberry. Delete the app on those devices to remove what they kept locally.
13.3 What happens for your paired partner
Your paired partner keeps their own account. Your pairing ends for both of you, and the shared canvas, streak, and activity history you had together are deleted. Your partner is told the pairing has ended, as they would be if you had unpaired. Your partner may still have screenshots, recordings, exports, or memories of shared canvas content they saw before deletion. Mulberry cannot delete copies your partner saved outside Mulberry.
13.4 What may remain
- Copies in backups or provider records, which are deleted or anonymized within 30 days.
- Product analytics events, which are kept for up to 30 days. Once your PostHog profile is deleted, they carry only Mulberry identifiers, not your email address or name.
- Crash reports, which are not linked to your account and are kept by Firebase Crashlytics for up to 90 days.
- Feedback you sent through Canny. Contact subha60kundu@gmail.com to have it removed.
- Records Mulberry must keep longer where required by law or needed for security, fraud prevention, dispute resolution, or enforcement.
Deleting the app from your device does not delete your Mulberry account. Use the account deletion option in the app, or contact subha60kundu@gmail.com.
14. Your choices and controls
You may have the following controls:
- You can choose whether to sign in with Google or, on iPhone, iPad, and Mac, with Apple, and whether to share your name and real email address with Mulberry when you sign in with Apple.
- You can choose whether to create, redeem, accept, or decline a pairing invite.
- You can choose what to draw on the shared canvas.
- You can change or remove your device-local wallpaper background in the app where supported.
- You can log out, which removes or clears certain local session state and unregisters the current FCM token where possible.
- You can stop using Sign in with Apple with Mulberry in your Apple Account settings.
- You can delete your account in Mulberry's settings on iPhone, iPad, and Mac, or by email from Android, as described in section 13.
- You can clear local app data through Android system settings, or on iPhone and iPad by deleting the app. On Mac, moving Mulberry to the Trash may leave its local data in your user Library folder. Deleting your account from the Mac erases it.
- You can hide doodles from your wallpaper in Mulberry's settings. Your paired partner is told that you cannot see their latest drawings.
- On iPhone and iPad, you can turn notifications and Live Activities for Mulberry on or off in iOS Settings, and turn off the wallpaper automation in the Shortcuts app.
- On Mac, you can hide the desktop overlay, change the Quick Draw shortcut, choose whether Mulberry opens at login (off unless you turn it on), and turn notifications on or off in macOS System Settings.
- You can uninstall the app to remove app-managed local storage from your device.
- You can manage Google account controls, Apple Account controls, and Android, iOS, iPadOS, or macOS privacy settings through Google, Apple, and system controls.
Some choices may limit app functionality. For example, if you do not sign in, Mulberry cannot pair your account or sync the shared canvas. If FCM token registration is unavailable, backgrounded devices may not catch up until the app reconnects.
15. Privacy rights
Subject to applicable Indian law, you may request to:
- Access information Mulberry holds about you.
- Correct inaccurate or incomplete information.
- Delete your account and associated personal data.
- Withdraw consent where processing depends on consent.
- Raise a grievance or complaint about Mulberry's handling of your information.
- Ask questions about this policy or Mulberry's data practices.
To make a privacy request, contact subha60kundu@gmail.com. Mulberry may need to verify your identity before responding to certain requests. Mulberry will try to respond within a reasonable time and, where possible, complete deletion, correction, or access actions within 30 days.
16. International processing
Mulberry is intended for users in India, but some service providers may process information outside India. This may include Google, Firebase, Apple, Canny, PostHog, Supabase, Fly.io, and their infrastructure providers.
By using Mulberry, you understand that your information may be processed in countries where these providers operate, subject to this policy, provider terms, applicable law, and appropriate contractual or technical safeguards.
17. Security
Mulberry uses reasonable technical and organizational measures designed to protect information, including authenticated API requests, server-side session checks, access controls, and encrypted transport for production network communication.
Mulberry stores authentication tokens and app state locally on the device so the app can work across launches and keep the canvas synchronized. On iPhone, iPad, and Mac, sign-in tokens are kept in the Apple Keychain. You should protect your device with a passcode, biometric unlock, or other device security feature.
Mulberry excludes local app data from Android backup where technically possible to reduce the chance that local tokens, cached canvas state, or local wallpaper assets are copied through platform backup.
Production logs are not intended to include device identifiers, user identifiers, or canvas payloads.
No method of transmission or storage is completely secure. Mulberry cannot guarantee absolute security.
Development builds may use local development servers or cleartext local network traffic for testing. Production builds should use secure transport to the production API.
18. Children's privacy
Mulberry is not intended for users under 18 years old. Mulberry does not knowingly collect personal data from children or minors.
If you believe a person under 18 has provided information to Mulberry, contact subha60kundu@gmail.com so the information can be reviewed and deleted where appropriate.
19. Sensitive information
Mulberry is designed for personal communication between two paired users. The app may process relationship-related information that you choose to provide, such as your partner's display name, relationship anniversary date, and shared drawings.
Do not use Mulberry to share highly sensitive information unless you understand that it may be visible to your paired partner and processed by Mulberry systems as described in this policy.
Mulberry does not intentionally collect government identification numbers, financial account data, health data, biometric data, precise GPS location, or contacts.
20. Third-party links and services
Mulberry may link to or rely on third-party services that are not controlled by Mulberry. This policy does not apply to third-party websites, apps, services, or privacy practices. Review those third parties' privacy policies before using them.
21. Changes to this policy
Mulberry may update this Privacy Policy from time to time. If changes are material, Mulberry will provide notice by email at least 30 days before the material changes take effect, unless a shorter period is required for legal, security, or operational reasons.
The "Last updated" date at the top of this policy shows when it was last changed.
22. Contact and grievance
For privacy questions, requests, complaints, or grievances, contact:
Subhajit Kundu
ITI Crossing, Kalyani, West Bengal, India, 741235
Email: subha60kundu@gmail.com
Mulberry has not appointed a Data Protection Officer, EU representative, or UK representative because Mulberry is operated from India and is intended for India-only availability.
Please include enough information for Mulberry to understand and respond to your request. For security, Mulberry may need to verify your identity before fulfilling certain privacy requests.