Conversation
AngelCodes95
left a comment
AngelCodes95
left a comment
There was a problem hiding this comment.
regarding content, looks good and seems to cover a wide range. ** Not a lawyer **
| </FormSection> | ||
|
|
||
| <CheckboxField> | ||
| <CheckboxInput |
There was a problem hiding this comment.
Is it possible to make the required field message something other than "Please check this box if you want to proceed"? If not, then no worries.
| <Paragraph> | ||
| Events may be photographed and/or recorded. These materials may capture your name, | ||
| voice, image, or likeness. By attending, you grant permission for your image to be | ||
| used in photos, videos, and other media without compensation. If you prefer not to be |
There was a problem hiding this comment.
-used in photos, videos, and other media without compensation. If you prefer not to be
+used in photos, videos, and other media for marketing and promotional purposes. DEVx, reserves the right to distribute all content and materials captured or produced during the events.| Events may be photographed and/or recorded. These materials may capture your name, | ||
| voice, image, or likeness. By attending, you grant permission for your image to be | ||
| used in photos, videos, and other media without compensation. If you prefer not to be | ||
| photographed, please request an opt-out indicator at check-in. |
There was a problem hiding this comment.
There should be no opt-out. If people are disgruntled, then they can just not attend our events. This is more of a notice/disclaimer than it is asking for permission.
| <SectionTitle>Data Collection</SectionTitle> | ||
| <Paragraph> | ||
| By registering, you provide certain personal information for event coordination | ||
| purposes. You may optionally consent to receive additional communications. Your data |
There was a problem hiding this comment.
The data may be processed outside of the United States. We cannot necessarily guarantee that their data will be contained within the United States. Not sure if this is a worthwhile to keep. We partner with services like Luma and use AI providers that may be in the US or China, so we can't necessarily say we follow a strict data use policy if that's what's implied. We can control what we can control, but most of the data is in the public space (public as in public forum like X.com is a public forum). We don't operate in private; but when we do we may have to include a separate privacy policy.
| rel="noopener noreferrer" | ||
| > | ||
| Get Your Ticket | ||
| <Button variant="primary" size="default" onClick={() => setIsModalOpen(true)}> |
There was a problem hiding this comment.
I think instead of a modal, we should just include a sentence above saying "By checking in, you agree to the Event Terms". Make it clear it is present. Then they only need to press one button to agree.
| By submitting, I agree to these{" "} | ||
| <TermsLink href="/event-terms" target="_blank" rel="noopener noreferrer"> | ||
| terms |
There was a problem hiding this comment.
-By submitting, I agree to these{" "}
+By submitting, I agree to the [event terms and conditions](...)There was a problem hiding this comment.
I think we should not have the modal (remove it). My main concern is about the check-in friction. I want to remove the friction and instead go with a clean disclaimer on the page.
claudinethelobster
left a comment
claudinethelobster
left a comment
There was a problem hiding this comment.
Great work on this — clear structure and readable flow. I left a legal/content pass and recommend a few updates before merging:\n\n1) Minor policy consistency\n- Current text conflicts between "18+ or parental consent" and "under 18 must be accompanied by parent/guardian at all times".\n- Please choose one policy and make both sections match.\n\n2) Identify legal entity + contact\n- "DEVx" should be tied to a legal/organizer entity and a contact email/address for notices.\n\n3) Acceptance language\n- Add explicit enforceability text: "By checking this box and registering, you agree..." especially for waiver/release terms.\n\n4) Data Collection section needs more detail\n- Add what data is collected, retention, sharing/processors (e.g. registration/hosting platforms), privacy contact, and a privacy policy link.\n\n5) Add standard legal boilerplate\n- Effective date\n- Severability\n- Entire agreement\n- Terms updates/modification language\n\n6) Liability carve-outs\n- Current release is broad; include counsel-approved carve-outs for non-waivable rights (e.g. gross negligence/willful misconduct) where applicable.\n\n7) Photo opt-out process clarity\n- Keep opt-out language, but specify who to ask and note best-effort limitations for crowd shots.\n\n8) Cancellation/changes policy clarity\n- Add explicit policy language around event changes/cancellation and attendee-incurred costs.\n\nIf helpful, I can draft a revised v2 ToS text directly in this PR.
|
Formatting fix (reposting cleanly): Great work on this — clear structure and readable flow. I recommend a few updates before merging:
If helpful, I can draft a revised v2 ToS text directly in this PR. |
4 participants
No description provided.