You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Objective: We have a pending Pull Request (PR #2167) that updates the "How is my data stored?" section of the Gitcoin Passport documentation. This update aims to provide a clearer, more user-friendly explanation of our data storage practices, focusing on security, privacy, and data portability. The revisions incorporate details about our encryption methods, the use of Ceramic and our proprietary database for data integrity, and the integration with Ethereum's Layer 2 solutions for enhanced data portability.
Feedback: Provide any feedback or request changes if necessary. If there are suggestions for improvement, please communicate these clearly to ensure timely adjustments.
Merge if Approved: If the PR meets all requirements and is deemed beneficial for the project, please proceed to merge it into the main branch. Ensure that all merge conflicts, if any, are resolved before finalizing.
Additional Notes: This update is part of our ongoing efforts to enhance the user experience and trust in our platform. It's crucial that the explanation is both technically accurate and accessible to our diverse user base, including those new to Web3.
The text was updated successfully, but these errors were encountered:
Objective: We have a pending Pull Request (PR #2167) that updates the "How is my data stored?" section of the Gitcoin Passport documentation. This update aims to provide a clearer, more user-friendly explanation of our data storage practices, focusing on security, privacy, and data portability. The revisions incorporate details about our encryption methods, the use of Ceramic and our proprietary database for data integrity, and the integration with Ethereum's Layer 2 solutions for enhanced data portability.
Tasks:
Additional Notes: This update is part of our ongoing efforts to enhance the user experience and trust in our platform. It's crucial that the explanation is both technically accurate and accessible to our diverse user base, including those new to Web3.
The text was updated successfully, but these errors were encountered: