Alpha Participation Agreement
Version: 2026-11. Effective date: November 13, 2026.
1. About this agreement
1.1 Parties. This Alpha Participation Agreement (“Agreement”) is between you and Synapdeck, Inc., a Delaware corporation (“Synapdeck”, “we”, “us”). It covers your participation in the private alpha of the Synapdeck service (the “Alpha”).
1.2 How it fits with our other terms. Our Terms of Service and Privacy Policy still apply to you during the Alpha. This Agreement adds terms specific to the Alpha. If this Agreement and the Terms of Service conflict, this Agreement controls for anything about the Alpha. §7.4 also amends our Privacy Policy for Alpha participants, as it describes.
1.3 Acceptance. You accept this Agreement by checking the box when you first sign in to the Alpha. We record the date you accepted and the version you accepted. If you do not agree, do not use the Alpha.
1.4 Changes. We may update this Agreement during the Alpha. We will tell you about material changes by email or in the app at least 30 days before they take effect. Continuing to use the Alpha after a change takes effect means you accept the updated Agreement. If you do not agree to a change, stop using the Alpha. You can also delete your account as described in §9.2.
2. Alpha access
2.1 Invitation only. The Alpha is open only to people we invite. Your invitation and account are personal to you. You may not sell, transfer or share them, or let anyone else use your account. If we give you invitation codes to pass on, you may share those as we describe when we give them.
2.2 Eligibility. You must be at least 18 years old to join the Alpha. You must also be able to form a binding contract where you live.
2.3 No fees. The Alpha is free. We will not charge you for using it. Some features may have usage limits, such as monthly AI credits, and we may change those limits during the Alpha.
2.4 No promise about future pricing. Taking part in the Alpha does not entitle you to free or discounted access after the Alpha ends, or to any particular plan, price or feature. If we offer alpha testers a benefit at launch, we will describe it and its conditions in writing at that time.
3. What “alpha” means
3.1 Unfinished software. The Alpha is pre-release software. It will have bugs, and some features will be incomplete. You understand that:
- features may change, move or be removed without notice, including features you rely on;
- the service may be slow or unavailable, including for planned maintenance with little warning;
- review scheduling, card rendering, imports and other results may be wrong, and we may correct them later, which can change your review history or due dates;
- collaboration and sync features may lose or duplicate recent edits; and
- we may reset parts of your account, such as settings or scheduling data, to fix a problem, as described in §4.
3.2 Not for critical use. Do not use the Alpha as your only copy of material you cannot afford to lose, or for study where a scheduling error would cause you serious harm, such as the last weeks before a licensing exam. Keep your own copies of important material.
3.3 No support commitment. We will try to respond to bug reports and questions, but we do not promise any response time or fix.
4. Your content
4.1 You keep ownership. Section 3 of the Terms of Service applies to the decks, notes, media and other content you put into the Alpha. You keep ownership of it, and the license you give us is the same one described there.
4.2 Export. You can export your content using our standard data-export tools. Exports are intended to be complete, but the export feature is also alpha software: bugs may cause an export to fail or produce incomplete or corrupted files. Check important exports and keep independent copies of material you cannot afford to lose. Your data-access rights under our Privacy Policy and applicable law remain unaffected.
4.3 You may lose data. Content you put into the Alpha may be lost, corrupted or deleted, in part or in full, at any time. This includes decks, notes, media, review history and scheduling data. A serious failure may require us to restore the whole Alpha database to an earlier state or reset it to empty, and may leave us unable to give advance notice. We cannot promise to restore lost content. Keep independent copies of important material. Section 10 governs our liability for data loss.
4.4 Planned resets. If we plan a reset in advance, for example because of a change to how content is stored that cannot be migrated, we will try to email you at least 14 days beforehand so you can export your content. If we can’t give that notice, or a reset happens because of a bug, outage or emergency, we will tell you once we reasonably can.
4.5 Backups. We may keep backups, but during the Alpha we do not promise that any backup exists or that we can restore any particular content from one.
5. Feedback
5.1 What counts. “Feedback” means suggestions, ideas, bug reports, survey answers and comments you give us about the service, through any channel. It does not include your study content.
5.2 Our use of feedback. You give us a perpetual, irrevocable, worldwide, royalty-free license to use, change and build on your Feedback for any purpose, without paying you or crediting you. We do not have to use any Feedback.
5.3 Quoting you. We will not publish your name or a quote from you, for example in a testimonial, without your separate permission.
5.4 Security testing and reporting. During your invited participation in the Alpha, we authorize good-faith security testing of the Synapdeck-operated Alpha application, APIs and MCP service, subject to these conditions:
- Use accounts you control and data you own or have created for testing.
- Use only the steps reasonably necessary to establish and report a vulnerability. Stop testing that vulnerability once you have established it.
- Do not intentionally access, change or delete other people’s data. If you unexpectedly encounter another person’s data, credentials or other sensitive information, stop the affected testing and report it privately without further exploration.
- Take reasonable care to avoid excessive resource consumption, service disruption and harm to others. Stop the affected activity if you become aware that it is causing those problems.
- Obtain our written permission before load-testing, stress-testing, social engineering or testing outside this scope. This authorization does not extend to third-party systems or services.
Report vulnerabilities privately to security@synapdeck.com, including enough information for us to investigate.
Research conducted in good faith and with reasonable care under this section is authorized notwithstanding Section 4 of the Terms of Service and §8 of this Agreement. We will not pursue legal action, remove you from the Alpha or seek reimbursement merely because you conduct compliant research or publish a disclosure permitted by §6.4. This protection does not cover negligence or willful misconduct. Encountering an unexpected failure during otherwise compliant testing does not, by itself, establish negligence.
We may ask you to pause or stop testing. Authorization for further testing ends when we do so, when your participation ends or when the Alpha ends. This does not withdraw protection for earlier compliant research or change your disclosure rights under §6.4.
6. Talking about the Alpha
6.1 Talk freely. You may tell anyone that you are in the Alpha, post screenshots, describe what you see, and praise or criticize Synapdeck publicly. If you post about a bug, we’d appreciate it if you told us too, but you don’t have to. Security vulnerabilities are subject to §6.4.
6.2 Other testers’ information. Other testers may share decks, notes or messages with you, or post them in Alpha community spaces. Don’t republish another tester’s content or personal information outside the Alpha without their permission, unless they have made it public themselves or its license allows it.
6.3 Things we mark confidential. Occasionally we may show you something and clearly mark it as confidential, such as an unannounced feature. Please don’t share anything we’ve marked that way until we make that information public, or until 12 months after we disclose it to you, whichever comes first. This does not cover information that is already public through no fault of yours, that you knew before we told you, or that you must disclose by law. Section 6.4 governs permitted security disclosures.
6.4 Coordinated security disclosure. Report vulnerabilities privately under §5.4 before publishing their details. You may publish details once the fix is fully deployed or 90 calendar days after your initial private report, whichever comes first. You and we may agree in writing on an earlier or later publication date. We will work with you to coordinate publication.
Public disclosures must exclude other people’s personal information and content, live credentials and other sensitive information obtained during testing. Section 6.3 does not prevent disclosure permitted by this section. These disclosure rights and conditions continue after your participation or the Alpha ends.
7. Data, analytics and AI features
7.1 Analytics and diagnostics. We collect the product analytics described in Section 2 of our Privacy Policy, and you can turn them off in Settings → Privacy as described there. We also collect error reports and service logs so we can find and fix bugs and protect the service. AI usage logs record metadata such as message counts, context length, tool names, call counts and statuses, without tool-call arguments or results. We use this metadata internally to evaluate tool-use behavior and improve instructions. Turning product analytics off does not stop these operational logs. We will not turn on session recording or other extra diagnostics for your account unless you opt in separately.
7.2 AI features. Features such as the assistant, AI deck generation and search send prompts and relevant content to third-party AI model or embedding providers. When you create or edit content, it is sent to our embedding provider for indexing. Search queries are sent when you run a search. Our providers are Google Cloud and Anthropic, which process this information on our behalf under our business agreements and the data-processing safeguards described in our Privacy Policy. We do not authorize these providers to use your content to train their models.
We store embeddings for search and delete them when their source content is deleted. AI usage and diagnostic logs follow the retention rules for other service logs in our Privacy Policy. Provider retention is governed separately by our agreements with those providers.
We do not currently use your content to train or fine-tune AI models. Before introducing such use, we will describe it in an updated Privacy Policy, provide the required advance notice and obtain any consent required by applicable law. AI output may be wrong, so check it before you rely on it.
7.3 Contacting you. We may email you about your participation in the Alpha, for example with Alpha release notes, surveys or requests for a feedback session. You can stop these optional participation emails at any time. Joining the Alpha does not subscribe you to marketing or promotional emails, which require your separate explicit consent. We will still send essential messages about your account, security, data resets and changes to this Agreement.
7.4 Staff access to your content. During the Alpha, a small number of our staff may look at your account and content, including private decks and notes, to fix bugs, to understand how features are being used, and to decide what to build. We keep what they see inside Synapdeck, and we won’t publish or quote your content without your permission (§5.3). This section amends Sections 3 and 4 of our Privacy Policy for you while you take part in the Alpha: in addition to the product analytics and debugging access described there, our staff may review your account and content as described here.
8. Acceptable use during the Alpha
Section 4 of the Terms of Service applies, subject to the security-testing authorization in §5.4.
You may use AI agents, scripts, browser automation and other tools to perform actions you are otherwise permitted to perform. Automated use is subject to the same account permissions, usage limits and other restrictions as manual use.
If we consider your automated use of the service abusive, we may require you to stop the affected activity, including conduct not expressly prohibited below. We will notify you of the activity you must stop, and you must comply promptly. You may resume it only with our permission or under conditions we specify. This does not limit our ability to suspend or end access immediately under §9.3.
During the Alpha, you agree not to:
- load-test or stress-test the service without our written permission;
- knowingly or recklessly create excessive load or disrupt the service, or continue an automated workload after you become aware it is causing those problems or we ask you to stop;
- attempt to access other users’ data or bypass usage limits, credit metering, access controls or sandboxing, except for the limited security testing authorized by §5.4; or
- use the Alpha to run a paid or commercial service for other people.
9. Term and termination
9.1 Term. This Agreement starts when you accept it and lasts until the Alpha ends, your account is deleted or we end your participation, whichever happens first, subject to the provisions that survive under §9.5. Stopping use by itself does not end this Agreement or delete your account.
9.2 Stopping use and deleting your account. You can stop using the Alpha at any time. Stopping use does not delete your account or content. You can export your data or request account deletion using our standard account tools, as described in our Privacy Policy.
9.3 Suspension and removal. We may suspend or end your access to the Alpha at any time, with or without notice, including where we consider your conduct abusive, harmful, disruptive or otherwise unsuitable for the Alpha, subject to the protection for compliant security research and disclosure in §5.4. This does not affect requests concerning your personal data under our Privacy Policy and applicable law.
9.4 End of the Alpha and transition. We may end the Alpha or transition it to a beta or public release. This may involve changes to features, account settings or data formats, and may require migration or resets as described in §4. We will try to tell you about disruptive changes in advance; where urgent action is necessary, we will tell you as soon as reasonably practicable afterward. Sections 4 and 10 also apply to migration and reset work undertaken as part of this transition, including work completed after the Alpha ends. Your subsequent use of the beta or public service is governed by the Terms of Service and any additional terms you accept. This section does not change the notice requirements for material changes to this Agreement, the Terms of Service or our Privacy Policy.
9.5 What survives. §5 (Feedback, including the protection for earlier compliant security research under §5.4), §§6.2–6.4, §9.4, §10 and any other terms that by their nature should survive will continue after this Agreement ends. Sections 4 and 10 continue to apply to transition work as described in §9.4. The authorization to conduct new security testing ends as described in §5.4.
10. Disclaimers, liability and general terms
10.1 No warranty. THE ALPHA IS PROVIDED “AS IS” AND “AS AVAILABLE”, WITH ALL FAULTS. To the extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, non-infringement, and any warranty that the Alpha will be accurate, available, or free of errors or data loss.
10.2 Limit of liability. Section 7 of the Terms of Service applies to the Alpha, including its exclusion of indirect damages and its provisions concerning losses caused by your negligence or willful misconduct. To the extent the law allows, our total aggregate liability to you for all claims arising from or related to the Alpha is limited to $100, including claims for lost, corrupted or deleted content. This Alpha-specific cap replaces the general liability cap in Section 7 of the Terms of Service for those claims. Nothing in this Agreement limits liability that cannot be limited by law.
10.3 Your local law. Some places do not allow some of these disclaimers or limits. Where that is true, they apply only as far as your local law allows, and you keep any rights that law gives you.
10.4 Disputes. Section 8 of the Terms of Service (Delaware law, Delaware courts, the 30-day informal resolution and mediation steps, and the one-year limitation period) applies to this Agreement.
10.5 Everything else. This Agreement, the Terms of Service and the Privacy Policy are the whole agreement about the Alpha. Section 10 of the Terms of Service (severability, no waiver, assignment and force majeure) applies to this Agreement too.
10.6 Contact. Questions about the Alpha: alpha@synapdeck.com. Legal notices: legal@synapdeck.com.