Palantir Technologies Inc.

Pieris Christofi

Sam Stoll

Arnav Jagasia

Ashley Meuser

Nicolas Prettejohn

Mihir Patil

Mihai Condur

Hugo Dobbelaere

Craig Massie

Alexandra Greehy

Helena Kertesz

Alexander Bell-Thomas

Systems and methods for lineage-aware data retention are provided. An example method includes receiving information of a committed transaction. The committed transaction is configured to add or change data to a dataset. The example method further includes receiving one or more lineages for the committed transaction, determining one or more parent transactions based at least in part on the one or more lineages, obtaining one or more parent retention dates that correspond to the one or more parent transactions respectively, and determining a transaction retention date for the committed transaction based at least in part on the one or more parent retention dates.

Systems and methods for lineage-aware data retention

A computer system provides transaction-level data retention policy inheritance. The system may perform operations including storing a first dataset comprising a plurality of transactions, each of the plurality of transactions comprising one or more data items; receiving a first transaction to the first dataset, the first transaction comprising one or more data items; determining a first retention policy for the first transaction; and storing the first retention policy with the first transaction. The system may further perform operations including calculating a deletion date for the first transaction based on the first retention policy; and storing the deletion date with the first transaction in the first dataset.

Transaction-level data retention policy inheritance

A computer system provides shared access to electronic data assets. The system may perform operations including: receiving, from a first user, a request to access a shared data asset, wherein: the shared data asset is associated with a shared data asset object, and the shared data asset object identifies at least a second user authorized to approve sharing of the shared data asset; in response to receiving the request from the first user: generating a data access request object including at least an identification of the first user and an identification of the shared data asset object; and providing an indication of the data access request object to the second user associated with the shared data asset object; receiving, from the second user, an approval of the request; and in response to receiving the approval of the request from the second user: granting the first user access to the shared data asset associated with the shared data asset object.

Data asset sharing

Growing community of inventors

London, United Kingdom

Pieris Christofi