Privacy Policy

Who we are

Luminosity Event Planning at luminosityeventplanning.com is operated by Luminosity Development LLC. This policy describes information the app collects when you use it. It matches the product as it is built. It does not add a retention schedule or a certification the app does not state.

Questions about your information: support@luminositydevelopment.com.

Accounts

Creating an account stores your name, email address, and a password. The password is stored as a hash, not as the text you typed. The name you enter is also saved as your starting display name. On your profile you can change the display name, email, and password, and you can add an optional phone number in E.164 form. The app stores that number. It does not send a text message to verify it.

The account also stores whether your email is verified, when you last signed in, and whether you must reset your password before signing in. A connect code is stored so someone can open your connect link or QR code.

Profiles

A profile can include a display name, pronouns, a short bio, a longer bio, a Zoom name, a city, a region, a country, and profile photos. For a single event you can save pronouns and bios that apply only there. Presenter and team pages show the display name, pronouns, bio, and photo set for that event. Those pages do not show your email, phone, Zoom name, region, or country.

Your city can appear on your connect page and in a connection search result, together with your pronouns, when you have filled those in.

Aliases and display names

Aliases and display names are what other guests see. Public pages, the newsfeed, and connections show the display name on your profile. They do not show the email on your account, and they do not show a separate real name in its place. If a presenter or team link has no display name, the page uses a generic label rather than another name from the account.

The name you type at signup starts as that public display name. Change it on your profile if you do not want guests to see it. Your own account page shows your email to you. Organizers of an event you register for, apply to, or staff, and platform admins using the account tools, can see the name and email on the account. A vendor or sponsor page shows a contact email only when that listing is set to show contact details.

Event registration

Registering stores that you registered, the time you agreed to that event's rules, whether you want to volunteer, notes you write for the organizers, and your answers to questions the organizers added. If the event is adults only, the registration stores that you confirmed you are 18 or older. You can save sessions onto a personal schedule.

Organizers can open the roster for their event, including the name and email on the account, registration answers, and payment status. This app does not take card numbers. Organizers record payment themselves, and the app can store an amount, a method, a reference, and a note.

Applications

You can apply as a speaker, volunteer, sponsor, or vendor when that event has applications open. An application stores the display name you enter, a short message, and the details for that role. Those details can include a talk title, abstract, bio, and links; availability and interests; a company name, website, and tier; or a business name, website, and what you sell. Organizers of that event can read the application. The account email is shown to them and is not posted on the public event page.

Newsfeed posts and photos

A newsfeed post stores the text you write. You can attach up to four photos and optional alt text. You can mark a post anonymous. Guests then see "Anonymous" instead of your display name. The post is still tied to your account so organizers can remove it.

Uploaded photos are checked by their contents and re-encoded. That removes location data, including GPS coordinates stored in the file, and drops the original file name. Newsfeed photos and vendor and sponsor photos are stored on a private disk and shown through the site, not as a public file path. Profile photos, event logos, covers, and room images go through the same re-encoding, so location data is stripped there too.

Vendor and sponsor listings

A listing can include a display name, description, website, social links, a location note (such as a booth or table), photos, and an optional contact name, email, and phone. Contact details appear on the public listing only if the page is set to show them. The public name of the listing is the display name entered for that page.

Connections and messages

A connection is between two accounts. Nothing on that connection is shared until the other person accepts. After that, each person can turn schedule sharing and messages on or off for themselves. Connection messages store the text you send and whether they have been read.

You can search for someone by display name, or by a full email address, if they have left "Let people find me" on. A search result shows the display name, and pronouns and city when those are set. It does not show the email address or the phone number, and it does not reveal that an email is on file when the person cannot be found. Someone who already has your connect link can still send a request when search is off.

Event messages are separate threads between people on an event. A thread stores a subject, the message text, and when each participant last read it. People in the thread see display names.

Session feedback

When feedback is open, a registered guest can leave a score and a comment on a session and can mark that feedback anonymous. An anonymous comment is shown to organizers as Anonymous. The row is still stored with the account.

Cookies and sessions

The site uses a session cookie to keep you signed in, and a second cookie so forms can be checked as coming from this site. If you check "Remember this browser" on the sign-in form, an additional cookie keeps that sign-in. Session records can include an IP address, a browser identifier, and the session data. A session stays active for the idle time set on the server, which is two hours unless that setting is changed. Password-reset links expire after 60 minutes.

These cookies run the account and the forms. The app does not load an advertising or analytics script.

Email

Mail from the app is transactional: a message to verify your email address, and a message with a password-reset link. Those messages are sent through Azure Communication Services. The from name is Luminosity Event Planning. The app is built to run on Microsoft Azure. Local development can write mail to a log instead of sending it.

Who else sees information

• Other guests see what the product shows in public: display names and aliases, public profiles, posts, listings, and a schedule you have chosen to share with a connection.
• Organizers of an event see the registrations, applications, feedback, and roster tools for that event, including account emails where those screens show them.
• Platform admins can look up accounts and can unpublish or suspend an event.
• Azure Communication Services sends the transactional email described above. The app has no advertising and no feature that sells personal information.

What you can change

You can edit your profile, delete your own newsfeed posts and profile photos, and remove a connection. The app does not have a separate control that deletes an entire account. To ask about your information, email support@luminositydevelopment.com. This policy does not set a retention period. The app does not state one.

Changes

If this policy changes, the date at the top of this page changes with it. See also the Terms of use.