Feedback
Roadmap

Have something to say?

Tell us how we could make the product more useful to you.

Add “Self-Audit Toolkit” and Evidence Retention Features for Standards Compliance

Category: Governance & Trust Description: To support self-assessments and reviews aligned with DGSI or similar digital governance standards, we propose the addition of an Audit Toolkit feature within OpenPolicy.me. This feature should help institutional and civic tech users demonstrate integrity, transparency, and compliance through internal review mechanisms. Key Functionality: Audit Checklist Builder based on selected standards (e.g., AI ethics, cybersecurity, data governance) Evidence Uploads & Tagging for screenshots, documents, or in-app usage logs Evidence Storage with Timestamps to support audit trails Progress Tracker showing completion status against standards Downloadable Audit Summary Report for sharing with partners, funders, or councils Why this matters: A growing number of civic tech platforms like OpenPolicy.me are being evaluated against public trust and digital governance frameworks. This feature helps maintain readiness for formal audits, reviews, or certifications by capturing continuous evidence and encouraging best practices in ethical development and transparency. Linked Stakeholder Reference: Proposed in context of discussions with Digital Governance Council (Cherlene Tay – Senior Manager, Standardization) Links https://dgc-cgn.org/standards/#standards OpenPolicy.me should focus on the following key DGSI (Digital Governance Standards Institute) standards to build strong credibility and demonstrate alignment with trusted digital governance frameworks: ✅ 1. DGSI 100 – Data Governance and Accountability Why: Ensures responsible data handling, user consent, and transparency in how legislative data and user feedback are stored and processed. Key Areas: Data classification, retention, lifecycle management, data subject rights. ✅ 2. DGSI 200 – Cybersecurity Risk Management Why: Covers risk assessments, vulnerability management, and protection of platform integrity, essential for a public civic tech platform. Key Areas: Threat modeling, penetration testing, access control, system monitoring. ✅ 3. DGSI 301 – Algorithmic Transparency and Fairness in AI Why: Critical if OpenPolicy.me is using NLP/AI to summarize bills or conduct sentiment analysis. Ensures decisions are explainable

OpenPolicy about 1 year ago

Completed

Google PlayStore Production

Run your closed test with at least 12 testers for 14 more days starting from the review date https://support.google.com/googleplay/android-developer/answer/14151465 App testing requirements for new personal developer accounts In November 2023, we changed the requirements for publishing new apps on Google Play to help developers to test their app, identify issues, get feedback and ensure that everything is ready before they launch. These changes require developers with personal accounts created after 13 November 2023 to meet specific testing requirements before they can make their app available on Google Play. This article provides an overview of the new requirements, a summary of the different testing tracks in Play Console and the steps that developers with personal accounts will need to take to make their apps available to users on Google Play. Introducing testing requirements for newly created personal accounts Testing is an integral part of the app development process. By running tests against your app consistently, you can verify your app's correctness, functional behaviour and usability before you release it publicly. This minimises the impact of any technical or user experience issues and helps you to release the best version of your app. Developers that regularly use Play Console's testing tools prior to publishing their apps are able to provide higher quality experiences that can lead to higher ratings and more success on Google Play. To help all developers to deliver high-quality apps, we're introducing new testing requirements. Developers with personal accounts created after 13 November 2023 will need to test their apps before those apps are eligible to be published for distribution on Google Play. Certain features in Play Console, such as Production (Test and release Production) and Pre-registration (Test and release Testing Pre-registration), will be disabled until developers meet these requirements. Overview of testing requirements If you have a newly created personal developer account, you must run a closed test for your app with a minimum of 12 testers who have been opted in for at least the last 14 days continuously. When you meet these criteria, you can apply for production access on the Dashboard in Play Console so that you can ultimately distribute your app on Google Play. When you apply, you must answer some questions to help us understand your app, its testing process and its production readiness. You can read about the different types of testing tracks and requirements for each in more detail below, and find more details about applying for production access. Understanding different testing tracks and their requirements Play Console provides different types of testing tracks so that you can gradually ramp up testing and improve your app to the point that it's ready to reach billions of users on Google Play. Internal testing: Before you've finished setting up your app, you can quickly distribute builds to a small group of your own trusted testers. This can help you to identify issues and get early feedback. Builds are normally available to testers within seconds of being added in Play Console. Interna

OpenPolicy about 1 year ago

Completed

Incorrect or Outdated Bill Associations

Title: Old bills shown under current identifiers (e.g., current C-2 showing COVID relief bill) Description: The current Bill C-2 is related to border security, but the app displays an outdated version. Possibly a session mismatch or outdated data source. Impact: High risk of misinformation. Category: Data Source Issue / Accuracy

OpenPolicy about 1 year ago

1