Workspace access
API requests check the caller's access to organizations, brands, and prompts. Resources outside that access scope are treated as unavailable.
Trust and security
Understand the data behind your visibility.
Get Nodded brings brand information, tracked prompts, AI responses, and connected services together. Here is how access and credentials are handled, and what to consider when setting up your workspace.
Controls built into the platform.
Protected API keys
New API keys are shown when created. The platform stores a hash for verification rather than a recoverable copy of the original key.
Connection credentials
Google Search Console tokens and supported article-publishing credentials use encryption before storage. Connect only the accounts and publishing destinations your team needs.
Request limits
The API applies request limits, with additional limits on crawler ingestion and public report access. These controls help manage automated traffic and resource use.
What you bring into Get Nodded.
Brand and prompt data
Your website, brand details, competitors, and tracked questions give your workspace its context. Use prompts about your market and avoid including confidential customer details.
AI answers and sources
Tracked responses, brand mentions, and cited pages power visibility analysis. Prompt tracking involves external AI services that generate the answers you review.
Optional integrations
Search Console adds search performance data. Publishing connections let you send content to your chosen destination. Each connection has its own permissions and data flow.
Company logos shown in the dashboard: Logos provided by Logo.dev
Share reports deliberately.
Shareable reports let clients or colleagues view results without signing in. Treat a report link as access to that report: review its contents and share it only with the intended audience.
Review before publishing.
AI-generated drafts need editorial review. Check sources, product claims, and any personal information before sending an article or post to a connected publishing service.
Questions to cover in a security review.
What should we review before connecting an account?
Identify which data the integration reads or writes, who owns the connected account, and who should be able to use it. For publishing connections, agree on a review process before content goes live.
Where can we confirm compliance and procurement requirements?
Contact hello@getnodded.com to discuss required certifications, data residency, retention terms, or contractual commitments before purchasing. This page describes product controls and does not replace a review of the terms applicable to your deployment.
How do we report a security concern?
Email hello@getnodded.com with a description of the issue and the affected feature. Do not include passwords, API keys, or other customers' data in your message.
Bring your requirements into the conversation.
Discuss workspace access, connected accounts, report sharing, and your team's review process.