Developers can see, copy, correct and delete their information by writing to us; the people on camera should ask the developer first and can always write to us; the rights of U.S. state, EEA and UK residents explained.
Developers and visitors. You can revoke keys and delete webhook endpoints in the dashboard, and sign out at any time. To see or get a copy of your information, correct it, or delete your account, write to legal@orgasm.dev from the address you sign in with.
The people on camera. We process your session for the developer whose product you used, so please make requests about it to that developer, who can delete a session at once; we will help it respond. If you cannot reach the developer, or believe orgasm.dev was used on you without your consent, write to legal@orgasm.dev. We will act on what we can verify, which may include ending sessions and revoking the developer’s access. We hold no name or contact details for you, so we may need details of the session, such as when it ran and in which product, to find it.
U.S. state privacy rights. Depending on where you live, for example in California, Colorado, Connecticut, Oregon, Texas, Virginia or Washington, you may have the right to know what personal information we hold about you and how we use and disclose it; to get a copy of it; to correct it; to delete it; to opt out of its sale, of sharing for cross-context behavioural advertising and of targeted advertising, none of which we do; to limit the use of sensitive personal information, which we use only to provide the Service; and not to be treated differently for using these rights. You may use an authorised agent. We verify a request through the email address on the account or, for the people on camera, with the developer, and answer within 45 days, which the law allows us to extend once. If we decline a request, you can appeal by replying to our answer; if the appeal is refused, you can contact your state’s attorney general.
California. In the past 12 months we have collected these categories of personal information about developers and visitors: identifiers (an email address, an account identifier, an IP address); account credentials (API keys, kept only as hashes); professional information (what you are building, the company your address belongs to and your role in it); commercial information (your company’s credit purchases and charges); internet or network activity (requests and logs); and the contents of messages sent to us. The sources are you, your sign-in provider and your use of the Service; the purposes are those in section 5; the recipients are those in section 11. For the people on camera, we act as the developer’s service provider. We have not sold personal information or shared it for cross-context behavioural advertising, and we have no actual knowledge of doing so for anyone under 16.
The EEA and the UK. If the GDPR or the UK GDPR applies to you, we rely on performing our contract with you for developer accounts; on our legitimate interests in running, securing and improving the Service and in preventing its misuse, for logs and security; and on our legal obligations where the law requires us to act. For the people on camera, the developer’s legal basis applies, which for this kind of information is normally the person’s explicit consent, and the developer’s notice must also cover the aggregated statistics in section 10. You have the rights of access, rectification, erasure, restriction, objection and portability, and you may withdraw consent at any time. You may also complain to your data protection supervisory authority.