Yes. The aggregation runs against the database storage Pirate Forms uses regardless of tier. The free plugin captures everything the dashboard needs (name, email, subject, message, submitted date, source URL); Pro fields surface as additional group-by options when present.

Yes when SleekView's optional status column is enabled. Statuses (new, replied, spam) store as metadata alongside Pirate Forms rows, so the dashboard groups by them. If you do not use that feature, the status Donut simply remains empty and the other cards still work.

No. SleekView Charts reads in paged chunks and uses indexed columns where possible. Even tens of thousands of submissions aggregate quickly because the query runs against the same data path the table view uses.

Yes. Pirate Forms stores the source URL with each submission, so SleekView Charts groups by it. The Bar card ranks pages by inquiry volume. Useful for sites that embed the same contact form on /contact, /about, /speaking, and elsewhere.

No. SleekView Charts is read-only over stored entries. Pirate Forms' email notifications fire on submission as before. The submission flow does not route through SleekView, so disabling the charts dashboard leaves email behavior unchanged.

You can count submissions with attachments (Count of rows with a non-empty upload field), but the files themselves stay in the table view. Useful for application-style forms to read attachment rate over time.

Yes. SleekView Charts reads the standard Pirate Forms storage tables and any added metadata persists in WP postmeta or its own table. Plugin updates do not affect either layer, so dashboards keep working.

If Pirate Forms records the WordPress user ID on submissions from logged-in users, yes. A filter chip splits anonymous from logged-in. Useful for membership sites that mix open and gated contact paths.