Abstract: The technology teaches limiting sharing of visitor identity information across web sites, receiving from a visited web site server in a visitor's browser a page with a privacy script that runs in the browser and interfaces with a privacy ID server and third-party apps that seek visitor identification. The privacy script running in the browser retrieves a first party cookie including a visitor ID, forwards the cookie to the privacy ID server, receives from the privacy ID server, a site-by-app-specific ID for the visited site and one of the apps, and provides respective server site-by-app-specific IDs to respective third-party apps, without providing the visitor ID to the apps, thereby allowing tracking of the visitor on repeat visits to the visited site but not facilitating identification of the visitor across sites. Site-by-app-specific IDs for the visitor are distinct and uncorrelated for among distinct pairs of the web sites and third-party apps.

Abstract: A moving body setting system includes: an equipment control apparatus configured to control first equipment and second equipment included in a moving body; and a setting apparatus including: a storage unit configured to store setting information of each of the first equipment and the second equipment in association with user information; a user selection unit configured to select a user of the moving body; and a transmission control unit configured to read, from the storage unit, the setting information of the first equipment and the second equipment associated with user information of the user selected by the user selection unit, and perform control for transmitting, to the equipment control apparatus, first setting information which is based on the setting information of the first equipment that has been read and second setting information which is based on the setting information of the second equipment that has been read, and the equipment control apparatus is configured to change, at a timing at which bo

Abstract: The technology teaches limiting sharing of visitor identity information across web sites, receiving from a visited web site server in a visitor's browser a page with a privacy script that runs in the browser and interfaces with a privacy ID server and third-party apps that seek visitor identification. The privacy script running in the browser retrieves a first party cookie including a visitor ID, forwards the cookie to the privacy ID server, receives from the privacy ID server, a site-by-app-specific ID for the visited site and one of the apps, and provides respective server site-by-app-specific IDs to respective third-party apps, without providing the visitor ID to the apps, thereby allowing tracking of the visitor on repeat visits to the visited site but not facilitating identification of the visitor across sites. Site-by-app-specific IDs for the visitor are distinct and uncorrelated for among distinct pairs of the web sites and third-party apps.

Abstract: The technology disclosed relates to causing delivery of Segmentation as a Service™ (SegAAS) instrumentation code and segment processing code to run on a user's machine and generate data that tracks a user session on a website, receiving and processing data from the user session and invoking callback function code, configured to run on the user's machine, that performs actions specified by the website's operator, as triggered by delivery of segment codes. Also included is receiving readings from the user session, analyzing the data to track progress of the session, and generating segment codes that characterize results of the analysis in an actionable way specified by rules provided by the website operator. Further included are repeatedly causing delivery of updated lists of the segment codes based on the analyzing of the progress and timing delivery of unsolicited actions directed to retaining the visitor and extending the user session with the website.

Abstract: The technology disclosed relates to causing delivery of Segmentation as a Service™ (SegAAS) instrumentation code and segment processing code to run on a user's machine and generate data that tracks a user session on a website, receiving and processing data from the user session and invoking callback function code, configured to run on the user's machine, that performs actions specified by the website's operator, as triggered by delivery of segment codes. Also included is receiving readings from the user session, analyzing the data to track progress of the session, and generating segment codes that characterize results of the analysis in an actionable way specified by rules provided by the website operator. Further included are repeatedly causing delivery of updated lists of the segment codes based on the analyzing of the progress and timing delivery of unsolicited actions directed to retaining the visitor and extending the user session with the website.

Abstract: The technology teaches limiting sharing of visitor identity information across web sites, receiving from a visited web site server in a visitor's browser a page with a privacy script that runs in the browser and interfaces with a privacy ID server and third-party apps that seek visitor identification. The privacy script running in the browser retrieves a first party cookie including a visitor ID, forwards the cookie to the privacy ID server, receives from the privacy ID server, a site-by-app-specific ID for the visited site and one of the apps, and provides respective server site-by-app-specific IDs to respective third-party apps, without providing the visitor ID to the apps, thereby allowing tracking of the visitor on repeat visits to the visited site but not facilitating identification of the visitor across sites. Site-by-app-specific IDs for the visitor are distinct and uncorrelated for among distinct pairs of the web sites and third-party apps.

Abstract: The technology disclosed relates to causing delivery of Segmentation as a Service™ (SegAAS) instrumentation code and segment processing code to run on a user's machine and generate data that tracks a user session on a website, receiving and processing data from the user session and invoking callback function code, configured to run on the user's machine, that performs actions specified by the website's operator, as triggered by delivery of segment codes. Also included is receiving readings from the user session, analyzing the data to track progress of the session, and generating segment codes that characterize results of the analysis in an actionable way specified by rules provided by the website operator. Further included are repeatedly causing delivery of updated lists of the segment codes based on the analyzing of the progress and timing delivery of unsolicited actions directed to retaining the visitor and extending the user session with the website.

Abstract: The technology disclosed relates to causing delivery of Segmentation as a Service™ (SegAAS) instrumentation code and segment processing code to run on a user's machine and generate data that tracks a user session on a website, receiving and processing data from the user session and invoking callback function code, configured to run on the user's machine, that performs actions specified by the website's operator, as triggered by delivery of segment codes. Also included is receiving readings from the user session, analyzing the data to track progress of the session, and generating segment codes that characterize results of the analysis in an actionable way specified by rules provided by the website operator. Further included are repeatedly causing delivery of updated lists of the segment codes based on the analyzing of the progress and timing delivery of unsolicited actions directed to retaining the visitor and extending the user session with the website.

Abstract: The technology disclosed relates to causing delivery of Segmentation as a Service™ (SegAAS) instrumentation code and segment processing code to run on a user's machine and generate data that tracks a user session on a website, receiving and processing data from the user session and invoking callback function code, configured to run on the user's machine, that performs actions specified by the website's operator, as triggered by delivery of segment codes. Also included is receiving readings from the user session, analyzing the data to track progress of the session, and generating segment codes that characterize results of the analysis in an actionable way specified by rules provided by the website operator. Further included are repeatedly causing delivery of updated lists of the segment codes based on the analyzing of the progress and timing delivery of unsolicited actions directed to retaining the visitor and extending the user session with the website.

Abstract: The technology disclosed relates to causing delivery of Segmentation as a Service™ (SegAAS) instrumentation code and segment processing code to run on a user's machine and generate data that tracks a user session on a website, receiving and processing data from the user session and invoking callback function code, configured to run on the user's machine, that performs actions specified by the website's operator, as triggered by delivery of segment codes. Also included is receiving readings from the user session, analyzing the data to track progress of the session, and generating segment codes that characterize results of the analysis in an actionable way specified by rules provided by the website operator. Further included are repeatedly causing delivery of updated lists of the segment codes based on the analyzing of the progress and timing delivery of unsolicited actions directed to retaining the visitor and extending the user session with the website.

Abstract: An audio visual turn/hazard signaling system in a vehicle can include an electronic user-selectable sound file, a control circuitry containing a solid state relay, a sensor, and an amplifier. The signal system of the invention provides a customizable signal system including a sound file where the operator can choose the volume and frequency to play when turn signal is activated. The signal system of the invention also provides an automatic volume adjuster wherein the safety of the operator while operating a vehicle is enhanced.

Abstract: An audio visual turn/hazard signaling system in a vehicle can include an electronic user-selectable sound file, a control circuitry containing a solid state relay, a sensor, and an amplifier. The signal system of the invention provides a customizable signal system including a sound file where the operator can choose the volume and frequency to play when turn signal is activated. The signal system of the invention also provides an automatic volume adjuster wherein the safety of the operator while operating a vehicle is enhanced.

Abstract: An interface for programming a motor control of a motor includes a microcontroller in signal communication with a first signal port and a second signal port, and a solid state relay in signal communication with the microcontroller and the second signal port. The solid state relay includes a control element responsive to first and second signals from the microcontroller for turning on power and for turning off power, respectively, to the motor control, wherein the microcontroller is adapted for sending a programming signal from the computer to the motor control in response to the programming signal being sent within a defined time following the control element turning on power to the motor control.

Abstract: A system for document processing includes a user interface unit and a command unit having a context server, and an image I/O device interface. The command unit is coupled to a conventional application server and an image capture and generation device for routing image data and commands to the application server for processing. The user interface unit accepts commands and displays information to a user. The user interface unit sends data to and receives data from the command unit. The command unit is responsive to the user interface device and initiates a task or process by setting a context and passing that context and data to the application server. The device interface is coupled to the context server and the image capture and generation device. The context server controls processing of the image data according to the context, and then generates a receipt image and sends it to the device interface for output to the image capture and generation device.