Frequently Asked Questions

You can upload structured research datasets in the following formats: CSV, Excel (.xlsx), JSON (.json/.jsonl), HDF5, TSV, and Parquet. Do not upload sensitive or regulated data (e.g., PHI, financial account numbers, precise geolocation). If your data is governed by regulatory requirements (e.g., subject to HIPAA, GDPR, or similar frameworks), please refer to Question 6 (“What changes in a self-hosted (institution-managed) deployment”) for more details. Self-hosting is currently the only option for using Asta with regulated data.

Key points

• Uploaded files remain associated with your account.
• We never share, sell, or redistribute your uploaded datasets.
• Uploaded datasets are automatically purged 7 days after upload from within our systems.
• If we detect sensitive or regulated data:
  
  • We will attempt to notify you at the email address you provided
  • We may remove the affected files to maintain compliance with our Terms of Use.
  • ⚠️ Note: You are solely responsible for ensuring your uploaded datasets complies with relevant laws and institutional policies. Ai2 is not liable for any misuse or unauthorized disclosure resulting from prohibited uploads.

• We do not share your uploaded datasets with third parties and we do not make them public.
• Limited, least-privilege access by Ai2 system administrators to your datasets may occur for safety, reliability, or legal reasons. For example, to investigate a bug or system issue.
• If you choose to opt in to allow your de-identified interactions with Asta (e.g., prompts, outputs, analysis steps) to be included in a public research dataset, we will use those interactions only for research purposes; i.e., to improve Asta.
• Regardless of your consent setting, your raw uploaded datasets are never redistributed or used for advertising or profiling.

• Raw uploaded datasets are never used for model training.
• Prompts and interactions (your questions, feedback, and system events) may be temporarily logged to improve reliability and Asta quality, but they are not used to train models without explicit opt-in consent.

Explorations are designed for short research sessions:

• An exploration is active for the first 24 hours. During that window you can ask follow-ups.
• After 24 hours, the exploration becomes read-only: you can view results, but you cannot continue the conversation in that exploration. To keep working, start a new exploration.
• If you uploaded multiple files to an exploration, deletion is at the exploration level (you can’t remove individual files from that exploration).

When You’re Signed In

• You can view and delete any of your explorations at any time in the hosted Asta interface.
• Deleting an exploration will remove:
  
  • All datasets uploaded into that exploration
  • All analyses, results, and outputs generated in that exploration
• Deletion is immediate and permanent. No recovery of deleted data is possible
• Uploaded datasets are automatically purged 7 days after upload if not deleted earlier. You can continue to access exploration summaries and results, but the source files themselves are deleted.

When You’re Using Asta Anonymously

• Recent explorations may be visible to you via browser cookies, allowing you to revisit and delete them while the cookie is intact.
• However, if you clear your cookies, you will lose access to those explorations (and the ability to delete them), as they are no longer associated with your browser session.
• To manage storage and maintain system hygiene:
  
  • Uploaded datasets are automatically purged 7 days after upload if not deleted earlier.
  • Anonymous explorations with no activity for 30 days will be deleted automatically.
  • Once deleted, these explorations cannot be recovered.
• Tip: To ensure you retain access to your data and can manage your explorations directly, we recommend signing in.

Self-hosting gives your organization full control over storage, retention, access policies, and compliance.

• You  decide where data lives, who can access it, how long it’s kept, and how it’s deleted at your institution. You are responsible for setting and enforcing these policies, including any applicable legal or compliance requirements.
• Self-hosting is the only recommended path for regulated data (e.g., PHI under HIPAA, controlled datasets under specific data-use agreements, GDPR residency needs).
• In self-hosted deployments, access to uploaded data is controlled entirely by your organization. Ai2 does not have visibility into datasets stored or processed in your environment.