Palantir Technologies Inc.

Michal Duczynski

Nicolas Trinquier

Harsh Pandey

Joseph Hashim

Jenny Fan

Ankit Shankar

Spencer Tank

Xinyi Wang

Arthur Thouzeau

Yeong Wei Wee

Alice Yu

Benedict Cappellacci

Sebastiaan Visser

Issei Nino

Matthew Rauen

Sorin-Alexandru Nutu

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

A user interface generation system and associated methods are disclosed for displaying nodes of a computer program or computation. The system may determine an ordering and position of elements for display. The ordering can include determining a first ancestor branch of a node associated with a stage with an earliest start time among the start times associated with the stages of a plurality of ancestor branches. This first ancestor branch may be designated as first in the ordering. A second ancestor branch may be determined from among the remaining ancestor branches having an stage with an earliest start time among the start times associated with the remaining stages. This second ancestor branch can be designated as second in the ordering.

Interactive graph generation for computation analysis

Display screen or portion thereof with graphical user interface

Methods, systems, and computer-readable media described herein may include: obtaining first data from a first datastore managed by a first entity, the first data comprising a first status of a first task of a first subsidiary workflow that is part of an integrated workflow; integrating the first data into a second datastore managed by a second entity that manages the integrated workflow, with an integration layer; generating a graphical user interface to present an interactive graphical object that displays the integrated first data and the integrated workflow to a user; receiving one or more updates from the user to the integrated first data, where the one or more updates are based on one or more graphical user interactions with the integrated first data; identifying a change to a portion of the first data; and writing the change in the first datastore using the integration layer interface.

Automating management of integrated workflows based on disparate subsidiary data sources

Growing community of inventors

Pecice, Poland

Michal Duczynski