FIELD OF THE INVENTION
[001] The present disclosure relates to the field of data extraction. Particularly, the disclosure
provides a system and method for timely and accurate extraction of event data from user devices.
BACKGROUND OF THE INVENTION
[002] Every media where content is published needs to have a system for measuring the number of consumers, the demographic details of consumers, time of consumption of content and usage patterns of consumers. This measurement may require capturing event data
corresponding to a user accessing media on a user device.
[063] One method for such measurement may comprise using TV audience meters placed at households which measure clicks of remote used for switching channels. Other traditional approaches may include, for example, methods for measurement of Radio FM based usage by end consumer by using "Paper Diary" and Computer Aided Telephonic Interview (CATI)
methods. Audio and video streaming applications such as YouTube™ employs Digital methods for measurements.
[004] The existing methods for such measurement have several shortcomings including challenges relating to scalability and accuracy in the existing technologies. Specifically, the step of capturing event data from a device for such* measurement suffers due to inaccuracies in the. method for extracting event data. For example, while using Paper Diary there exist challenges of forgetting the .content that has been heard, which may lead to inaccuracies. While using CATI the call completion rates of panels is known to be very low. Portable Personal Meters, another technique used for measurements, uses Audio Character Recognition of heard sound which is still not a completely accurate technology and leads to inaccuracies in event data extraction.
[005] Thus, there is a need of a system and method to mitigate the above mentioned drawbacks of the existing systems and methods for data extraction.

SUMMARY OF THE INVENTION
[006] Before the present methods, systems, and hardware enablement are described, it is to be understood that this invention is not Eimited to the systems, and methodologies described, as there can be multiple possible embodiments of the present invention which are not expressly illustrated in the present disclosure. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present invention.
[007] The present application provides a method and system for accurate and timely extraction of specific event data from user devices. In one embodiment, the user device may be a device comprising thereon a real-time or any other operating system. Examples of user devices may include, but are not limited to a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, a tablet, a mobile phone, and the like. In another embodiment, the user device comprises thereon at least one processing unit coupled to a memory wherein the system to implement the disclosed method is implemented using the processing unit of the user device. In an embodiment, the processing unit maybe retrofitted onto the user device or may be a preexisting processor of the user device. In another embodiment, the processing unit is a pre-existing processing unit of said user device to implement system and method of the present invention. In still another embodiment, the processing unit is a processor.
[008] In one aspect, the invention discloses a system for timely and accurate extraction of event data, operatively connected to a user device comprising a processing unit including at least one processor to implement said system) on said user device; a memory unit coupled to said processing unit to store event data of said user device; a plurality of components to identify, extract and transfer event data from said user device; wherein said plurality of components are coupled to said memory unit for implementation by said processing unit. In one embodiment, the memory unit is retrofitted onto said user device. In another embodiment, the memory unit is a memory location allocated to system on the user device to implement said system. In still another embodiment, the memory unit is a pre-existing memory unit of the user device.
2

[009] In another aspect of the invention, the system as is communicatively connected to a backend server through a network connection. The backend server is configured to analyze the data extracted by said system and provide consumption patterns to a user of said system. The system further includes at least one input/output interface for communication with a user. The event data is stored in a pre-existing location on occurrence of an event on the user device, wherein the pre-existing location for the event data is generated by the operating system of the user device.
[0010] In another embodiment, the system comprises various components, each component having a predefined function to perform. In one embodiment, the system comprises a data identification component configured to identify whether an event data in a preexisting location corresponds to a predetermined event type. The event data is stored in the preexisting location on occurrence of an event on the user device. As an example, in one aspect, the user device may be a Smartphone running on an operating system. An event data is stored in the location and is generated for each event in the user device such that the event data may comprise details on use of any applications, such as time of accessing and exiting applications and the like. In yet another embodiment, the real-time operating system or normative operating system of the device may generate the preexisting location.
[0011] In another embodiment, the system of the present invention further comprises a data extraction component configured to extract event data from the preexisting location on identification event data corresponding to an event type and stores in a memory.
[0012] The system further comprises a data transfer component configured to transfer the extracted event data to a backend server over a network for further analysis. In one embodiment, the data transfer component detects availability of network connection to the user device and on detection of network connectivity transfers the extracted event data to a backend server.
[0013] In yet another embodiment, the system comprises other component configured to perform
at least one of the function of securing, encrypting, decrypting, indicating data extracted, depending on the veracity and sophistication of the user device, for securing the data extracted.
3

[0014] In yet another aspect of the invention, the plurality of components are structured as a single component unit with at least one processor to enable the functioning of the plurality of components and the processor of the single component unit is coupled to a memory for implementation of the system and method disclosed by the present invention. In another aspect, the plurality of components comprises at least one processor to enable the functioning of each of said components. The processor of each of the plurality of components is further coupled to a memory.
[0015] In still another aspect of the invention, a method for timely and accurate extraction of event data from a user device is disclosed. The method comprises the steps of:
a) identifying whether an event data in a pre-existing location created by said user device corresponds to a predefined event type;
b) extracting the event data on identification of the predefined event type;
c) storing the extracted event data in a memory unit (206); and
d) transferring the event data to a backend server connected to said user device through a network for further analysis-.
[0016] The event data in the present invention is stored in a pre-existing location on occurrence
of an event on the user device. The pre-existing location for the event data is generated by the operating system of the user device, The identification in step (a), of whether an event data in said pre-existing location created by said user device corresponds to a predetermined event type is carried out by a data identification component. In step (b), on identification of the predefined event type in step (a), the event data is extracted using a data extraction component. The data extraction component is further configured to store the extracted, event data in a memory unit (step (c)). The event data is then transferred to a backend server using a data transfer component, as in step (d). The data transfer component of the present invention, is configured to transfer the extracted event data stored in the memory unit or a data storage to the backend server. The data transfer component is further configured to detect the availability of network connection between
4

the user device and the backend server and transfer the event data to the backend server on detection of network connection with the user device. The data transfer component is also configured to make periodic detections for a network connection till the network connection is established. The data transfer component is also configured to delete the event data from said memory unit, m another aspect of the invention, the method further includes the step of securing the securing the data extracted from said user device using an other component.
[0017J The method as disclosed by the present invention is implemented using the system as described in the paragraphs above with the help of the components, memory unit and processors.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The foregoing summary, as well as the following detailed description of preferred embodiments, are better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and system disclosed in the drawings:
[0019] Fig. 1 illustrates an architecture for implementing the system and method for timely and accurate extraction of event data, according to an embodiment of the present invention;
[0020] Fig. 2 illustrates the system for timely and accurate extraction of event data, in accordance with an embodiment of the present invention ;
[0021] Fig. 3 illustrates a flowchart showing the various steps involved in the method for timely and accurate extraction of event data, according to an embodiment of the present invention;
[0022] Fig*4 illustrates a user device including various components coupled to a memory according to an embodiment of the present invention; and
5

[0023] Fig. 5 illustrates a user device comprising of a system for components coupled to the input and output devices and a memory coupled to said system according to an embodiment of
the present invention.
DETAILED DESCRIPTION OF THE INVENTION
[0024] The detailed description set forth below in connection with the appended drawings is intended as a description of various embodiments of the present invention and is not intended to represent the only embodiments in which the present mvention may be practiced. Each embodiment described in this disclosure is provided merely as an example or illustration of the present invention, and should not necessarily be construed as preferred or advantageous over other embodiments. The detailed description includes specific details for the purpose of providing a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without these specific details
[0025] The words "comprising," "having," "containing," and "including," and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.
[0026] It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. Although any systems and methods similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present invention, the preferred, systems and methods are now described.
[0027] The disclosed embodiments are merely exemplary of the invention, which may be embodied in various forms.
[0028] The elements illustrated in the Figures inter-operate as explained in more detail below. Before setting forth the detailed explanation, however, it is noted that all of the discussion below,
6

regardless of the particular implementation being described, is exemplary in nature, rather than limiting.
[0029] Method steps of the invention may be performed by one or more processors. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, the processor receives (reads) instructions and data from a memory (such as a read-only memory and/or a random access memory) and writes (stores) instructions and data to the memory. Storage devices suitable for tangibly embodying computer program instructions and data include, for example, all forms of non-volatile memory, such as semiconductor memory devices, including EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROMs. Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits) or FPGAs (Field-Programmable Gate Arrays).
[0030] Fig. 1 illustrates an architecture for implementing the system (104) for timely and accurate extraction of event data. In one embodiment, an event data is stored in a preexisting location on the user device (216) on occurrence of an event. In another embodiment, the real-time operating system of a user device (216) generates the preexisting location containing event data corresponding to each event on the user device (216). The user device (216) may be any computing device such as a mobile phone, tablet, computer, laptop and the like. In one specific example, the user device (216) may be a Smartphone comprising a mobile operating system wherein an event data is generated on user accessing and exiting any application on the Smartphone. The event data may comprise information on the time and time-period for which an application is accessed on the user device. The event data may comprise details on usage of any application on the Smartphone. The techniques disclosed in this application are independent of the operating system of the user device. In an embodiment, the predefined event type may be defined as "accessing media applications". In another embodiment, the predefined event type may be defined as accessing a specific application such as radio (FM / AM / Digital / Internet) application wherein the event data includes the time of accessing the radio (FM / AM / Digital / Internet) application, the'time of exiting the radio (FM / AM / Digital / Internet) application, the
7

stations tuned in while accessing the radio application. In another embodiment, this technique may enable a system administrator to define the predefined event to be extracted in real time.
[0031] The system (104) is communicatively coupled to a backend server (102) through a network (106) and the user device (216). In an embodiment, the user device (216) may include the system (104) operatively connected to having a real time operating system or a normative operating system. In another embodiment, a plurality of user devices ("N" user devices) is connected to the network (206). In another embodiment, at least one of the user device (216) from crN" user devices include the system (104) operatively connected to said user devices and running on the devices, said user device (216) having a real time operating system or a normative operating system running thereon. In an embodiment, the system (104) may use the processor associated with the device for implementing the system (104) on the user device. In another embodiment, the system may use a processor specifically added to implement the system (104) on the user device (216).
[0032] Although the present invention is explained considering that the backend server (102) is implemented as a computing system, it may be understood that the backend server (102) may
also be implemented as a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, a tablet, a mobile phone, and the like. In an embodiment, the backend server (102) is implemented in a cloud-based environment. In another embodiment, the backend server (102) may also be configured to track the activities of the system (104). In one aspect of the invention, the backend server (102) is configured to analyze the event data to generate analysis report on user consumption preference and/or usage patterns of end users/consumers. In another aspect, the backend server (102) is configured to transmit user consumption preference back to the user on his device. In yet another aspect of the invention, the backend server (102) is configured to send the consumption patterns of users to third parties. The backend server (102) has requisite analytical capabilities, to analyze external data sets that can be interfaced with the server which has the measurement data as extracted from the device. The correlation analysis could be using specific algorithms that are written for very specific cases, depending on the use case of type of device(s) and type of data sets being interfaced.
8

[0033] In an embodiment, the network (106) may be a wireless network, a wired network or a combination thereof. The network may be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), and the like, to communicate with one another. In another embodiment, the network (106) may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. In another embodiment, the devices may not be connected to the network (206) at all times and may connect and disconnect to the network (206) at various intervals of time.
[0034] Fig. 2 illustrates the system (104) for timely and accurate extraction of event data from a user device (216), according to an embodiment of the present invention. In the embodiment, the system (104) includes at least one processor (202). In one aspect, the at least one processor is a processor of the user device (216) configured to implement the system (104). In another aspect, the at least one processor is a processor other than the processor of the user device (216) which is configured to implement the system (104) on the user device (216). The at least one processor (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. The system (104) further comprises an input/output (I/O) interface (204), and a memory (206). The I/O interface (204) may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface (204) may allow the system (104) to interact with the user. Further, the I/O interface (204) may enable the system (104) to communicate with other computing devices, such as web servers and external data servers. The I/O interface (204) can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. In an embodiment, the memory (206) is the memory of the user device (216). In another embodiment, the memory (206) is the memory other than the
9

memory of the user device which may be retrofitted onto the user devices (216). In another embodiment, the memory (206) is a memory location allocated to the system (104) on the user device (216) for implementation of the system (104). The memory (206) may include any computer-readable medium for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0035] In an embodiment of the invention, the at least one processor (202) is configured to identify whether an event data in a preexisting location corresponds to a predetermined event type. In another embodiment, the processor (202) is further configured to extract event data from the preexisting location on identification of event data corresponding to an event type and stores in the memory (206). Furthermore, the processor (202) is configured to transfer the extracted event data to a backend server (102) over a network (106) for further analysis. In yet another embodiment, the processor detects availability of network connection to the user device (216) and on detection of network connectivity transfers the extracted event data to a backend server (102).
[0036] In an embodiment, the system (104) comprises a plurality of components configured to identify, extract and transfer event data from said user device (216). In one embodiment, the plurality of components include a Data Identification Component (210) configured to identify
whether an event data in a preexisting location corresponds to a predetermined event type.
[0037] In another embodiment, the system (104) comprises a Data Extraction component (212) configured to extract the event data on identification of the predefined event type by the event identification component (210). The data extraction component (212) is configured to extract the event data before the identified event data is deleted from the preexisting location. In an embodiment, the preexisting location may be a FIFO stack of a predefined length wherein the event data is deleted from the location according to FIFO rules on occurrence of a new event'on the user device. In an embodiment, the preexisting location may be a FS LO stack of a predefined length wherein the event data is deleted from the location according to FILO rules on occurrence
10

of a new event on the user device. The Data Extraction component (212) is further configured to
store the extracted data in a location illustrated as "Data storage (220)" as illustrated in Figure 2. Data storage (220), serves as a repository for storing extracted event data.
[0038] In yet another embodiment, the system (104) comprises a Data Transfer component (214) configured to transfer the extracted data stored at location "Data storage (220)" to a backend server (102). The Data Transfer component (214) may be configured to detect availability of a network connection on the user device (216) after storing of at least one event data in a specific location of the data storage. On detecting network connectivity, the Data transfer component (214) transfers the event data stored at the location of the Data storage (220), to a backend server (102). In an aspect, the Data transfer component (214) is configured to delete the event data from the Data storage (220), freeing the memory at the Data storage (220).
[0039] Instill another embodiment, the system comprises an other component (218) configured
to perform at least one of the function of securing, encrypting, decrypting, indicating data extracted, depending on the veracity and sophistication of the user device. In one aspect, the other component (218) is a Data Securing Component for securing the data extracted from the user device (216). In another aspect, the other component is a Data Encrypting Component configured to encrypt the event data extracted from the pre-existing location. In another aspect, the other component (218) is a Data Decrypting component configured to decrypt the event data extracted form the pre-existing location.
[0040] In one embodiment, the system (104) comprising of plurality of components (210, 212, 214, 218) is an external system communicatively coupled to network (106) and user device . (216), as illustrated in Fig. 2. In an alternative embodiment, the system (104) is a part of the user device, as illustrated in Figs. 3 and 4. In Fig. 3, the user device (216) comprises a processing unit consisting the components (210, 212, 214, 218) coupled to a memory of the said system (104). The components shown herein maybe hardware components or may be implemented as a software. In an embodiment, each component may comprise a processor associated with the component enabling said component to perform its function. In another embodiment, the
11

processors of each component are coupled to a memory as shown in Fig. 3 wherein the memory maybe a retrofitted memory or a pre-existing memory of the user device (216).
[0041] As illustrated in Fig. 4, the user device (216) comprises a processing unit consisting of a single component coupled to a memory. The single component may comprise at least one processor to enable the functionalities of all tbe components (210, 212, 214, 218)) shown in Fig. 2 and Fig. 3. In an embodiment, the single component may be a hardware component comprising at least one processor retrofitted to the user device. In another embodiment, the component may use apre-exiting processor of the user device (216) for implementation.
[0042] Fig. 5 illustrates the various steps of the method for accurate and timely extraction of specific event data from user devices (216). Step 302 includes identifying whether an event data in a pre-existing location on a user device (216) corresponds to a predetermined event type. At the step 304 if the event data is not identified as the predefined event type, the location is periodically rechecked to identify the predefined data type. At the step 306, when the event data is identified as corresponding to a predefined event data, the event data is extracted from the location. In an embodiment, the event data is extracted before the event data gets deleted from the location. In an embodiment, the location may be a FIFO stack of a defined length where event data gets deleted from the location due to addition of new data into the location. In an embodiment, the location may be a FILO stack of a defined length where event data gets deleted from the location due to addition of new data into the location. The step 308 illustrates that the extracted event data is then stored in a memory unit (206). At the step 310, a network connection with the user device is detected. When a network connection (106) is not detected, as illustrated at the step 312, periodic detections are made to check for network connection (106). In an embodiment, the detection of network connection is initiated only when at least one event data is extracted and stored in a memory unit (206). Lastly, at the step 316 the network connection (106) is detected and the extracted event data is transferred to a backend server (102).
[0043] In an embodiment, the backend server (102) may analyse the extracted event data and provide consumption patterns to a user of the user device. In another embodiment, the backend server (102) may perform analysis and shares the data to a third party which may be use the data for providing recommendation to the users of a user device. This backend server (102) will have
12

requisite analytical capabilities, with algorithms that can analyse external data sets that can be interfaced with the server which has the measurement data as extracted from the device. The correlation analysis could be using specific algorithms that are written for very specific cases, depending on the use case of type of device/s and type of data sets being interfaced.
[0044] Various modifications to these embodiments are apparent to those skilled in the art from the description and drawings herein. The principles associated with the various embodiment defined herein may be applied to other embodiments. Therefore, the description is not intended to be limited to the embodiments shown along with the accompanying drawings but is to be provided broadest scope consistent with the principles and novel and inventive features describe/disclosed or suggested herein. Any modifications, equivalent substitutions, improvements etc. within the spirit and principle of the present invention shall all be included in the scope of protection of the present invention.

CLAIMS
1) A system (104) for timely and accurate extraction of event data, operatively connected to
a user device (216) comprising:
a processing unit including at least one processor (202) to implement said system (104)
on said user device (216);
a memory unit (206) coupled to said processing unit to store event data of said user
device (216);
a plurality of components to identify, extract and transfer event data from said user
device (216);
wherein said plurality of components are coupled to said memory unit (206) for
implementation by said processing unit.
2) The system as claimed in claim 1, wherein said system (104) is communicatively connected to a backend server (102) through a network connection (106).
3) The system as claimed in claim 2, wherein said backend server (102) is configured to analyze the data extracted by said system (104) and provide consumption patterns to a
user of said system (104).
4) The system as claimed in claim 1, wherein said system (104) includes at least one input/output interface for communication with a user.
5) The system as claimed in claim 1, wherein said system (104) is operatively connected to an operating system of said user device (216).
6) The system as claimed in claim I, wherein said processing unit is a pre-existing processing unit of said user device (216) to implement said system (104).
7) The system as claimed in claim 1, wherein said processing unit is retrofitted onto said system (104) to implement said system.

8) The system as claimed in claim 1, wherein said memory unit (206) is a pre-existing memory unit of said user device (216).
9) The system as claimed in claim 1, wherein said memory unit (206) is retrofitted onto said user device (216).
10) The system as claimed in claim 1, wherein said memory unit (206) is a memory location allocated to system on said user device to implement said system.
11) The system as claimed in claim 1, wherein the event data can be extracted from a
plurality of user devices (216).
12) The system as claimed in claim 1, wherein the event data is stored in ,a pre-existing location on occurrence of an event on said user device (216).
13) The system as claimed in any one of the claims 1 and 6, wherein said pre-existing location for the event data is generated by the operating system of said user device (216).
14) The system as claimed in claim 1, wherein said plurality of components are structured as a single component unit with at least one processor to enable the functioning of said plurality of components.
15) The system as claimed in claim 14, wherein said processor of said single component unit
is coupled to a memory.
16) The system as claimed in claim 1, wherein each of said plurality of components, comprises at least one processor to enable the functioning of each of said components.
17) The system as claimed in claim 16, wherein said processor of each of said plurality of components are coupled to a memory.
18) The system as claimed in any one of the preceding claims, wherein said plurality of components include at least a data identification component (210) configured to identify

whether said event data in said pre-existing location created by said user device (216) corresponds to a predetermined event type; at least a data extraction component (212) configured to extract the event data on identification of said predefined event type by the data identification component (210); and at least a data transfer component (214) configured to transfer the event data to said backend server (102).
19) The system as claimed in claim 18, wherein said plurality of components include another component (218) configured to perform at least one of the functions of securing, encrypting, decrypting and indicating data extracted from said user device (216).
20) The system as claimed in claim 18, wherein said data extraction component (212) is configured to store the extracted event data in a data storage (220).
21) The system as claimed in claim 18, wherein said data transfer component (214) is configured to transfer the extracted event data stored in said data storage (220) to said backend server (102).
22) The system as claimed in claim 18, wherein said data transfer component (214) is configured to detect the availability of network connection between said user device (2.16) and said backend server (102) and transfer the event data to said backend server (102) on detection of network connection with said user device.
23) The system as claimed in claim 18, wherein said data transfer component (214) is configured to periodically delete the event data from said data storage (220) on said user device (2.16)
24) A method for timely and accurate extraction of event data from a user device (216) comprising the steps of:

a) identifying whether an event data in a pre-existing location created by said user device corresponds to a predefined event type;
b) extracting the event data on identification of the predefined event type;
c) storing the extracted event data in a memory unit (206); and
16

d) transferring the event data to a backend server connected to said user device through a network for further analysis.
25) The method as claimed in claim 24, wherein said method is implemented using a system (104) including at least one processor coupled to said memory unit (206).
26) The method as claimed in claim 24, wherein the identification whether an event data in said pre-existing location created by said user device corresponds to a predetermined
event type is carried out by a data identification component (210).
27) The method as claimed in claim 24, wherein the extraction of the event data on identification of the predefined event type is carried out by a data extraction component (212).
28) The method as claimed in claim 28, wherein said data extraction component (212) is configured to store the extracted event data in a data storage (220).
29) The method as claimed in claim 24, wherein the transfer of the event data to said backend server connected to said user device is carried by a data transfer component (214).
30) The method as claimed in claim 30, wherein said data transfer component (214) is configured to transfer the extracted event data stored in said data storage (220) to a backend server (102).
31) The method as claimed in any one of the claims 24, 30 and 31, wherein said data transfer component (214) is configured to detect the availability of network connection between said user device (216) and said backend server (102) and transfer the event data to said backend server (102) on detection of network connection with said user device.
17

32) The method as claimed in claim 32, wherein said data transfer component (214) is configured to make periodic detections for a network connection till the network connection is established.
33) The, method as claimed in claim 30, wherein said data transfer component (214) is configured to delete the event data from said data storage (220).
34) The method as claimed in claim 24, wherein the event data is stored in a pre-existing location on occurrence of an event" on said user device (216).
35) The method as claimed in claim 24, wherein said pre-existing location for the event data is generated by the operating system of said user device (216).
36) The method as claimed in any one of the preceding claims, wherein said method includes a step of securing the data extracted from said user device.