Usage Policy

1. Use it for the work

• Invite only people who need access, give them the narrowest role that does the job, and remove them when they no longer need it.
• Put people’s information into Spell only when you have a right to, and only what the work requires.
• Send client-facing comments, approvals, signature requests and emails only to people who expect them.
• Connect only integrations and accounts you are authorized to connect.

2. Not allowed

Do not use Spell — including its files, comments, emails, Sign, the careers site or Astra — to:

• break the law, defraud, impersonate anyone, or forge or misuse signatures;
• harass, threaten or abuse anyone, or promote violence or hatred against people for who they are;
• share sexual content involving minors, or intimate images of anyone without their consent;
• send spam or deceptive invitations, signature requests or job postings;
• infringe others’ intellectual property or publish other people’s private information;
• discriminate unlawfully in hiring, or make decisions about people based solely on Astra’s output;
• use Astra’s research to profile private individuals rather than businesses;
• store payment card numbers, government identity numbers or health records where Spell is not designed to hold them.

3. Security and fair use

• Keep your login to yourself and do not share accounts.
• Do not try to reach another studio’s instance, test Spell’s security without our written permission, or get around its limits.
• Do not upload malware, scrape the Service, or load it in ways that degrade it for others.
• Do not resell or give access to Spell to people outside your studio, other than your own clients and contractors.

4. Reporting a concern

Tell us at hello@letsjam.design about misuse, a security issue or content that infringes your rights. Include where you saw it, what happened and how to reach you. If you find a vulnerability, please give us a chance to fix it before you share it.

5. How we respond

We keep our response in proportion to the problem. Usually we will ask the studio to fix it first; if needed we may remove content, disable an integration or a shared link, restrict a user, or suspend an instance. We act immediately, and may tell you afterwards, when there is a security risk, a legal requirement or a risk of serious harm.

If you think we got it wrong, write to us and we will review it. Asking for a review does not restore access by itself.

6. Changes

We may update this policy as Spell and the law change. The effective date above shows the current version.