Skip to content

Commit

Permalink
rfc(decision): Document sensitive data collected
Browse files Browse the repository at this point in the history
  • Loading branch information
antonpirker committed Jan 27, 2023
1 parent acb0400 commit 44a4651
Show file tree
Hide file tree
Showing 2 changed files with 36 additions and 0 deletions.
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,3 +30,4 @@ This repository contains RFCs and DACIs. Lost?
- [0047-introduce-profile-context](text/0047-introduce-profile-context.md): Add Profile Context
- [0048-move-replayid-out-of-tags](text/0048-move-replayid-out-of-tags.md): Plan to replace freight with GoCD

- [0070-document-sensitive-data-collected](text/0070-document-sensitive-data-collected.md): Document sensitive data collected
35 changes: 35 additions & 0 deletions text/0070-document-sensitive-data-collected.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
- Start Date: 2023-01-27
- RFC Type: decision
- RFC PR: https://github.com/getsentry/rfcs/pull/70
- RFC Status: draft

# Summary

One paragraph explanation of the feature or document purpose.

# Motivation

Why are we doing this? What use cases does it support? What is the expected outcome?

# Background

The reason this decision or document is required. This section might not always exist.

# Supporting Data

[Metrics to help support your decision (if applicable).]

# Options Considered

If an RFC does not know yet what the options are, it can propose multiple options. The
preferred model is to propose one option and to provide alternatives.

# Drawbacks

Why should we not do this? What are the drawbacks of this RFC or a particular option if
multiple options are presented.

# Unresolved questions

- What parts of the design do you expect to resolve through this RFC?
- What issues are out of scope for this RFC but are known?

0 comments on commit 44a4651

Please sign in to comment.