How Staylink handles your data

This Privacy Policy explains how Staylink handles data when you use the platform to create, manage, and share guide pages.

If you have questions about this policy or want to make a privacy request, contact hello@staylink.io.

We collect the access code you use to log in or claim a guide, any optional name you add to your account, and the session identifiers used to keep you signed in.

We also collect the content you create on the platform, including guide page text, uploaded images, staylink names, and optional property addresses.

If you contact us for support or a deletion request, we will also process the information you include in that communication.

We use your data to authenticate your account, maintain your session, let you create and edit guide pages, publish shared guide content, store uploaded images, and provide account or support help.

We may also use your data where needed to comply with legal obligations or to respond to account and content requests you send us.

Guide pages shared through a public link may be visible to anyone who has that link. Please only publish content that you are comfortable making available in that way.

Staylink stores account and guide data in Mongo Atlas.

Uploaded images are stored on AWS S3.

We also store session identifiers in your browser local storage so the platform can keep you signed in between page loads.

We keep account and guide data for as long as it is needed to provide the platform, unless you ask for deletion or we need to keep limited records for legal or operational reasons.

Browser-stored session identifiers remain in local storage until you log out, clear browser storage, or they are replaced. On the server side, sessions are configured to expire automatically after a limited period.

You can contact hello@staylink.io to request access to your data, ask for corrections, or request deletion.

If you want all data connected to an access code deleted, email hello@staylink.io with the subject line "Data Deletion Request" and include the relevant access code in the email.