Valutazioni e recensioni

Thank you for sharing this so clearly, and we’re sorry for the frustration. A couple of things may have caused what you saw. If the chart started at 1907 instead of 1900, it is possible the earliest valid value in that column was being read as 1907 rather than 1900. For the columns not appearing in the chart builder, this usually happens when those fields are interpreted as text or categorical values instead of numeric ones, and the graph builder currently prioritizes numeric columns. We agree this should feel much more straightforward. We’re improving the chart prompting experience so the AI follows the data more accurately, and we’ve also enabled the AI SQL Editor for you so you can correct column types more easily where needed. That should help bring in fields that may currently be excluded from graphing. Thanks again for the honest feedback - the app should make exploration easier, not harder, and this is exactly the kind of issue we want to fix.

We're sorry this was frustrating. OrcaSheets does support scatter plots, but currently they need to be created through the chart selection flow by choosing the scatter plot visualization and then assigning the relevant columns. We agree that something this basic should not feel complicated, and we're actively improving the product so chart creation, including through chat, becomes much more straightforward.

Thank you for coming back to update your review, Perbinder - that means a lot to us. Really glad the resizing is working for you. If anything else comes up, we're always here.

Thank you for this feedback, and we completely hear you. A cluttered interface that limits how much data you can see defeats the whole purpose. We're working on UI configurability, and resizing for sidebars and drawers is something we're looking to implement in the next upcoming updates. We want OrcaSheets to flex to your workflow, not the other way around. We appreciate your patience while we get there, and we're glad the concept is resonating. Updates are coming.

Thank you, Archiee! Glad it's been helpful for your data analysis. We just launched our AI SQL Editor (beta) that lets you describe your analysis in plain English and writes the SQL for you if you want to take things up a notch. It's a premium feature, but we'd love to get it enabled for you to explore. Drop us a note at [email protected] and we'll set you up.

Hallo Marius, vielen Dank für den Hinweis. Wir haben kürzlich ein Update veröffentlicht, das genau dieses Problem beheben sollte. Wir würden Ihnen gerne helfen, das zu lösen. Schreiben Sie uns gerne eine E-Mail an [email protected], dann können wir einen kurzen Call vereinbaren und sicherstellen, dass alles reibungslos funktioniert. Hi Marius, thank you for flagging this. We recently rolled out an update that should have resolved this exact issue. We'd love to help you get this sorted out. Could you drop us an email at [email protected]? We'll jump on a quick call and make sure everything's working smoothly for you.

Hey Alex, we hear you. That crash was a real one, and we're sorry it was your first impression. We've since shipped v26.2.2 that fixes that exact bug. Would you mind updating and giving it another shot? We promise it gets better from here. Also, we couldn't find any crash events on our end for your session, so we'd love to understand what happened. If you could share the CSV (with dummy data is totally fine) or any details about the crash, that would help us make sure no one else hits the same wall. Drop us a line at [email protected]. We're all ears and, more importantly, all fixes.

Starting something new always comes with a little uncertainty, so it genuinely means a lot to hear that we made the transition easy. Big data without a single SQL query is exactly what we set out to build, and we're so glad it's working for you.

Hi Molly, thank you for taking the time to write this and for being direct about it. You've flagged real gaps and we'd rather hear this than not. The padding and the inconsistent sizing across split-screen configurations - these issues are on our radar and actively being worked on for an upcoming release. You're right that they shouldn't require a workaround. The keyboard shortcuts living inside a PDF is genuinely indefensible and we know it. That's changing too. Reviews like yours are exactly what keep us honest about the surface. We hope you'll give us another look when the next release lands.

Fair point, Tay, and we hear you. Resizing is something we're actively working to support in an upcoming update, so you'll have full control over how OrcaSheets fits into your workspace. Appreciate the patience while we get there!

Hi Guillermo, We're truly sorry about this. One of OrcaSheets' core principles is that we run compute on your full dataset locally, not a sampled subset. Unlike most LLM-based tools that work on partial data and risk hallucinating results, we process every single row. So hearing that your 70k-row file was reduced to 6k is deeply concerning to us. We've already reached out to you personally via email because we want to get to the bottom of this. We're treating it as a priority and will do everything we can to make sure your experience with OrcaSheets changes completely. Thank you for flagging this. Feedback like yours is how we get better.

We totally get the skepticism. Privacy policies deserve a close read, and we respect that you're doing yours. Quick clarification: that checkbox covers your OrcaSheets account credentials (the email and password you use to sign up). We need those to, you know, let you log in. They're stored securely and never shared with third parties. Your database credentials, API keys, connection passwords? We literally cannot see them. They're processed and stored locally on your machine. Not on our servers. Not anywhere near us. That's the whole point of being local-first. Same for your table data. It stays on your infrastructure unless you explicitly opt into a cloud feature. We don't sell your data, don't use data brokers, and have zero advertising cookies. Read the full privacy policy here: https://orcasheets.io/privacy/ If you have any specific concerns, reach out at [email protected]. We're an open book (about everything except your data, obviously).

Really appreciate you sharing this! And huge thanks for reaching out to support -- glad the team was able to jump on that fix quickly. You're right that we're still smoothing out some UI/UX edges, and that feedback is super helpful. But so glad the core data analysis and visualisations are landing well-- that's what we obsess over. Thanks for sticking with us :)

We’re sorry for the confusion. On Setapp, OrcaSheets is meant to have all features enabled, and the 30-day indicator is part of an auto-refresh login cycle rather than a restricted trial. The Settings screen is available through the gear icon on the right sidebar, though we agree this should be much more obvious. We’d appreciate it if you could share a screenshot of the Settings screen or confirm whether a referral ID is visible there on [email protected], so we can verify your Setapp activation and understand what felt locked or missing.

Hi SK, thank you for the feedback and we hear you. On the emails, we did introduce a product onboarding sequence to help new users discover features they might otherwise miss, like Recipes, and we understand that may have felt unexpected if you weren't anticipating it. That's on us to communicate better upfront. On the UX and onboarding experience, the feedback is fair and actively being worked on. If you'd like to share anything more specific, we're at [email protected] and we're listening.

Thank you for sharing this, Anudeep. This is exactly the kind of use case we were built for. Moving from cybersecurity to health tech means navigating some of the strictest data governance requirements out there, and we're genuinely glad we could remove that friction for you. Keeping your data on your machine shouldn't mean compromising on analytical capability, and it's great to hear that came through. We'll keep making sure OrcaSheets keeps up with wherever your work takes you!

Glad to hear it, Troy! Let us know how it goes.

Hey Brandon, thanks for the honest feedback! We hear you on the documentation front, and we've been working on it. You can check out our onboarding guide here: https://orcasheets.ai/docs/onboarding-guide/ for a quick start. As for the Snowflake connector, we've just shipped a production-ready version along with sample connection configs for most connectors to make testing a breeze. Give it another spin when you get a chance, and if you hit any snags, we're right here. We'd love to change that 'waste of time' to a 'worth my time' 😊

Hey Pelle, appreciate you raising this. The registration is purely to verify you're a legitimate user accessing the software. Setapp does share user emails with us, but they still need to be validated on our end to meet our security standards. We're actively working with Setapp's existing API to see if their identity verification is sufficient for our requirements, and if it is, we'll streamline this so the extra step goes away entirely. We'll update here once we have a resolution. The GitHub calls are specifically for hosting our latest binaries so everyone can download them, and for issue reporting through GitHub Issues. Nothing more happening there, just straightforward hosting and transparency around bug tracking. If you'd like a detailed walkthrough of every network request the app makes, reach out to us at [email protected]. We're happy to go through it with you.