Palantir Technologies Inc.

Yeong Wei Wee

Alice Yu

Andrew Lampert

Natalie Meurer

Dyon Balding

Emily Wang

Matthew Sills

Megha Arora

Hao Dang

Michal Duczynski

Samuel Szuflita

Mihir Patil

Leslie Bennett

Kevin Meurer

Disclosed herein are systems and techniques for centralized data retention and deletion. Data can be ingested from multiple external data sources and saved internally for use to process data modification (e.g., deletion) requests via a data processing pipeline, which may apply eligibility checks and modification logic to determine the appropriate modifications to the relevant data items to comply with the data modification request. Various user interfaces may be generated to provide a user with oversight of the data processing pipeline and the data modifications. The user may review and trigger the modification of data stored at the external data sources and/or internally.

Centralized data retention and deletion system

Systems and methods are provided for improved auditing of user actions associated with a software application. The system includes functionality to log user actions in a structured, standardized way. The system includes interactive user interfaces for analyzing the logs. The logging is based on a well-defined categorization of available actions. The log information includes (and distinguishes among) user details, context details, user inputs, and/or system outputs (including identification of data objects). The interactive user interfaces enable a user to view structured log data in an efficient manner, such as by presenting logs in a tabular format, executing queries on the log data, and/or presenting visualizations that summarize the log data. The interactive user interfaces provide functionality that allows a user to investigate and/or audit user interactions with a data object. A reviewer is permitted to drag and drop one or more data objects of interest from the software application directly into the interactive user interfaces. The interactive interfaces present log entries associated with the object(s) for further review by the reviewer.

Audit logging database system and user interface

A system and method can provide charter-based access to resources using an object model. Charters are defined by an administrator to have certain markings, each marking indicating a control (e.g., permission, credential, qualification, constraint, requirement, etc.) that regulates work under the charter. Users are also associated with markings. A user starts a session to access the system and is authenticated. The system determines charters having markings that the user has, and these charters are provided to the user to select from. Selecting a charter allows the user access to resources associated with the charter, under the controls indicated by the markings. Charters, controls, qualifications, resources, authorizations and links between them can be implemented using an object model. Markings can control session parameters (e.g., geographic location), resource access, user credentials, qualifications, and/or data processing permissions for a group of users, simplifying project definition and revisions to controlling access under the charter.

Charter-based access controls for managing computer resources

Systems and methods are provided for processing an input dataset or running an inference. The systems and methods may be configured to accept an input dataset, access one or more predefined logic plugins for processing the input dataset, process the input dataset based at least in part on a first predefined logic plugin, and generate the one or more outputs based at least in part of the processing of the input dataset. The one or more outputs may have a different format than a format of the input dataset.

Systems and methods for customizing a process of inference running

Systems and methods are provided for determining a set of objects, the objects corresponding to a given case or application of a deletion/retention policy; determining at least one object in the set of objects to be scheduled for deletion, the at least one object being associated with a given state that specifies a deletion and/or retention type and schedule for the at least one object; and scheduling data corresponding to the at least one object for deletion from one or more data sources based at least in part on the deletion and/or retention type and schedule specified in the object state.

Approaches for managing data retention lifecycle

Growing community of inventors

London, United Kingdom

Yeong Wei Wee