WO2024057285A1

WO2024057285A1 - Methods and systems for providing a communication platform for minors

Info

Publication number: WO2024057285A1
Application number: PCT/IB2023/059202
Authority: WO
Inventors: Ana Victoria PUCHI BAUDRY
Original assignee: Mypax Inc.
Priority date: 2022-09-16
Filing date: 2023-09-15
Publication date: 2024-03-21

Abstract

Systems and methods for controlling a minor's use of a messaging platform are disclosed. The methods include connecting a minor account to an approved adult account by a parent account. A list of contacts associated with the parent account is presented on a first user interface of the parent account, and a selection of a contact from the list of contacts to be linked to the minor account as the approved adult account is received where the contact include a user identifier and at least a contact information. The methods also include presenting, on a second user interface associated with the minor account, an approved list of adult accounts a corresponding user identifier without contact information while the contact information in association with the user identifier is stored in a data store.

Description

TITLE: METHODS AND SYSTEMS FOR PROVIDING A COMMUNICATION

PLATFORM FOR MINORS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This claims priority to U.S. Provisional Application No. 63/376,044, filed on September 16, 2022, the disclosure of which is incorporated herein by reference in its entirety

BACKGROUND

[0002] With the growth of the Internet, a user’s ability to communicate with others and obtain information has never been greater. However, in many cases, this capability must be limited for the protection of the user or for other reasons. For example, it may be desirable to restrict and/or record a user’s activity to allow a parent to control a child’s contact with the outside world, such as to avoid exposing the child to inappropriate content, to prevent on-line predators from contacting the child, and to otherwise control the child’s use for disciplinary reasons. Specifically, although Internet based communication applications like instant messaging can be a great vehicle for children to establish and maintain friendships, it also puts children at risk for exposure to bad influences and even electronic predators. Because the communication is electronic in nature, it is easy for people to pretend to be who they are not, and very hard for parents to keep track of with whom their children are communicating. Other communications mechanisms such as voice and video chat present similar issues.

[0003] A key aspect of online parental control systems is the ability for parents to control with whom a child communicates online. Such systems enable parents to require that children receive permission to add friends to the list of parties with whom they can communicate. Unfortunately, even with such systems, the only mechanism parents have for actually determining the true identities of their child’s online buddies is to ask their child. The response of children is not reliable in this context, as children can be dishonest or themselves the victims of other’s dishonesty. Without being able to determine with whom their children are really requesting permission to communicate, the power to approve or deny the requests is not sufficient. Therefore, there exists a need in the art for parental control of electronic messaging contacts of a child. This should be balanced with providing a system that respects the child’s privacy and that is not overly restrictive.

[0004] This document describes methods and systems that are designed to address at least some of the issues discussed above.

SUMMARY

[0005] In various scenarios, systems and methods for controlling a minor’s use of a messaging platform. The methods are executed by a system including a processor and a non- transitory computer readable medium containing programming instructions (that cause the processor to execute the methods).

[0006] The methods may include, include connecting a minor account to an approved adult account by a parent account. A list of contacts associated with the parent account may be presented on a first user interface of the parent account, and a selection of a contact from the list of contacts to be linked to the minor account as the approved adult account may be received where the contact include a user identifier and at least a contact information. The methods may also include presenting, on a second user interface associated with the minor account, an approved list of adult accounts a corresponding user identifier without contact information while the contact information in association with the user identifier is stored in a data store. The parent account may previously be linked in a supervisory capacity to the minor account. The parent account, the minor account, and the approved adult account are configured to use the messaging platform in accordance with one or more permission rules of the messaging platform.

[0007] In one or more implementations, the methods may also include receiving a selection of the user identifier for transmission of a communication to the approved adult account via the second user interface, retrieving the contact information for the approved adult account from the data store, and transmitting the communication to the approved adult account without presenting the contact information on the second user interface.

[0008] In one or more implementations, the methods may also include presenting an identifier of a minor associated with the minor account without contact information of the minor on a third user interface associated with the approved adult account, and receiving, from the approved adult account, a second communication for transmission to the minor. The methods may include transmitting the second communication to the minor account without presenting the contact information of the minor account on the third user interface.

[0009] In various implementations, the methods can also include identifying and deleting any contact information included within a communication sent to the minor account or from the minor account. Optionally, an alert may be sent to the parent account upon identification of that contact information.

[0010] In various implementations, the methods can also include presenting on the first interface the approved list of contacts as being associated with the minor account, and allowing the parent account to permit or block one or more features associated with each of the contacts in the approved list of contacts.

[0011] In one or more implementation, the methods also may include sending an alert to the parent account upon identification of an unapproved adult contact within a messaging group that includes the minor account. [0012] Optionally, the parent account may be linked in a supervisory capacity to the minor account by verifying a relationship between the between an adult associated with the parent account and a minor associated with the minor account.

[0013] In one or more implementation, the methods also may include monitoring communications between the approved adult account and the minor account, and sending notifications to the parent account upon detection of a flagged activity. Optionally, the flagged activity may include detection of disallowed words, images, or contexts within the communications. Additionally and/or alternatively, a report comprising information relating to the flagged activity may be presented on the first user interface. The report can include at least a threshold number of communications transmitted before or after the flagged activity to or from the minor account.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG. 1 illustrates an example communication system.

[0015] FIG. 2 illustrates an example messaging platform that can be utilized with the communication system of FIG. 1.

[0016] FIG. 3 illustrates a flowchart of an example process for managing communications with minors.

[0017] FIGs. 4A-4D illustrate example user interfaces for implementing one or more steps of the method in FIG. 3.

[0018] FIG. 5 is an example computer system useful for implementing various embodiments.

[0019] In the drawings, like reference numbers generally indicate identical or similar elements. DETAIUED DESCRIPTION

[0005] As used in this document, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. Unless defined otherwise, all technical and scientific terms used in this document have the same meanings as commonly understood by one of ordinary skill in the art. As used in this document, the term “comprising” means “including, but not limited to.”

[0006] As used herein, a “parent” is any person who is in a supervisory relationship as a supervisor to a user being supervised such as, without limitation, a parent, a guardian, an elder sibling, a coach, a teacher, or the like. A “minor” as used herein is any person being supervised such as a child who is younger than the legal age of majority. An “approved adult” as used herein refers to a person who has been granted permission by a parent to communicate with a minor associated with the parent, via the messaging platform of the current disclosure. As will be understood from the discussion below, such approval facilitates communications between the approved adult and the minor without actual exchange of any contact information between the approved adult and the minor.

[0007] Utilizing the techniques disclosed herein, a parent can monitor and/or control communications between adults and minors (e.g., children), while not unnecessarily restricting communications between minors. The system can be configured either to prohibit the storing and exchange of any contact information for a minor outside of the messaging platform (e.g., email address, phone number), or to the extent such information is stored to conceal it from adults approved to contact the minor. Under either configuration, the messaging platform provides a secure and transparent way to facilitate communication between approved adults and minors preventing the approved adult and minor from obtaining each other’s direct contact information (such as a phone number, social media handle, or the like). Optionally, the system also provides the parent means to monitor communication between approved adults and minors.

[0008] The system can be configured to provide these features for email messaging, text type messaging (e.g., SMS), in-app messaging, push notifications, multimedia messaging, instant messaging, rich communication services, for phone calls, or for any other type of mobile communication. The system can be configured to preclude an adult (who is not a parent) from being able to directly contact a minor outside of the messaging platform, or vice versa. Moreover, by preventing exchange of contact information using the messaging platform, the parent cannot be cut out of the communications initiation and/or the monitoring loop to minimize or otherwise reduce the opportunity for inappropriate communication between an adult and a minor.

[0009] FIG. 1 illustrates an example communication system 100 for managing communications between users through their respective user accounts. The system 100 includes a server 102 that acts as a host and facilitates communications between a plurality of client computing devices 104 used by, for example, approved adults, parents, and minors. In one example, the server 102 is a single computing device. Alternatively, the server 102 can be more than one computing or electronic devices jointly configured to process software instructions serially or in parallel.

[0010] In some examples, the server 102 is in communication with one or more networks such as a network 106 comprised of one or more computing devices. The network 106 may be a private local area network (LAN), a private wide area network (WAN), the Internet, a mesh network, a cloud computing network, or any other network as is known in the art.

[0011] The server 102 and the one or more client devices 104 typically include one or more of a computer processor, memory, a network device (e.g., wireless transceiver), and input and/or output devices and/or interfaces according to some examples (discussed below in more detail with respect to FIG. 5).

[0012] In one example, each of the client devices 104 is a mobile device capable of accessing and locally running client software that provides access to a messaging interface 117 and a messaging platform 120. The messaging interface 117 is operable to transmit messages between the approved adults, parents, and minors, via the messaging platform 120. The messages can take the form of a chat, instant messaging, a non-chat inbox (e.g., similar to an email inbox, but within the communication system 100), multimedia messages, voice calls, and/or video calls, for example, as discussed in detail below. In examples, one or more of the client devices 104 is configured to execute an iPhone Operating System (iOS) or Android OS front end client, for example, and a backend linked to the network 106 or a cloud computing environment, for example.

[0013] The server 102 and each of the client devices 104 include respective network interfaces that facilitate communication with the other systems and/or components of the network 106 utilizing various communications protocols such as Transmission Control Protocol/Intemet Protocol (TCP/IP), User Datagram Protocol (UDP), hyper-text transfer protocol (HTTP), simple mail transfer protocol (SMTP), file transfer protocol (FTP) and the like. In some examples, the one or more client devices 104 are configured to communicate with the server 102 directly via a direct client interface 112 or over the network 106. In alternative examples, the one or more client devices 104 are configured to communicate with each other directly via a peer-to-peer interface 114.

[0014] One or more of the client devices 104 can be coupled to one or more media devices 105 such as a digital camera operable to capture digital images and/or audio streams. Example media devices 105 include an onboard camera integrated with a mobile device, or a

Bluetooth or wireless device. [0015] The system 100 additionally includes one or more data stores 108, which in some examples are operable to store and provide access to a repository of data such as email, text, images and other data and communications to other computing devices. In examples, the data store 108 is a storage area network device (SAN) configured to communicate with the server 102 and/or the one or more client devices 104 directly or over the network 106. In other examples, the data store 108 is located within the server 102 or within at least one of the client devices 104. The data store 108 may be configured to store one or more of computer software instructions, data, emails, text messages, images or other media files, database files, and configuration information, for example. In alternative examples, the server 102 and/or the one or more client devices 104 are configured to communicate media and other data in a cloud computing environment or to one or more third-party data locations via one or more web services. Each data store 108 can provide at least one database 116 for storing communications and other data and information.

[0016] In examples, the system 100 is a client-server architecture configured to execute computer software on the server 102, including any of the messaging functionality, archival functionality, account registration and verification functionality, analytical functionality, monitoring and reporting functionality, or the like, discussed herein, which is accessible by the one or more client devices 104 using either a thin client application or a web browser executing on the one or more client devices 104. In some examples, the server 102 loads the computer software instructions from local storage, or the data store 108 into memory and executes the computer software using the one or more computer processors. Thus, the client of the client devices 104 can be a dedicated app, or a general web browser, for example.

[0017] Referring to FIG. 2, with continuing reference to FIG. 1, a messaging platform 120 which provides a communications package for facilitating communications between users via their user accounts is shown. The platform 120 can be implemented as one or more software applications executed by the server 102 and/or client devices 104, for example, and is operable to require a parent to add, via a parent device, approved adult(s) to a contact list of a minor (whose account is linked to that of the parent) before the minor and the approved adult(s) can communicate with each other. In this manner, no contact information is exchanged between the minor and the approved adult while still allowing them to communicate with each other. In some embodiments, the parent may not have access to the payload of the messages exchanged between the minor and the approved adult. In such embodiments, the system can be configured for providing context (or other information relating to the exchanged messages such as title, type of payload, time, etc.) in a report or summary as discussed below. The platform 120 may, optionally, automatically include parents (e.g., parents) in at least some of the electronic communications in the system 100 between minors and approved adults and/or between minors (by, for example, allowing parents access to the payload of the messages being exchanged). In some other embodiments, the platform 120 may provide certain electronic communication monitoring capabilities to the parents, as discussed below.

[0018] The messaging platform 120 includes a messaging interface 117 that utilizes a gateway module 118 and a data module 115. The gateway module 118 is operable to interface with a plurality of user groups 110A-C, including an approved adult group 110A for approved adults 126, a parent group HOB for parents 128, and a minor group 110C for minors 130. The data module 115 is operable to interface with one or more databases 116 which can store or be linked to one or more user accounts 122 (e.g., store account data, profde information, etc. relating to account holders such as parents, approved adults, and minors), access lists 123, analytics logs and/or data 124, and communications or data fdes 125. The fdes 125 can include any of the data and information disclosed herein. Each of the approved adults 126, parents 128 and minors 130 are associated with respective accounts 122 and one or more access lists 123. The account data includes identifying information about the user, such as the user’s name, address, user identification (ID), and password. In one aspect, the data includes profile data, including information regarding the user’s demographic characteristics, such as the user’s age, interests, gender, educational history, etc. The data further includes the various connections of the user (e.g., minor, parents, approved adults, etc.). The access lists 123 are lists of rules that specifies whether the corresponding user can be granted or denied access to a particular object, user, or system resource, and may act as filters, managing which traffic can access the network from the messaging platform 120.

[0019] The gateway module 118 serves as an intermediary between the approved adults 126 and minors 130 and is operable to automatically review and monitor (and/or store/transmit for reviewing and monitoring) at least some (or all) of the communications between approved adults 126 and minors 130, as discussed below, whether the communication was initiated by the approved adult 126 or minor 130. Messages transmitted by one of the approved adult account to the linked minor (or vice versa) and/or the minor account are reviewed without requiring parent approval of the particular message (and, optionally, transmitted to the intended recipient only if such transmission is allowed; and/or analyzed for reporting or flagging to the parent). Thus, message-by-message approval is not required from the guardian or the parent. However, parent approval is needed to link the accounts of an approved adult 126 and minor 130. The gateway module 118 is operable to serve as a proxy that hides or abstracts external contact information of the minor 130 from corresponding approved adult 126 such that the approved adult 126 is prevented from contacting the minor outside of the messaging platform 120 (e.g., email address, telephone number, and physical and mailing addresses). Optionally, external contact information of the parent 128 can also be hidden from the approved adult 126. In one example, the messaging platform 120 does not store any external contact information for the minor 130. In such an example, if the system or system administrator needs to contact the minor 130 (e.g., because the minor requested a password reset), password reset instructions could be sent to an email address of the minor’s corresponding parent 128.

[0020] A minor 130 and approved adult 126 can only exchange messages if each of their respective accounts is linked to each other and to an account of the parent 128 of the minor 130, and such linking can only happen with approval of the parent 128. This prevents the approved adult 126 and minor 130 from contacting each other in the messaging platform 120 without parent approval, and further prevents the approved adult 126 and minor 130 from bypassing the messaging platform to transmit messages to each other, because they cannot obtain each other’s external contact information via the messaging platform 120 (even after linking).

[0021] On the other hand, minor account holders may be linked and allowed to exchange messages with each other (i.e., other minor users of the platform) without approval from the corresponding parent(s). This feature may serve as an incentive for minors to not create a fake account as an adult (i.e., pretending to be an adult) because the imposter adult account cannot connect with other minor contacts without parental approval. Optionally, the exchange of messages between minors may have restrictions without approval from the corresponding parent(s). For example, restrictions may be imposed on the type of messages (e.g., text only, voice only, etc.), the maximum number of messages, the timing of messages (e.g., no messages allowed during certain times), the length of messages, or the like until approval is received from the corresponding parent(s). This feature may also deter an adult from creating an account as a minor to connect with other minors.

[0022] The gateway module 118 may also be operable to coordinate the transfer of messages within the messaging platform 120 which could include messages in a chat interface (e.g., a group with all minor group members) and/or non-chat messages in an email format within the messaging platform 120. These are two-way communications which can be responded to by their recipients (e.g., the minors).

[0023] In one example, the gateway module 118 also permits voice and/or video calls between an approved adult 126 and minor 130 if the parent 128 has previously linked the minor 130 and approved adult 126. In some other examples, the system 100 is configured to only permit telephone calls between approved adults 126 and parents 128.

[0024] In certain embodiments, the messaging platform 120 may also include or interface with an analyzer module 119 that performs various analytics on the communications (e.g., message payload), communications related information (e.g., header, network, etc.) and/or data collected by the messaging platform 120 (discussed below in more detail). The communications related information may include, without limitation, information relating to actions taken by a user such as adding a connection to another user, sending a message to another user, uploading an image, reading a message from another user, viewing content associated with another user, attending an event posted by another user, among others. The data collected may include various types of data describing actions. Examples of stored data describing actions include the date and/or time when an action was performed, a user account identifier of the user performing the action, a type associated with the action, an object on which the action was performed or other data. The analyzer module may use any now or hereafter know methods for performing the analyses such as text parsing for detecting certain words (e.g., bullying words, offensive words, sexual content, etc.), image analysis to identify certain objects, video analysis, audio analysis or the like using, for example, machine learning, natural language processing, text parsing and annotations, pattern recognition, text mining, comparison to a predefined data structure, or the like. In some embodiments, the analyzer module 119 may be configured to extract context and/or other information about a communication from the analytics and perform an action accordingly. Optionally, the analyzer module 119 may be configured to perform the analytics on the communications, communications related information and/or data collected when the communication is in any one of a plurality of languages (e.g., English, French, German, etc.).

[0025] The results of the performed analytics may be provided to the parents 128 and/or may be used as a trigger to automatically perform an action (e.g., block further communications between a minor 130 and an approved adult 126 or between minors 130, until allowed to do so by the parent 128; filter or redact certain communications; send a copy of communication to a parent; or the like). In various examples, the parent 128 can select an option of receiving analytical reports as they occur (e.g., in real time) and/or as a digest (e.g., on a daily or weekly basis).

[0026] The messaging platform 120 may also include or interface with an account registration module 121. The account registration module 121 receives requests to create accounts from users using or establishing an account to use a service associated with the messaging platform 120. If the user is associated with an age that does not exceed a threshold age (a “minor”), another user that is a verified parent of the minor user (i.e., parent) provides administrative settings regulating the minor’s access to the platform 120. For example, the platform may restrict and/or monitor actions of a minor user based on administrative settings provided by the parent. For example, the system may automatically send notifications regarding a minor’s actions to a user account associated with a parent of the minor. As described above, an entity requesting an account may have an age that does not equal or exceed a threshold age (i.e., a minor). In one embodiment, the account registration module 121 determines whether a request for an account is received from a minor and requests identifying information for an additional user that is a parent of the minor. For example, if data included in a request for an account (e.g., an age, a birth date, etc.) indicating the user’s age indicates that the user’s age does not equal or exceed a threshold value, the account registration module requests that the user identify an additional user having a parental relationship with the requesting user. The account registration module 121 then verifies that the additional user has a parental relationship with a minor user requesting an account. If an additional user verified as having a parental relationship with a minor user provides authorization to the account registration module 121, an account for the minor is created and/or certain capabilities of an already created minor’s account are unlocked. Verification of a parental relationship between users is further described below in conjunction with FIG. 3.

[0027] The account registration module 121 may verify user accounts (i.e., parent) alleged to have a parental relationship with another user (e.g., a minor). For example, the account registration module 121 may determine whether a user alleged to have a parental relationship with a minor (a “purported parent”) has an account with the messaging platform 120, whether the purported parent is an adult and whether the purported parent is connected to the minor user. In other embodiments, the account registration module 121 performs any suitable actions for verifying a parental relationship between a purported parent and a minor user.

[0028] The account registration module 121 verifies that a purported parent has a valid account. For example, the account registration module 121 compares information identifying a purported parent with stored user accounts to verify that information identifying the purported parent corresponds to information in at least one stored user account. Additionally, the account registration module 121 analyzes a stored user account corresponding to the information identifying a purported parent to verify that the stored user account is authentic. For example, the account registration module 121 retrieves actions, locations, demographic data, facial recognition algorithms (e.g., to determine age authenticity, relationship between people, etc.) or other information associated with a user account to determine that the user account is authentic. Optionally, if the purported parent does not already have an account, the account registration module invites the purported parent to create an account and provide registration information that may be used to verify the parental relationship.

[0029] If a user account corresponding to a purported parent is verified (or created), the account registration module 121 determines an age from data in the user account. For example, the adult account registration module 121 compares the age from the user account associated with an adult age threshold and determines that the user account is associated with an adult if the age equals or exceeds the adult age threshold. The account registration module 121 may use any suitable data to determine the age associated with a user account. For example, the account registration module 121 uses an age declared in the user account, a birth date specified by the user account and the current date, the average age of other user accounts connected to the user account or other suitable data associated with the user account. In one embodiment, the account registration module 121 determines an age associated with a user account using different types of data to improve the accuracy of the age determination. The account registration module 121 determines whether the purported parent user is the parent of a minor user. In some instances, the relationship account registration module 121 leverages various social signals (e.g., information derived from connections, user profiles, user actions) to verify a parental relationship. In one embodiment, the account registration module 121 determines whether another user account of the minor is connected to the user account associated with the purported parent and, if the accounts are connected, determines whether the connection has a type associated with a parental relationship. Additional data associated with the user accounts of the minor user and of the purported parent may be used to verify the parental relationship. For example, location data associated with the minor user and purported parent user accounts is analyzed, or pictures having the minor and the purported parent tagged are analyzed to further determine the relationship between the minor user and the purported parent. In one embodiment, after verifying a parent-child relationship, the account registration module 121 automatically establishes a connection between the user account of the minor and the user account of the purported parent having a specified type indicating a parental relationship.

[0030] Referring back to FIG. 2, the user account module 122 stores account data associated with a user’s account. The account data includes identifying information about the user, such as the user’s name, address, user identification (ID), and password. The user account module 122 stores account data for a plurality of users accounts. In one aspect, the data includes social data, including information regarding the user’s demographic characteristics, such as the user’s age, interests, gender, location, educational history, etc. The data may also include regulation data set by a parent for connected minor accounts such as approved adult lists, blocked adult lists (adults that cannot connect with a minor account), approved minor lists, blocked minor lists, monitoring configurations (e.g., what types of communications, data, etc. should be monitored), reporting configurations (e.g, frequency of reporting, format of reporting, etc.), or the like. The data further includes the various connections of the user to other users of the messaging platform. The connections may be added explicitly by the user. For example, the user may select a particular other user to be a connected minor. The connections also may be automatically created by the system based on common characteristics of the users (e.g., users who are siblings may be connected to the same parent).

[0031] FIG. 3 illustrates a flow chart of an example method for managing communications with minors in accordance with this disclosure. The method may be applied without limitation to the above described messaging platform, where the steps and features in the flowchart are provided by the server 102 in cooperation with the client devices 104.

[0032] At 302, the system receives a request for registration from a user for using the messaging platform and determines whether the request is from a minor or an adult. For example, based on data (e.g., a provided age, a provided birth date, facial recognition, etc.) included in the request, the system determines an age associated with the requesting user and determines whether the age is less than a threshold age. If the age of the requesting entity does not equal or exceed the threshold age, the system determines that the requesting user is a child, the system may create a “restricted minor account” (304). To establish a minor account, a minor profde is created. Account information, such as a user name, password, may be stored in a secure database. A minor profde allows a minor to provide information that allows the system to interact with the minor. Optionally, the system may not create a minor account until approval from a verified parent is received.

[0033] A “restricted minor account” is an account that allows the minor account holder to use only certain functionalities or services offered by the messaging platform. For example, a restricted minor account may include restrictions such as, without limitation, ability to communicate with (i.e., send and/or receive communications) from minor users only, ability to send and/or receive text messages only (i.e., image and video sharing is disabled), restrictions on using video and/or phone calling, time-based communication restrictions (e.g., no communications during certain hours), content-based communication restrictions, or the like. It should be noted that restricted minor accounts are not allowed to send and/or receive communications from any adult accounts.

[0034] The system may also request, from the minor, information identifying a parent (e.g., a parent or a guardian) (306) where the parent may have the ability to approve modification of the minor’s restricted account to a non-restricted account. The system may then receive (308) information identifying a parent, which is the purported parent of the minor. Examples of information identifying a parent include: a name, an address, contact information (telephone number, email address), user identification (ID) information, account identifier, screen name or other suitable information.

[0035] The system may use the received information to determine whether the purported parent already has an account (310), and if the purported parent already has an account (310: YES), the system verifies that the identified parent user is the parent of the child (312) using, for example, one or more of the methods discussed above and/or any now or hereafter known technologies.

[0036] If the purported parent is determined not to already have an account (310: NO), the system requests the purported parent to create an account (314). The system may establish a parental account (316) upon receipt of required information from the purported parent (in response to an account creation request from the system in 312 and/or upon determination by the system that the requesting user is an adult in step 302). The system may guide the parent through the set up of a parent account. To establish a parent account, a parent profile is created. A parent profile allows a parent to provide information that allows the system to interact with a parent. For example, the system may request additional information as well (in addition to information provided by the requesting minor user), such as a verification or proof of age, a verification or proof of relationship with the requesting minor, other connections, password, name (first, middle and last), address information, verification preference such as e-mail or short message service (SMS) that is used to verify a parental account, primary phone number, mobile phone number that may be used if SMS is selected as a verification preference so that SMS messages may be sent to a mobile phone, a primary e-mail address that may be used if e- mail is selected as verification preference, secondary e-mail, password reminder questions, or the like. Optionally, creation of the parent account may require the parent to provide a verification code (e.g., an alphanumeric code) sent by the system to a communication platform different from the messaging platform of the system (e.g., a secondary email address, phone number, etc.).

[0037] After a parental account is established, the system may allow the user of the parent account to establish one or more minor accounts and/or connect with already existing minor accounts (318) upon verification of a parent child relationship. For example, the system may specify additional information and/or additional steps for the purported parent user to establish or connect to minor user’ s account. For example, an authorization request may specify that the purported parent user provide a portion of an identification number associated with the purported parent user (e.g., last four digits of a social security number, last four digits of a credit card number, etc.) to establish or connect to minor user’s account. A third-party verification company may use the identification number to confirm that the request was received from the purported parent user. As another example, the system may require that the request be received from a confirmed email address or as an SMS message from a mobile phone. The information and/or steps identified by the authorization request may be based on the specific country and/or jurisdiction of the purported parent user and/or minor user. In one embodiment, the minor user is also automatically added to a close friends or children list of the parent user.

[0038] If a parent creates a minor account, a verification code (e.g., an alphanumeric code) may be sent to an email or phone number (or other account) of the minor notifying the minor of account creation and providing them instructions to use the code for accessing the minor account for the first time. The minor account holder may then change or create the login credentials such as username and password.

[0039] The settings of a linked minor account may then be controlled by the parental account. For example, the parent user may approve modification of the minor user’s restricted account to a non-restricted account. Additionally and/or optionally, the system may present a number of options from which a parent may choose such that various customized controls may be imposed on a minor’s non-restricted account. For example, the parent may impose limits on the number of contacts, the number of communications, forms of communications (e.g., text only), content of communications (e.g., no videos), timing of communications, etc. The example user interface 410 in FIG. 4 A illustrates an interface displayed on a parent device that includes a list of actions 401 (allow/disallow sharing of images with some or all contacts), 402 (allow/disallow sharing of videos with some or all contacts), 403 (allow/disallow sharing of copy/pasting of communications), 404 (add or delete approved adults from the minor’s contact list), and 405 (configure notifications and reports) that a parent user may undertake with respect to a linked minor account 406 using one or more interactive user action buttons.

[0040] The parent account is secure and can only be accessed with the correct username and password. All data transmissions may be encrypted and secure, such as all profile information. Passwords that may be used by the parent, child or others designated to properly use the system may have expiration dates to insure password strength.

[0041] In addition, the system may allow the parent, via the parent account, to add approved adults to the linked minor account’s contact list. The approved adults may then communicate with the minor account user. Specifically, the parent may add the approved adult by selecting an adult that already exists in the contact list of the parent’s device (i.e., contact information of the adults first must be added to the contact list of the parent) for addition to the “approved contact list” of the minor account. Upon selection, the system operates to transparently add the approved adult to the “approved contact list” of the minor account of the messaging platform, without exchange of any contact information between the minor and the approved adult. The approved adult identifier (e.g., name) then appears in the approved contact list of the minor account, while the contact information itself may be hidden from the minor. The contact information, however, may be stored in a data store and linked to the approved adult identifier such that when a minor selects the approved adult identification for sending a communication, the messaging platform can correctly route the communication to the approved adult without the minor ever seeing the contact information (or vice versa for the approved adult). [0042] A notification may also be sent to the approved adult notifying them that they may communicate with the minor, via the messaging platform. Specifically, while the minor and the approved adult can communicate with each other once the approved adult is added to the “approved contact list”, the minor’s contact information is not provided to the approved adult (and/or vice versa). As such, the system is operable to require a parent to add approved adult(s) to a contact list of a minor (whose account is linked to that of the parent) before the minor and the approved adult(s) can communicate with each other. In this manner, no contact information is exchanged between the minor and the approved adult while allowing them to communicate with each other.

[0043] Optionally, the system may be operable to detect and block (e.g., by redaction, not sending the message, etc.) transmission of contact information of the minor (e.g., phone number, email address, social media account information, etc.) via the messaging platform.

[0044] If the approved adults to be added is not already in the contact list of the parent account, the parent must first add the approved adults (e.g., name, contact information, account information, etc.) the parent account contact list. The approved adult must also establish an account with the messaging platform to be able to communicate with the minor account holder. As such, if the approved adult who is selected by the parent for addition to the approved contact list of a minor does not have an account with the messaging platform, they may be invited to create an account and added to the approved contact list only upon creation of the account.

[0045] FIGs. 4A - 4D illustrate a user interface (e.g., a graphical user interface) displayed on a display screen of a device, where the device is used by a user of a parent account illustrating the steps for adding approved adults to the approved contact list of a linked minor account. For example, the parent may click on the “adult lists” icon 404 on user interface 410 on the parent’s mobile device to start adding approved adults to the minor M’s account. Such a selection will cause the system to display the parent’s contact list on as user interface 420 (FIG. 4B). The parent is able to select any of the user identifiers listed in the contact list displayed on user interface 420 (on the parent’s mobile device). This selection causes the selected individuals to be added as approved adults to be added to the “approved contact list” displayed as user interface 430 on the minor’s mobile device automatically (FIG. 4C) if the approved adult has an account with the messaging platform. FIG. 4D illustrates an optional example user interface 440 on a minor’s mobile device showing a contact list 441 including the approved adults (who have an account with the messaging platform) and minors, and a list of approved adults 442 who do not have an account with the messaging platform. The minor user may invite such approved adults to create an account with the messaging platform to be able to start communicating with the minor user.

[0046] The parent account holder may optionally be able to, via the parent device, view the contact list of the linked minor account holder including the approved adults and any minors, remove and/or block one or more contacts, communicate directly with the contacts, or the like.

[0047] At step 320, the system may allow a parent to setup specific notifications. For example, a parent may request a notification if more than a threshold amount of time is spent using the platform and/or communicating with a particular user, if offensive language use is detected (including specifying words to be flagged), bullying behavior is detected, inappropriate images or videos are detected, attempts are made to communicate (i.e., send and/or receive) communications from an unapproved adult and/or minor, attempts are made to communicate (i.e., send and/or receive) communications from an adult and/or minor who has never personally met the account holder minor, images or videos are shared, or the like. Such notifications may include any information regarding the minor account. Optionally, the notification may include a request to approve certain actions by the minor account holder (e.g., request to approve exchange of images). Notifications may be sent by e-mail, SMS, voicemail, or the like. In the above examples, a reply SMS message or e-mail may be sent by a parent to approve a particular request. Alternatively, the parent match system may provide one or more links that may be clicked upon to approve or decline a particular request. If a notification is provided by phone, a request for approval may be requested after the recital of an automated message, and approval may be solicited through key selection.

[0048] Additionally or alternatively, the system may maintain an activity/data log, and may generate activity reports for a parent’s review. Such reports may be viewed by logging into the parent match system or may be sent on a periodic basis to a parent by e-mail or other communication methods. Alternatively, the system may generate customized reports based upon a parent’s request. For example, a parent may request a report for certain incident detections such as incidents based on language analysis (e.g., for flagging curse words, bullying language, hate language, sexual language, drug related language, cyber predator language, psychological language indicative of depression, anxiety, addiction, etc., words indicative of never having met the minor account holder, or the like), image analysis for unsafe content, video analysis, number of messages exchanged with each contact etc. In various embodiments, a library of text such as words, phrases, and/or short hands may be created (automatically using, for example, artificial intelligence or machine learning and/or by a user) that is indicative of one or more of the above incidents and associated with the incident type. For example, the following phrases may be associated with the minor account holder not having personally met the person they are communicating with and/or cyber-predator incidents: “let’s meet in real life” or LMIRL; “age, sex, location” or ASL; “how old are you,” “how old,” “don’t be shy,” etc. The library may include words, short hands, and/or phrases in one or more languages (e.g., English, French, German, etc.). Additionally and/or alternatively, the system may analyze the communications for context and/or phonetics for detection of the above incidents. For example, the system may identify the language being used (e.g., based on location, words being used, etc.) and automatically analyze the text in association with the appropriate language context or phonetics. Optionally, one or more of such phrases/words/short hands/context may also be associated with a score, and an overall score may be generated as being indicative of the likelihood of an incident detection.

[0049] Optionally, all images and/or videos may be archived and/or shared with the parent account holder for review. The report may include, for detected incidents, date of detection, times, number of incidents, contact name(s) associated with the incident, or the like. In yet another example, and the report may also include a snapshot of a certain number of messages (e.g., 1, 2, 3, etc.) exchanged before and/or after the incident to provide context to the parent without disclosing the entire communication (thus preserving the minor’s privacy). In various embodiments, the parent may also select the option to automatically block transmission/receipt of, redact, or otherwise blur images, text, and/or videos relating to the above identified incident detections.

[0050] In some embodiments, the messaging platform of the current disclosure may also provide group messaging functionalities between more than two users. Such users may include one or more minors and one or more approved adults (the approved adults being linked to at least one of the minors in the group chat). In such scenarios, parents of the minors that are not linked to the approved adult within the messaging group will be notified that their respective minors are in a messaging group that includes an adult not already linked to the minor. The parent(s) may then either link the adult to the minor, block the minor from accessing the messaging group, and/or otherwise restrict access to the adult within the messaging group (e.g., redact messages, etc.). Optionally, minors may not be allowed to join any messaging groups that have adults not approved to communicate with the minor until the parent either links the adult with the minor or otherwise allows the minor to join the messaging group. Additionally and/or alternatively, an adult may not be allowed to join a messaging group until that adult has been linked to all the minors within the messaging group as an approved adult.

[0051] It should be noted that the above features described for parent and minor users can be provided for other types of supervisor users and supervised users in other implementations.

[0052] The server and the client devices may be using one or more computer systems, such as computer system 500 shown in FIG. 5. Computer system 500 can be any computer capable of performing the functions described in this document.

[0053] Computer system 500 includes one or more processors (also called central processing units, or CPUs), such as a processor 504. Processor 504 is connected to a communication infrastructure or bus 502. Optionally, one or more of the processors 504 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor that is a specialized electronic circuit designed to process mathematically intensive applications. The GPU may have a parallel structure that is efficient for parallel processing of large blocks of data, such as mathematically intensive data common to computer graphics applications, images, videos, etc.

[0054] Computer system 500 also includes user input/output device(s) 516, such as monitors, keyboards, pointing devices, etc., that communicate with communication infrastructure 502 through user input/output interface (s) 508.

[0055] Computer system 500 also includes a main or primary memory 506, such as random access memory (RAM). Main memory 506 may include one or more levels of cache. Main memory 606 has stored therein control logic (i.e., computer software) and/or data.

[0056] Computer system 500 may also include one or more secondary storage devices or memory 510. In some embodiments of this disclosure, main memory 506 may be considered the first memory and secondary memory 510 may be considered the second memory, or vice versa. Alternatively, secondary memory 506 may include multiple subcomponents that together serve as the first memory and the second memory. Secondary memory 510 may include, for example, a hard disk drive 512 and/or a removable storage device or drive 514. Removable storage drive 514 may be an external hard drive, a universal serial bus (USB) drive, a memory card such as a compact flash card or secure digital memory, a floppy disk drive, a magnetic tape drive, a compact disc drive, an optical storage device, a tape backup device, and/or any other storage device/drive.

[0057] Removable storage drive 514 may interact with a removable storage unit 518. Removable storage unit 518 includes a computer usable or readable storage device having stored thereon computer software (control logic) and/or data. Removable storage unit 518 may be an external hard drive, a universal serial bus (USB) drive, a memory card such as a compact flash card or secure digital memory, a floppy disk, a magnetic tape, a compact disc, a DVD, an optical storage disk, and/ any other computer data storage device. Removable storage drive 514 reads from and/or writes to removable storage unit 518 in any suitable known manner.

[0058] According to an example embodiment, secondary memory 510 may include other means, instrumentalities or other approaches for allowing computer programs and/or other instructions and/or data to be accessed by computer system 500. Such means, instrumentalities or other approaches may include, for example, a removable storage unit 522 and an interface 520. Examples of the removable storage unit 522 and the interface 520 may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and/or any other removable storage unit and associated interface.

[0059] Computer system 500 may further include a communication or network interface 524. Communication interface 524 enables computer system 500 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference number 528). For example, communication interface 524 may allow computer system 500 to communicate with remote devices 528 over communications path 526, which may be wired and/or wireless, and which may include any combination of LANs, WANs, the Internet, etc. Control logic and/or data may be transmitted to and from computer system 500 via communication path 526.

[0060] In some embodiments, a tangible, non-transitory apparatus or article of manufacture comprising a tangible, non-transitory computer useable or readable medium having control logic (software) stored thereon is also referred to in this document as a computer program product or program storage device. This includes, but is not limited to, computer system 500, main memory 506, secondary memory 510, and removable storage units 518 and 522, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 500), causes such data processing devices to operate as described in this document.

[0061] Based on the teachings contained in this disclosure, it will be apparent to persons skilled in the relevant art(s) how to make and use embodiments of this disclosure using data processing devices, computer systems and/or computer architectures other than that shown in FIG. 12. In particular, embodiments can operate with software, hardware, and/or operating system implementations other than those described in this document.

[0062] Terms that are relevant to this disclosure include:

[0063] An “electronic device” or a “computing device” refers to a device that includes a processor and memory. Each device may have its own processor and/or memory, or the processor and/or memory may be shared with other devices as in a virtual machine or container arrangement. The memory may contain or receive programming instructions that, when executed by the processor, cause the electronic device to perform one or more operations according to the programming instructions. Examples of electronic devices include personal computers, servers, mainframes, virtual machines, containers, gaming systems, televisions, and mobile electronic devices such as smartphones, personal digital assistants, cameras, tablet computers, laptop computers, media players and the like. In a client-server arrangement, the client device and the server are each electronic devices, in which the server contains instructions and/or data that the client device accesses via one or more communications links in one or more communications networks. In a virtual machine arrangement, a server may be an electronic device, and each virtual machine or container may also be considered to be an electronic device. In the discussion below, a client device, server device, virtual machine or container may be referred to simply as a “device” for brevity.

[0064] The term “message” or “communication” as used herein means one or more discrete bundles of data containing content, instructions, routing information, and/or authentication information. The content (i.e., payload) of a message may be part of the message, routing and authentication information may be included in another part such as a header, and the entire payload and header may be wrapped in an envelope. Messages can optionally be encrypted, e.g. through SSL and AES encryption protocols. Messages can be formatted in a standard data-format (e.g., JSON, XML, HTML, and the like).

[0065] The terms “memory,” “memory device,” “data store,” “data storage facility” and the like each refer to a non-transitory device on which computer-readable data, programming instructions or both are stored. Except where specifically stated otherwise, the terms “memory,” “memory device,” “data store,” “data storage facility” and the like are intended to include single device embodiments, embodiments in which multiple memory devices together or collectively store a set of data or instructions, as well as individual sectors within such devices. A computer program product is a memory device with programming instructions stored on it. [0066] The terms “processor” and “processing device” refer to a hardware component of an electronic device that is configured to execute programming instructions. Except where specifically stated otherwise, the singular term “processor” or “processing device” is intended to include both single-processing device embodiments and embodiments in which multiple processing devices together or collectively perform a process.

[0067] In this document, the terms “communication link” and “communication path” mean a wired or wireless path via which a first device sends communication signals to and/or receives communication signals from one or more other devices. Devices are “communicatively connected” if the devices are able to send and/or receive data via a communication link. “Electronic communication” refers to the transmission of data via one or more signals between two or more electronic devices, whether through a wired or wireless network, and whether directly or indirectly via one or more intermediary devices. The term “wireless communication” refers to communication between two devices in which at least a portion of the communication path includes a signal that is transmitted wirelessly, but it does not necessarily require that the entire communication path be wireless.

[0068] In this document, when terms such as “first” and “second” are used to modify a noun, such use is simply intended to distinguish one item from another, and is not intended to require a sequential order unless specifically stated.

[0069] It is to be appreciated that the Detailed Description section, and not any other section, is intended to be used to interpret the claims. Other sections can set forth one or more but not all exemplary embodiments as contemplated by the inventor(s), and thus, are not intended to limit this disclosure or the appended claims in any way.

[0070] While this disclosure describes example embodiments for example fields and applications, it should be understood that the disclosure is not limited to the disclosed examples. Other embodiments and modifications thereto are possible, and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and/or entities illustrated in the figures and/or described in this document. Further, embodiments (whether or not explicitly described) have significant utility to fields and applications beyond the examples described in this document.

[0071] Embodiments have been described in this document with the aid of functional building blocks illustrating the implementation of specified functions and relationships. The boundaries of these functional building blocks have been arbitrarily defined in this document for the convenience of the description. Alternate boundaries can be defined as long as the specified functions and relationships (or their equivalents) are appropriately performed. Also, alternative embodiments can perform functional blocks, steps, operations, methods, etc. using orderings different than those described in in this document.

[0072] References in this document to “one embodiment,” “an embodiment,” “an example embodiment,” or similar phrases, indicate that the embodiment described can include a particular feature, structure, or characteristic, but every embodiment can not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it would be within the knowledge of persons skilled in the relevant art(s) to incorporate such feature, structure, or characteristic into other embodiments whether or not explicitly mentioned or described in this document. Additionally, some embodiments can be described using the expression “coupled” and “connected” along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some embodiments can be described using the terms “connected” and/or “coupled” to indicate that two or more elements are in direct physical or electrical contact with each other. The term “coupled,” however, can also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

[0073] The breadth and scope of this disclosure should not be limited by any of the above-described example embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A method for controlling a minor’s use of a messaging platform, the method comprising, by a processor: connecting, via a parent account, a minor account to an approved adult account by: presenting, on a first user interface of the parent account, a list of contacts associated with the parent account; receiving, via the first user interface, a selection of a contact from the list of contacts to be linked to the minor account as the approved adult account, the contact including a user identifier and at least a contact information; presenting, on a second user interface associated with the minor account, an approved list of adult accounts, each of the approved list of adult accounts including a corresponding user identifier without contact information; and storing, in a data store, the contact information in association with the user identifier, wherein the parent account is linked in a supervisory capacity to the minor account, and the parent account, the minor account, and the approved adult account are configured to use the messaging platform in accordance with one or more permission rules of the messaging platform.

2. A method of claim 1, further comprising: receiving a selection, via the second user interface, of the user identifier for transmission of a communication to the approved adult account; retrieving the contact information for the approved adult account from the data store; and transmitting the communication to the approved adult account without presenting the contact information on the second user interface.

3. A method of claim 1, further comprising: presenting, on a third user interface associated with the approved adult account, an identifier of a minor associated with the minor account without contact information of the minor; and receiving, from the approved adult account, a second communication for transmission to the minor; transmitting the second communication to the minor account without presenting the contact information of the minor account on the third user interface.

4. A method of claim 1, further comprising identifying and deleting any contact information included within a communication sent to the minor account or from the minor account.

5. A method of claim 4, further comprising sending an alert to the parent account upon identification of that contact information.

6. A method of claim 1, further comprising presenting on the first interface the approved list of contacts as being associated with the minor account, and allowing the parent account to permit or block one or more features associated with each of the contacts in the approved list of contacts.

7. A method of claim 1, further comprising sending an alert to the parent account upon identification of an unapproved adult contact within a messaging group that includes the minor account.

8. A method of claim 1, further comprising linking the parent account in a supervisory capacity to the minor account by verifying a relationship between the between an adult associated with the parent account and a minor associated with the minor account.

9. A method of claim 1, further comprising: monitoring communications between the approved adult account and the minor account; and sending notifications to the parent account upon detection of a flagged activity.

10. A method of claim 9, wherein the flagged activity comprises detection of disallowed words, images, or contexts within the communications.

11. A method of claim 9, further comprising presenting, on the first user interface, a report comprising information relating to the flagged activity, the report further comprising at least a threshold number of communications transmitted before or after the flagged activity to or from the minor account.

12. A system for controlling a minor’s use of a messaging platform, the system comprising: a processor; and a non-transitory computer readable medium comprising programming instructions that when executed by the processor will cause the processor to: connect, via a parent account, a minor account to an approved adult account by: presenting, on a first user interface of the parent account, a list of contacts associated with the parent account, and receiving, via the first user interface, a selection of a contact from the list of contacts to be linked to the minor account as the approved adult account, the contact including a user identifier and at least a contact information; present, on a second user interface associated with the minor account, an approved list of adult accounts, each of the approved list of adult accounts including a corresponding user identifier without contact information; and store, in a data store, the contact information in association with the user identifier, wherein the parent account is linked in a supervisory capacity to the minor account, and the parent account, the minor account, and the approved adult account are configured to use the messaging platform in accordance with one or more permission rules of the messaging platform..

13. A system of claim 12, further comprising programming instructions that when executed by the processor will cause the processor to: receive a selection, via the second user interface, of the user identifier for transmission of a communication to the approved adult account; retrieve the contact information for the approved adult account from the data store; and transmit the communication to the approved adult account without presenting the contact information on the second user interface.

14. A system of claim 12, further comprising programming instructions that when executed by the processor will cause the processor to: present, on a third user interface associated with the approved adult account, an identifier of a minor associated with the minor account without contact information of the minor; and receive, from the approved adult account, a second communication for transmission to the minor; transmit the second communication to the minor account without presenting the contact information of the minor account on the third user interface.

15. A system of claim 1, further comprising programming instructions that when executed by the processor will cause the processor to identify and delete any contact information included within a communication sent to the minor account or from the minor account.

16. A system of claim 15, further comprising programming instructions that when executed by the processor will cause the processor to send an alert to the parent account upon identification of that contact information.

17. A system of claim 12, further comprising programming instructions that when executed by the processor will cause the processor to present on the first interface the approved list of contacts as being associated with the minor account, and allow the parent account to permit or block one or more features associated with each of the contacts in the approved list of contacts.

18. A system of claim 12, further comprising programming instructions that when executed by the processor will cause the processor to send an alert to the parent account upon identification of an unapproved adult contact within a messaging group that includes the minor account.

19. A system of claim 12, further comprising programming instructions that when executed by the processor will cause the processor to link the parent account in a supervisory capacity to the minor account by verifying a relationship between an adult associated with the parent account and a minor associated with the minor account.

20. A system of claim 12, further comprising programming instructions that when executed by the processor will cause the processor to: monitor communications between the approved adult account and the minor account; and send notifications to the parent account upon detection of a flagged activity.