Privacy
Effective date
Who is responsible
Rolez is operated by MedA LLC.
For privacy and support questions, contact support@rolez.io.
Rolez is intended for customers worldwide.
Information you provide
When you use the contact form, we collect the details you enter, including your name if you provide it, email address, topic and message.
If you request an availability email, we record your email address, selected role, consent wording version and request time.
Email sign-in uses a one-time link. We store a hash of its token and maintain a revocable sign-in session.
Why the information is used
Contact information is used to handle your enquiry. Availability requests are used to tell you when the role you selected is available, if you choose that option. Sign-in information protects access to your account.
Security records help investigate misuse. They record event types and internal account references, rather than message content, email addresses or sign-in tokens.
Your choices
Availability consent is separate from making a purchase. You can withdraw availability requests through Manage availability requests after verifying your email through sign-in.
Withdrawal removes the selected local requests and prevents their pending signup messages from being dispatched. Any mailing-list removal that has not succeeded remains pending; the confirmation does not claim it is complete.
Approved retention schedule
This schedule has been approved but is not yet active. Automatic deletion under this schedule remains disabled.
The approved schedule keeps ordinary contact-form records for 730 days after submission. It does not use an unrecorded last-reply date. Enquiries linked to an order or setup request are retained for separate review.
The approved schedule removes ended sign-in links and sessions seven days after their first recorded end. Accounts with no protected purchase, company, entitlement or setup reference are eligible after 365 days without sign-in, provided no session or other linked record still requires them.
Availability requests are eligible for removal 365 days after the selected role has become available, subject to its recorded availability date. Withdrawal can remove a request earlier. No availability date is invented.
The approved security-event period is 365 days. Queued message records normally have an approved seven-day limit; active work and protected purchase/package notices are handled separately. A failed mailing-list withdrawal remains visible and pending.
Separate copies and service providers
Deleting a website record does not itself delete a copy already delivered to a support mailbox or held by a service provider. Provider copies and backups have their own retention schedules.
DigitalOcean provides our website and database hosting. Purelymail hosts our support mailbox. Resend is configured for service email, and Cloudflare Turnstile provides bot checks. These services process the information needed to perform those functions.
Purchase, package, company-summary and setup records are outside these ordinary cleanup rules.
Analytics
Visitor analytics are off under the launch plan. An analytics cookie banner is planned separately.