Trust, Security & Privacy
This page is maintained by the GRANTED Atlas project team to answer common questions about how the site works, what data it stores, and the controls in place. It describes current app-visible practices and is not an independent certification or audit.
What this site is
GRANTED Atlas is an analytic workspace for the NSF GRANTED portfolio: a public catalog of awards, a Lessons Bank of community-submitted notes, and an AI assistant that helps explore connections between awards.
The award catalog is built from publicly available NSF information. Lessons are contributed by approved members of the community.
Accounts and access
- Accounts are created with email and password or with Google sign-in.
- New accounts start in a pending state. An admin must approve a member before they can submit lessons.
- Administrative actions (approving members, editing or deleting any lesson) are limited to accounts with the admin role.
- Roles are stored in a dedicated table and enforced server-side; they cannot be changed from the browser.
Data we store
- Profile: the display name and organization you choose to share, plus the email used to sign in.
- Lessons you submit: title, body, optional source link, NSF award number, topics, tags, and the name/organization you attach as the submitter.
- AI usage: the awards you select in the Ideate tool are sent to a language model to generate connection summaries. Prompts are not used to train third-party models.
We do not collect payment information and the site does not sell user data.
Who can see what
- The award catalog and the Lessons Bank listing are visible to everyone.
- Submitter name, organization, and source link on a lesson are visible only to the lesson's author and to admins. Other readers see the lesson content without the submitter's identifying fields.
- Profile display name and organization are visible to other signed-in users by design, because members publish them as their identity in the community.
- Account roles are visible only to the user themselves and to admins.
Security controls in the app
- Database access is governed by row-level security. Policies scope reads and writes to the signed-in user or to admins, and are evaluated on every request.
- Authentication is handled by our backend provider; passwords are never stored by the application directly.
- Traffic between your browser and the site is served over HTTPS.
- Service credentials (such as backend service keys and AI provider keys) are stored as server-side secrets and are never shipped to the browser.
Deletion and corrections
- You can delete a lesson you authored from the Lessons Bank.
- To delete your account, update your profile, or request removal of a specific lesson, contact the project team using the channel below.
Third parties used to operate the site
- Lovable Cloud — hosting, authentication, database, and storage.
- Google — optional social sign-in.
- Lovable AI Gateway — language model calls used by the Ideate tool.
These providers process data only as needed to deliver the features above.
Reporting a security concern
If you believe you have found a security issue, please contact the project team before disclosing it publicly so we can investigate and fix it. The fastest channel is the project's primary maintainer; the GRANTED Atlas team will acknowledge reports and follow up with next steps.
Updates to this page
This page reflects current practices and may change as the site evolves. Significant changes will be noted here. For questions about a specific topic not covered above, please reach out to the project team.