BCINexus · Reference
Platform FAQ
Answers about the platform. Questions about the desktop app itself are in the BCILattice FAQ.
Data and privacy
- Does signing in upload my recordings?
- No. Data leaves your machine only when you publish, share to a team, or create a share link. Being signed in changes nothing on its own.
- Where is published data stored?
- On platform-managed cloud storage. On-premise and air-gapped deployment is available for institutions that cannot use it — see the enterprise section.
- Can I delete something I published?
- Not by deleting it silently. Once other people can cite it, changes go through corrections or retraction so citations keep resolving. Legal and privacy takedowns are handled separately.
- Is my work used to train AI models?
- Only where you have explicitly allowed it. It is a per-account setting, not an assumption.
Publishing
- Why was my publish refused?
- Something on the blocking list is missing — usually the title, modality, task type, a 30-character summary, a pipeline definition, or a co-author who has not accepted yet. The dialog names the exact check; the full list is in publish readiness.
- Do I need a paid plan to publish?
- No. Publishing and peer review are not gated by plan. Storage quotas and some export formats are.
- Can I publish without review?
- Submission enters the review path by default. That is the point of the platform — the public record is meant to have been looked at.
- What is the difference between a study version and a review version?
- A study version is a public snapshot. A review submission has its own version counter that increments each time you resubmit during review; the two are deliberately independent.
Review
- How long does review take?
- Each stage sets its own service-level window, commonly a week, and overdue reviews are swept and escalated to administrators. Total time depends on how many stages the pipeline has and how many rounds of changes are requested.
- Why can I not see all the reviewer comments?
- Reviewers deliberate internally and share what you need. Internal comments never reach your browser at all — the filtering happens server-side. See how review works.
- Who are my reviewers?
- On an open pipeline, named people. On a blind pipeline you see stable anonymous labels such as "Reviewer 2 — Technical Review", and the same label always means the same person.
- Changes were requested. Do I start over?
- No. Resubmitting re-enters the
samestage with a bumped version, and the reviewers already on it are notified. - Can I review my own work?
- No. The guard applies to administrators too — a conflict of interest is about identity, not authority.
- How do I become a reviewer?
- Apply at apply-reviewer. Applications are read by a human and answered by email, usually within a few days. The reviewer handbook covers what happens next.
- Do reviewers get credit?
- Yes. Completing a stage on work that publishes adds you to its contributor list, anonymised if the pipeline was blind, and counts toward your reviewer metrics and directory listing.
Accounts, teams, and billing
- I am out of desktop seats.
- Deactivate an old machine from account settings. Re-activating a machine you used before reuses its record instead of taking another seat.
- Does a team member need their own plan?
- Team membership governs shared content. Running the desktop app still needs a seat on their own account.
- What happens if I downgrade?
- Gated features switch off. Studies, published work, and local files are not deleted; content over the new quota becomes read-only.
- Can I sign in with ORCID?
- Yes, and it is worth doing if you publish — signing in with ORCID verifies the identifier on your profile, which then travels with your author byline.
Still stuck?
Email [email protected] with your account email, the study or submission identifier, and what you expected to happen.
Something missing or out of date? Email support or request a doc page. Include the page name and what you expected to find.