Skip to main content

​
Frequently Asked Questions

​
Scoring

Scores are based on observable signals from your product’s public presence, documentation, and UX. They provide a strong directional assessment but may not capture internal capabilities that aren’t externally visible. Connecting integrations (GitHub, Linear) adds ground-truth operational data for more accurate scoring.
Yes. Enter any public URL and Dacard.ai will assess it. This is a common use case for benchmarking against competitors. Competitor scores won’t have integration data, so they’re based solely on public signals.
We recommend re-scoring after major product releases or quarterly at minimum. Score history is preserved automatically so you can track your trajectory over time.
Scores reflect the current state of your product’s public signals. Changes in your website, documentation, pricing page, or observable features will affect scores. The AI evaluator also improves over time, which may cause minor scoring adjustments.
Score your product’s main landing page or marketing site. This gives the broadest view of your product positioning, features, and AI integration. You can also score specific feature pages for dimension-level analysis.

​
DAC Copilot

DAC draws on established product management frameworks and thought leadership. Its recommendations are directionally strong but should be validated against your specific context. Always verify before making critical decisions.
DAC maintains conversation history within a session. If you close the panel and reopen it on the same page, the conversation continues. Navigating to a different product resets the conversation context.
DAC only accesses the scoring data for the product you’re currently viewing. It does not access your code, internal documents, or data from connected integrations. It uses the scoring result and framework knowledge to generate recommendations.

​
Account & Team

Organizations are created automatically based on email domain. Users with the same email domain (e.g., @acme.com) are grouped into the same organization.
Team members can sign up directly and will be automatically added to your organization based on email domain. Admins can manage roles from Settings > Organization.
Dacard.ai uses hierarchical roles: Member, Lead, Executive, and Admin. Higher roles inherit all permissions from lower roles. Roles are assigned during onboarding based on job title and can be changed by admins. See Roles & Permissions for the full matrix.
Currently, each user belongs to one organization based on their email domain. Multi-org support is on the roadmap.

​
Integrations

Integrations access operational metrics only: PR velocity, cycle times, review patterns, issue throughput. They do not access code content, message content, or personal data.
Connected sources sync daily via automated jobs. You can also trigger a manual sync at any time from the Sources page.
Yes. Go to Settings > Integrations and click Disconnect. This removes all synced data from that source.

​
Privacy & Security

Your scoring data is private to your organization by default. Shared result links (/r/) are public, but the URL is unguessable, so only people you share it with can view it.
Scoring data is stored in Turso (SQLite edge database). Authentication is handled by Clerk. Payment processing by Stripe. All connections are encrypted in transit.
Yes. Contact support to request full data deletion. You can also delete individual products and scores from the dashboard.