How can we help?

Tablivo helps you inspect local data exports on a Mac: browse tables, filter and sort records, run supported read queries, inspect values and export useful results. It is not a full spreadsheet editor, database server, backup service or data recovery tool.

Tablivo is currently in development. A release date and App Store link will be added to the product page when available. Screenshots and features may change before release.

Tablivo is being developed for macOS. There is currently no announced iPhone, iPad, Windows or web version. Check the eventual App Store listing for the final macOS and hardware requirements.

No. Browse lets you explore tables, search, filter, sort and choose columns without writing a query. SQL is optional for more specific questions. Analyze provides supported summaries of the Browse scope.

No. Open a complete local file export. Tablivo does not connect to a remote database server, restore a server backup or continuously synchronize a source. To inspect updated information, create a fresh export and reopen it.

Tablivo processes the files you open and query results locally; it does not automatically upload them to BaskayaLabs or an external processing service. Saving an export to a cloud-synced folder, copying with synchronized clipboard features, or emailing a file can share data through services you choose. See the Privacy Policy.

BaskayaLabs does not use opened file contents for advertising, tracking, profiling or training AI models. The app has no advertising or third-party analytics SDKs. Tablivo does process values locally to provide the features you request.

Not through normal file inspection in the app. We can see information you voluntarily send to support, such as text, screenshots or attachments. Please redact sensitive details and use fictional sample data.

Inspection uses private working data and is designed not to edit your original file. Export creates a separate output at the location you choose. Keep backups, and use standalone exports rather than files being actively written by another application.

File inspection and analysis run locally and do not require a database server. App Store purchase, restoration or subscription verification may require internet access to Apple. Local processing does not mean every purchase or access check can always be completed offline.

Closing releases the current session and the app attempts to clean up temporary working data. An unexpected termination can leave temporary files until cleanup. Your source file, saved CSV exports and clipboard or cloud copies are not deleted by closing a session.

No BaskayaLabs account system is included. App Store purchases use your Apple Account through Apple. Do not send your Apple Account password or payment details to support.

Check that it is a supported, complete export and has finished downloading. Renaming an extension does not convert a file. Unsupported variants, encrypted content, incomplete data or workload limits can prevent import. Copy the exact error and file type when requesting help.

Supported readers include SQLite, CSV/TSV, JSON and JSON Lines, supported SQL exports, XML, Excel and OpenDocument spreadsheets, Parquet, Avro, DBF, DIF and GeoJSON, plus supported compressed text exports. This does not mean every variant or feature is supported. Check the in-app Supported formats help for your build.

Encrypted databases and protected document variants that require decryption are unsupported. If you are authorized to access the information, create a supported unencrypted export using the source application and handle that export securely.

It may depend on live WAL or journal files, use encryption, or be an unsupported file with a database-like extension. Close writers and create a complete standalone export using the original application. Do not delete database sidecar files just to force the file to open.

Choose a file that is fully available locally and that macOS allows the app to read. Download cloud placeholders first. Provider availability and sync state may affect opening or saving. For troubleshooting, use a local copy in a folder you control.

Select an actual supported file rather than a folder, and check that it has finished downloading. Cancel and reopen the file picker if needed. If a selected local file still cannot be opened, report the macOS version, file extension and visible state to support.

Only supported compound text export formats can be decompressed for inspection. This is not a general archive extractor. Archives such as .tar.gz, nested compressed files and physical database backups such as .bak, .mdf or .ibd are not supported. Export the relevant tables to a supported format instead.

Some readers preserve stored values as text to avoid losing leading zeros or numeric precision. Spreadsheet dates may remain serial values. Tablivo does not reproduce every formatting rule of the source application. Inspect type and source metadata before choosing a conversion.

No. Supported readers inspect stored values and available formula metadata. Cached results may be missing or out of date. Recalculate and save the workbook in its original application first if you need refreshed stored results. Macros and external worksheet automation are not run.

Some formats need row identifiers, source types or metadata to preserve context. A spreadsheet’s first row may remain data rather than becoming column names. Use the in-app format help to understand generated columns and metadata tables; do not assume they came directly from your source rows.

NULL represents a missing database value; empty text is a present value with no characters; zero is a numeric value. Their display and export can differ. Inspect a cell when the distinction matters, and keep the source file because CSV readers may not preserve it.

Queries must be supported read-only SQLite statements, even when the original export came from another database system. Unsupported SQL, resource limits or an incomplete query can produce an error. Read the status message and use a smaller, more focused query. A preview is not necessarily the complete result.

Use the available Stop control; Escape can stop a running query. Workload checks may also stop processing. Cancellation and duration depend on the operation. Check the current status before assuming a new result replaced the previous one.

A failed or cancelled query keeps the previous successful result rather than replacing it with incomplete output. Check the result status and query context before copying or exporting. Editing query text alone does not run it.

Analyze summarizes the current Browse scope, including supported missing, distinct and duplicate-value checks, numeric or date summaries and charts. It is not a guarantee that the whole original file or the current SQL result is being analyzed. Check the displayed scope and selected columns; ambiguous values may remain unconverted.

No. Readers and operations have format, row, column, memory, storage and time limits. Some CSV/TSV workloads offer an extended mode with your approval, but this does not increase every format’s limits. Use the limits shown by your build; a smaller focused export is often the clearest solution.

Check the selected export scope. Depending on the context, export can use the Browse matching scope or the last successful SQL results; an explicit SQL LIMIT or OFFSET still matters. Copy CSV is limited to the visible page or preview. Exporting a result is not the same as exporting an entire database.

Exact values preserves the exported text. Spreadsheet safe adds a leading apostrophe to formula-like text to help prevent a spreadsheet from treating it as a formula. That deliberately changes affected text, including some negative numbers stored as text. Neither mode controls every receiving spreadsheet’s automatic type conversion.

No. CSV is plain tabular text; it does not preserve workbook formatting, charts or executable formulas as a workbook. Binary values are represented by byte-count summaries rather than their binary contents. NULL and empty text may be interpreted alike by another reader. Keep your source file.

A saved CSV goes to the location you choose in the macOS save dialog. Check that the destination is writable, has enough free space and is available locally. Cloud provider interruptions may affect saving. Copying CSV places text on the clipboard rather than creating a file. Report the exact error if saving still fails.

Final pricing, subscription duration and any eligible trial will be shown in the App Store and purchase confirmation when available. We are not promising a launch price or trial here. Do not treat a development preview as evidence of a completed App Store purchase.

Use Restore purchases in an App Store build with the Apple Account used for the purchase. Check your internet connection, system date and subscription status. Pending, expired or unverified purchases may not provide access. If it persists, email the exact message and app version; never send account credentials.

Manage Apple-billed subscriptions in Apple subscription settings. Follow Apple’s cancellation instructions; uninstalling Tablivo does not cancel billing. Refund eligibility and requests are handled by Apple: refund instructions.

Cancellation concerns subscription access, not ownership of your data. Your original files and saved exports remain where you stored them. App features may require an active verified entitlement. Keep important exports and source files independently of the app.

Email BaskayaLabs@gmail.com with the Tablivo version, macOS version, file extension and approximate size, exact error, and steps to reproduce. Tell us what you expected and what happened. A minimal fictional sample or redacted screenshot is more useful than a large confidential dataset.

No. Start with the error message and steps. If a sample is useful, create a small fictional file with the same structure. Remove personal data, secrets and identifying metadata. We do not need passwords, payment details or a production database.

We cannot promise support for every file variant, successful recovery, or a fixed response time. We can investigate a clear report and explain known limitations. Tablivo is still in development, so a feature request or bug report is not a commitment to a release date.

Email the task you are trying to complete, your macOS version, relevant accessibility settings or file format, and what blocks you. Use a redacted screenshot or fictional example if helpful. We will use this information to assess the request; support for a future feature is not guaranteed.