Ratings and reviews

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.

Hey hanjuu, thanks for the honest feedback. Really appreciate it. To give some context on the spreadsheet interactions - OrcaSheets isn't a traditional spreadsheet, it's a columnar analytics engine. The data you import stays immutable by design, and any transformations happen at the column level through queries rather than manual cell edits. So things like cell deletion or in-cell functions aren't missing by accident, they're outside the scope because the focus is analytics, not data editing. That said, the UX feedback is completely valid. We're actively working on making the experience more intuitive so the analytics-first approach is clear from the get-go. And yes, opening a CSV, getting quick insights before jumping into a database or SQL client, that's exactly the sweet spot we're building for. Thanks for the support, more good stuff coming soon.

Hi Eugenia, thank you for flagging this. A couple of hours staring at a spinning icon is painful, and we're sorry you had to deal with that. Good news though: we've pushed a fix for .xlsx handling that's already live, so this should be much smoother now. If you'd be open to sharing the file with us at [email protected], we'd love to help you get it working right away. Thanks for not giving up on us just yet! :)

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 :)

Hey Christian, fair callout, let us clarify. Your data never leaves your machine. All processing happens locally. The cloud API connection on startup is only for authentication and license validation, not for touching your data. Think of it like logging into an app, the app needs to know it's you, but your files stay right where they are. We understand the concern around the sign-in requirement, but that's a security measure by design. It keeps your license and preferences secure, with zero data piggybacking happening in the background. Don't take our word for it though. Turn off your internet after login and try it for yourself. So yes, very much local. Promise. 🤝

Hey kyo kou! Thank you so much for the kind words, really glad we're able to impress you. We'd love to help figure out what's going on with the add button. Would you be up for a quick chat? We can reach out over email if that works for you.

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.

Hey, thanks for flagging this and sorry about the rough start. We just pushed a new build that should fix this. Can you update and give it another shot? If it’s still acting up, drop us a line at [email protected] with your crash log and we’ll sort it out.

OrcaSheets does not store database passwords in plain text, and the app does not reveal saved passwords back to the user. After you save credentials, the password is not viewable again. If you’re referring to the downloaded connection template, any password shown there is only indicative / a placeholder (not your actual password). Your real password stays with you, and once saved in OrcaSheets it’s stored encrypted locally. Could you please share a screenshot (with any sensitive parts blurred if needed) and the exact steps where you noticed the password shown in plain text? That will help us investigate and resolve it promptly. For clarity: credentials stored locally are encrypted using a device-level key.

Music to our ears! That's the whole point. If there's anything you'd like to see us do better, we're always listening.