Privacy Policy

Fun.Do Privacy Policy

Last updated: May 10, 2021

This Privacy Policy describes our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You.

We use Your Personal data to provide and improve the Service. By using the Service, You agree to the collection and use of information in accordance with this Privacy Policy.

Interpretation and Definitions


The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.


For the purposes of this Privacy Policy:

  • Account means a unique account created for You to access our Service or parts of our Service.
  • FUN.DO is referred to as either “We”, “Us” or “Our” in this Agreement.
  • Cookies are small files that are placed on Your computer, mobile device or any other device by a website, containing the details of Your browsing history on that website among its many uses.
  • Country refers to: West Bengal, India
  • Device means any device that can access the Service such as a computer, a cellphone or a digital tablet.
  • Personal Data is any information that relates to an identified or identifiable individual.
  • Service refers to the Website.
  • Service Provider means any natural or legal person who processes the data on behalf of the Company. It refers to third-party companies or individuals employed by the Company to facilitate the Service, to provide the Service on behalf of the Company, to perform services related to the Service or to assist the Company in analyzing how the Service is used.
  • Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).
  • You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.

Collecting and Using Your Personal Data

Types of Data Collected

Personal Data

While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to contact or identify You. Personally identifiable information may include, but is not limited to:

  • Email address
  • First name and last name
  • Phone number
  • Address, State, Province, ZIP/Postal code, City
  • Usage Data

Usage Data

Usage Data is collected automatically when using the Service.

Usage Data may include information such as Your Device’s Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

When You access the Service by or through a mobile device, We may collect certain information automatically, including, but not limited to, the type of mobile device You use, Your mobile device unique ID, the IP address of Your mobile device, Your mobile operating system, the type of mobile Internet browser You use, unique device identifiers and other diagnostic data.

We may also collect information that Your browser sends whenever You visit our Service or when You access the Service by or through a mobile device.

Tracking Technologies and Cookies

We use Cookies and similar tracking technologies to track the activity on Our Service and store certain information. Tracking technologies used are beacons, tags, and scripts to collect and track information and to improve and analyze Our Service. The technologies We use may include:

  • Cookies or Browser Cookies.A cookie is a small file placed on Your Device. You can instruct Your browser to refuse all Cookies or to indicate when a Cookie is being sent. However, if You do not accept Cookies, You may not be able to use some parts of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service may use Cookies.
  • Flash Cookies.Certain features of our Service may use local stored objects (or Flash Cookies) to collect and store information about Your preferences or Your activity on our Service. Flash Cookies are not managed by the same browser settings as those used for Browser Cookies. For more information on how You can delete Flash Cookies, please read “Where can I change the settings for disabling, or deleting local shared objects?” available at
  • Web Beacons. Certain sections of our Service and our emails may contain small electronic files known as web beacons (also referred to as clear gifs, pixel tags, and single-pixel gifs) that permit the Company, for example, to count users who have visited those pages or opened an email and for other related website statistics (for example, recording the popularity of a certain section and verifying system and server integrity).

Cookies can be “Persistent” or “Session” Cookies. Persistent Cookies remain on Your personal computer or mobile device when You go offline, while Session Cookies are deleted as soon as You close Your web browser. Learn more about cookies: What Are Cookies?.

We use both Session and Persistent Cookies for the purposes set out below:

  • Necessary / Essential Cookies

Type: Session Cookies

Administered by: Us

Purpose: These Cookies are essential to provide You with services available through the Website and to enable You to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts. Without these Cookies, the services that You have asked for cannot be provided, and We only use these Cookies to provide You with those services.

  • Cookies Policy / Notice Acceptance Cookies

Type: Persistent Cookies

Administered by: Us

Purpose: These Cookies identify if users have accepted the use of cookies on the Website.

  • Functionality Cookies

Type: Persistent Cookies

Administered by: Us

Purpose: These Cookies allow us to remember choices You make when You use the Website, such as remembering your login details or language preference. The purpose of these Cookies is to provide You with a more personal experience and to avoid You having to re-enter your preferences every time You use the Website.

For more information about the cookies we use and your choices regarding cookies, please visit our Cookies Policy or the Cookies section of our Privacy Policy.

Use of Your Personal Data

We may use Personal Data for the following purposes:

  • To provide and maintain our Service, including to monitor the usage of our Service.
  • To manage Your Account: to manage Your registration as a user of the Service. The Personal Data You provide can give You access to different functionalities of the Service that are available to You as a registered user.
  • For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased or of any other contract with Us through the Service.
  • To contact You: To contact You by email, telephone calls, SMS, or other equivalent forms of electronic communication, such as a mobile application’s push notifications regarding updates or informative communications related to the functionalities, products or contracted services, including the security updates, when necessary or reasonable for their implementation.
  • To provide You with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless You have opted not to receive such information.
  • To manage Your requests: To attend and manage Your requests to Us.
  • For business transfers: We may use Your information to evaluate or conduct a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Our assets, whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, in which Personal Data held by Us about our Service users is among the assets transferred.
  • For other purposes: We may use Your information for other purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns and to evaluate and improve our Service, products, services, marketing and your experience.
  • We may share Your personal information in the following situations:
  • With Service Providers: We may share Your personal information with Service Providers to monitor and analyze the use of our Service, to contact You.
  • For business transfers: We may share or transfer Your personal information in connection with, or during negotiations of, any merger, sale of our assets, financing, or acquisition of all or a portion of Our business to another business.
  • With Your consent: We may disclose Your personal information for any other purpose with Your consent.

Retention of Your Personal Data

We will retain Your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.

We will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of Our Service, or We are legally obligated to retain this data for longer time periods.

Transfer of Your Personal Data

Your information, including Personal Data, is processed at the our operating place and in any other places where the parties involved in the processing are located. It means that this information may be transferred to — and maintained on — computers located outside of Your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from Your jurisdiction.

Your consent to this Privacy Policy followed by Your submission of such information represents Your agreement to that transfer.

We will take all steps reasonably necessary to ensure that Your data is treated securely and in accordance with this Privacy Policy and no transfer of Your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of Your data and other personal information.

Disclosure of Your Personal Data

Business Transactions

If we are involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy.

Law enforcement

Under certain circumstances, we may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).

Other legal requirements

We may disclose Your Personal Data in the good faith belief that such action is necessary to:

  • Comply with a legal obligation
  • Protect and defend the rights or our property
  • Prevent or investigate possible wrongdoing in connection with the Service
  • Protect the personal safety of Users of the Service or the public
  • Protect against legal liability

Security of Your Personal Data

The security of Your Personal Data is important to Us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While We strive to use commercially acceptable means to protect Your Personal Data, We cannot guarantee its absolute security.

Children’s Privacy

FUN.DO mandates that users of 13 years of age and below must have parent’s permission to participate in various contests and classes organized by FUN.DO . Furthermore, to get consent of the parent, before uploading their child’s work on our website or social media as a part of the contest, an email is sent on the parents email ID provided during registration or through whatsapp group created for this purpose . We do not knowingly collect any other personally identifiable information from anyone other than the information submitted by users to participate their child as a contestant or for our learning program.


FUN.DO is a community. We offer several features that allow members to connect and communicate in public or semi-public spaces. Please be sensible and judge before posting in these community spaces or sharing your personal information with others on our website. Be aware that any personal information you submit there can be read, collected, or used by others, or could be used to send you unsolicited messages.


Links to Other Websites

Our Service may contain links to other websites that are not operated by Us. If You click on a third party link, You will be directed to that third party’s site. We strongly advise You to review the Privacy Policy of every site You visit.

We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.

Changes to this Privacy Policy

We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page.

We will let You know via email and/or a prominent notice on Our Service, prior to the change becoming effective and update the “Last updated” date at the top of this Privacy Policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

Contact Us

If you have any questions about this Privacy Policy, You can contact us:


The below policies apply to all applications (including websites for the purposes of these policies) that call the Google+ API (called “API Clients” in our Google+ Platform Terms of Service) and specifically address:

  1. General rules
  2. Personal information from the Google+ APIs
  3. What you can’t do in your application
  4. Related policies

A. General Rules

  1. Required privacy policy and other notifications
    1. Expressly provide users with your privacy policy and adhere to it (for both information you get from a Google+ API about the user and from the user directly).
    2. Don’t change your privacy policy without providing reasonable advance notice to your users. If you list your application with us, ensure that the privacy policy link in your application listing is up to date.
    3. Comply with the EU user consent policy.
  2. Information you may not collect, store, or share
    1. Don’t collect, store, or share sensitive personal information such as credit card, bank account, driver’s license, or social security numbers, except as necessary to collect payment.

B. Personal information from the Google+ APIs

This section applies to users’ personal information (including lists of people from users’ circles) your application gets by calling the Google+ API.

  1. Using and sharing data from the API
    1. Don’t use users’ personal information for purposes beyond the limited and express purpose of your application (including as it may reasonably evolve due to ongoing development), or for purposes other than improving their experience in your application, without getting specific opt-in consent from the user.
    2. Don’t sell, rent, make visible, or otherwise provide a user’s personal information to any third party, including other users, without getting specific opt-in consent from the user. Opt-in consent isn’t required to provide users’ personal information to third parties, like infrastructure providers or customer service contractors, whose services are reasonably necessary to help you build or run your applications. You’re responsible for how those third parties handle this information, and you must contractually require them to keep it confidential.
    3. Don’t use stale data. You can cache or store data you’ve obtained through the Google+ API, but to the extent reasonably possible within the context of your application, use fresh data recently fetched from the API. If the fresh data reveals that content is gone (for instance, because a user deleted it), delete it and don’t use your stale copy. For clarity, if you comply with these requirements, you may cache data longer than specified by the cache header.
  2. Deletion rules
    1. Give users a reasonably convenient way to delete any of their personal information you’ve obtained from the API.
      1. Don’t show the user that their data has been deleted without actually deleting the data within a reasonable period of time.
      2. If you created an account for the user associated with their identity on Google+ (including internal accounts not explicitly exposed to the user) you must give the user a reasonably convenient way to delete that association.
      3. If a user deletes their account on your system, deletes the association between that account and their account on Google (“disconnects”), or deletes their Google account, you must delete all personal information you obtained from the Google API relating to them.
    2. As the only exceptions to the above, you may keep the following information:
      1. Information you’re required by applicable law to retain.
      2. Information you’re required to retain by a separate agreement with Google.
      3. Aggregated information that does not include any of the user’s personally identifying information, and would not allow that information to be inferred.
      4. Information (e.g. email address) that you obtained from other Google APIs, as long you comply with their terms.
      5. The user’s Google user ID.

Please also note the Data Portability requirement in our Google+ Platform Terms of Service requiring you to allow users to export data equivalent to what you access via the API.

C. What you can’t do in your application

  1. Application listing and purposeIf you list your application on Google+, we give you the ability to describe your application.
    1. Don’t be dishonest or incomplete about the application’s purpose or type in your description.
    2. Don’t trick users into installing something that’s significantly different from what your description leads them to expect.
    3. Don’t include repetitive text, irrelevant keywords, or misleading formatting in your description.
    4. Don’t list your application more than once or create multiple listings that all point to an application with essentially the same functionality.
  2. User Experience
    1. Don’t mislead your users about what your application does, or trick them into using it.
    2. Not all relationships are created equal—two users can have each other in circles, or a user can simply follow someone. Your application should respect that distinction, and not suggest a reciprocal relationship that doesn’t exist.
    3. Don’t include functionality that proxies, requests, or collects usernames, passwords, or other personal authentication information for Google accounts.
    4. Don’t mimic functionality or warnings on the user’s computer system or on Google.
    5. Don’t induce users to violate Google’s terms of service or other applicable Google policies.
    6. Don’t allow unlawful gambling. You may include simulated gambling, but if you do, you must prevent your users from converting their simulated winnings into something of value outside your application, such as transferable virtual goods, virtual currency, or money.
  3. Posts to the stream and notifications initiated by your application
    1. Don’t mislead your users about what buttons or links included in posts or notifications will do, or trick users into clicking them.
    2. Don’t do any of the following without the user taking an explicit action each time to initiate it:
      1. Post an update to the user’s stream or send a notification (including invite).
      2. Modify the user’s circles in any way.
      3. Share the user’s location information.
    3. Don’t send any posts on behalf of the user without:
      1. Showing an accurate preview of what’s about to be posted and making sure the user is aware of what will cause the share action.
      2. Allowing users to append their own text.
      3. Letting users pick the individuals or circles with whom they want to share.
      4. Indicating that your application is the source of the post or notification.
    4. Don’t circumvent a user’s Google+ privacy settings, including the user’s circles or other permission settings.
    5. Don’t circumvent technical limitations on your use of Google-provided APIs, such as limits on the number or frequency of stream posts. Don’t screen scrape or use any non-documented APIs.
    6. Don’t circumvent any Google+ user interfaces that ensure the user is aware of and agrees to stream posts or the like made on their behalf.
    7. Don’t circumvent any Google+ user interfaces or settings that limit the visibility of information, such as stream posts, from others.
    8. Don’t share with any third party any personal authentication mechanism granted by Google or by any user to you, including your personal certificate or a user’s authorization token.
    9. Don’t override the default sharing option to be “Your circles,” “Extended circles,” or “Public.”
    10. Don’t encourage, facilitate or incentivize repetitive or spammy posts.
    11. Don’t mislead users about requirements to access any functionality in your application.
    12. Don’t require your users to post to the stream or issue a notification (including invites) in order to access application functionality. Posts to the stream and notifications should always be optional.
  4. SecurityWe take security very seriously: we can suspend your application without notice if it appears to have a security or stability issue that could affect Google or its users.
    1. If you experience a security breach or misuse of information, you must notify Google.
    2. If you experience a breach exposing private user information, you must also notify your users.
  5. Additional rules for the Google+ canvasWhere content from your application appears while the user is on the Google+ canvas, a few extra rules apply.
    1. User experience
      1. Provide meaningful functionality. Don’t just provide a link to a webpage, a piece of static content, or a pointer to install an application off of Google+. (It’s OK to provide a link to install a native mobile application that uses the Google+ APIs.)
      2. Don’t generate pop-ups or pop-unders in a new window.
      3. Don’t employ distractions from the primary purpose of the application, like long-running animations, auto-playing video or audio, or strobing/flashing backgrounds.
      4. Don’t use your application to promote or advertise alcohol, tobacco, ammunition and firearms, or other content not suitable for users under the relevant age of majority (whether in an on-canvas application, via stream posts, or other content that appears on Google+).
    2. Monetization policies
      1. Only use Google’s in-app payments for in-app purchases in applications located on the Google+ canvas.
      2. Clearly and honestly describe the products or services that you are selling. Conspicuously post your terms of sale (including any refund and return policies).
      3. Make it clear that you, not Google, are the seller of your products and services.
      4. Don’t require users to pay to obtain basic application functionality without explaining in your application’s description that payment will be required.
      5. Please also note the requirements in our Google+ Platform Additional Terms regarding user data and third-party advertising.
  6. Writing app activity to GoogleIf you write activities to Google via the moments API the following additional rules apply:
    1. You must use reasonable efforts to make users aware of the activities that you write to Google.
    2. Unless you obtain the user’s explicit consent, you must:
      1. Only write activities based on a user’s direct action in your application.
      2. Only write activities at the time of that user action, or as close as technically reasonable.
    3. If your application handles information covered by the Video Privacy Protection Act (“VPPA”) then you must comply with the VPPA. You confirm that any disclosure to Google of information covered by the VPPA will not be incidental to the ordinary course of your business.
  7. Additional rules when Google+ Sign-In is used
    1. When your application displays a login screen to a user, an option for Google+ Sign-In should be presented at least as prominently as other third party login options.
    2. Your application must make it reasonably easy for users to:
      1. Know if they are connected to a Google account, and if so to which account.
      2. Disconnect the application from their Google account(s).
      3. Sign out of your application.

These policies may be revised from time to time without notice. Please check back here for any updates.

Last revised August 7, 2015


EU user consent policy

If your agreement with Google incorporates this policy, or you otherwise use a Google product that incorporates this policy, you must ensure that certain disclosures are given to, and consents obtained from, end users in the European Economic Area along with the UK. If you fail to comply with this policy, we may limit or suspend your use of the Google product and/or terminate your agreement.

Properties under your control

For Google products used on any site, app or other property that is under your control, or that of your affiliate or your client, the following duties apply for end users in the European Economic Area along with the UK.

You must obtain end users’ legally valid consent to:

  • the use of cookies or other local storage where legally required; and
  • the collection, sharing, and use of personal data for personalization of ads.

When seeking consent you must:

  • retain records of consent given by end users; and
  • provide end users with clear instructions for revocation of consent.

You must clearly identify each party that may collect, receive, or use end users’ personal data as a consequence of your use of a Google product. You must also provide end users with prominent and easily accessible information about that party’s use of end users’ personal data.

Properties under a third party’s control

If personal data of end users of a third party property is shared with Google due to your use of, or integration with, a Google product, then you must use commercially reasonable efforts to ensure the operator of the third party property complies with the above duties. A third party property is a site, app or other property that is not under your, your affiliate’s or your client’s control and whose operator is not already using a Google product that incorporates this policy.