StayMap Privacy Policy
Effective date: October 12, 2026
StayMap is a personal accommodation journal. Your journal is stored on your device. Optional accounts, email forwarding, a private desktop outline, Friends, shared stats summaries and direct recommendations, maps, sharing, backups and TestFlight testing involve the additional data flows described below.
Your journal and local storage
StayMap stores information you add or import, including properties and locations, dates, booking references, room details, prices, points, ratings, notes, check-in records, trip purpose and funding. Optional arrival details include property clock times, a time zone, breakfast information and arrival instructions. Personal hotel memories can include a room tip, experience highlights and one selected photo. Wallet stores the loyalty numbers, tiers, balances, expiry dates and notes you enter. Settings and storage diagnostics are also local. Your places stores saved property names, addresses, map coordinates, websites, private planning notes and any received recommendation text and author name. Saved ideas are separate from booked stays and do not increase your travel statistics. The Would return collection is derived from completed stays and your explicit review answers. Around your stay stores nearby place names, categories, addresses, optional map coordinates and websites, private notes, and any recommendation text and sender name you deliberately save. Saved places and nearby finds are included in journal backups. Nearby finds attached to a deleted stay are also included in that stay’s recovery copy.
Booking costs can include a confirmed booking total and currency, separately from a nightly rate. Cruise stays can contain a ship name, sailing dates, cruise line and ports of call, including each port’s name, country, sailing day, optional map coordinates and visited status. Nearby finds can have a Want to go or Been there status. These saved details are included in journal backups and a deleted stay’s local recovery copy. Booking totals, cruise itineraries and nearby visit statuses are not included in the desktop outline or automatically sent through recommendation sharing.
Your saved journal is not automatically uploaded or synchronized when you create a StayMap account. An account is optional and adds a private inbox for forwarded booking confirmations, private friend connections and recommendations you explicitly send or receive. The local journal works without one. StayMap does not display advertising or automatically access your email, calendar, hotel or loyalty accounts. Optional service providers process information as described below. Apple's services and TestFlight handle information separately.
Optional accounts and forwarded emails
StayMap uses Supabase for accounts, private inboxes, the optional desktop outline and the Friends features described below, and Resend to deliver sign-in codes and receive emails. Your first email sign-in on iPhone creates an optional account. On the desktop website, choose Create an account explicitly; signing in to an existing account does not create another one. Account information includes your email address, assigned account identifier, forwarding address and authentication records. Sign-in credentials are stored in your device's Keychain. Signing in does not create a public profile or friends directory, or connect your local journal to the cloud.
When you forward a confirmation to your StayMap address, Resend receives the complete email, including headers, text, HTML and any attachments. StayMap's backend retrieves readable content and stores a limited text copy, sender, subject, delivery times, attachment count and processing information in your private inbox. Confirmation text can contain guest names, booking references, travel dates, hotel addresses, prices and other information included in the email. Forward only messages you intend to import and remove unrelated email history where practical.
When you open the email's files, the backend checks your access and obtains attachment metadata and temporary download links from Resend. When you choose photos or PDFs to read, the app downloads the selected files and reads them on your device. The backend does not download or store attachment binaries or raw email files, retain the temporary links, or perform cloud OCR. Original attachments are not added to a permanent document library in the app. Extracted text and your review corrections are retained locally as described under Imports. The backend converts readable HTML to text without loading embedded remote images. StayMap does not use a cloud AI service to turn confirmations into stays. Email providers may separately use automated security and abuse screening under their own practices.
Keep your forwarding address private: anyone who knows it can send mail to it. Settings → Account & forwarding lets you replace the address. The old address then stops delivering into your StayMap inbox; existing inbox messages remain. This does not withdraw email copies already processed by the provider.
Inbox retention and account deletion
Opening a review first saves a local copy of the selected or extracted text. For an email without attachments, a successful local handoff and server acknowledgement remove the active cloud text and sender/subject copy. Emails with attachments remain in the temporary cloud inbox until you discard them or retention expires, so you can choose other files separately. You review and correct the details before explicitly saving a stay. Remove email copy in Confirmations, or Discard email in Account & forwarding, removes the active cloud inbox copy without deleting local drafts or saved stays. A network failure can leave a cloud copy pending for retry. Downloaded text follows the local import, journal and backup practices below.
A daily cleanup removes inbox messages and delivery receipts older than 30 days. Removal normally occurs at the next cleanup after that period; service outages or a paused project can delay it. Receipts retain account and delivery identifiers and timestamps, without the email text, to prevent repeated delivery. This describes StayMap's database, not every provider copy.
In Settings → Account & forwarding → Delete account, confirm with a fresh code sent to your account email. This deletes your Supabase account, forwarding address and associated active inbox, desktop outline and its revisions, Friends, shared stats summary, recommendation, report and block records. Signing out does not delete the account or turn off stats sharing. Neither action removes downloaded import text, local stays, recovery copies, exports or shared copies; use the corresponding local and provider controls for those. Deleting an account or stay does not cancel a hotel reservation.
Resend documents 30-day email and log retention on its Free, Pro and Scale plans and seven-day backups. Earlier message removal requires a separate request to Resend; StayMap's inbox and account deletion do not automatically delete Resend's copies. Use the contact details below for help with a provider deletion request. Provider logs, security records and backups follow their applicable retention practices rather than the active inbox deletion time. Resend retention and processing.
Service records and processing locations
Supabase and Resend process account and delivery events, request times, IP addresses, user-agent/device information, responses and errors to authenticate users, deliver email, prevent abuse and maintain service reliability. These operational records can be associated with an account. StayMap's application handlers do not deliberately log email bodies, sign-in codes or credentials. Provider mail storage and operational records are separate from those application logs.
StayMap's Supabase database project is in Ireland. Resend stores message contents, webhook payloads, delivery logs and account records in the United States; choosing Ireland for mail routing does not make storage EU-only. Supporting services can process information outside the database region. Resend describes contractual safeguards for international transfers in its processing terms. Resend regions, Resend processing terms, Supabase privacy.
Supabase's Free plan currently lists one day of API/database logs, one hour of Auth Audit Logs and no included automatic backups or point-in-time recovery. Those plan limits do not establish when all internal security records or provider copies are erased. Authentication audit records are subject to the provider's service and security retention. Supabase plan, Auth audit records, backup practices.
Optional private desktop outline
Open the StayMap desktop journal. In a supported build, Account → Desktop journal explains the scope and asks before connecting. Signing in or registering alone does not upload your saved stays.
Connecting sends hotel names, check-in and check-out dates, cities, countries and saved map coordinates for all stays on that device to your account in StayMap's Supabase backend. These fields describe past, current and planned accommodation locations. Changes are sent while the app is open. Connection state, account and record identifiers, revision history, consent versions and request-limit counters are retained to manage updates and account isolation. Fields are linked to your account and used for app functionality, not advertising or tracking.
The outline excludes personal photos, ratings, notes, street addresses, original confirmation text, booking references, costs, cruise itineraries, memberships and saved places. Text entered in the name, city or country fields is included as part of those fields; for a cruise, the name can be the recorded ship name. After you explicitly enable desktop editing on a compatible iPhone build, desktop additions and edits to names, dates, cities, countries and map coordinates can update this iPhone while StayMap is open. Conflicting edits require your review, and private device-only fields are preserved. This is not full-journal synchronization or a complete backup. Keep using Backup & restore for your full local journal.
Only the signed-in owning account can read the outline and, when enabled, add or edit its basic stay details through the app's API. Friends and public visitors do not get access. StayMap's operator and hosting providers have administrative access needed to operate their systems. The outline is not end-to-end encrypted.
Pause connection stops cloud reads and writes but keeps the cloud copy. Erase cloud journal removes the active cloud outline and its revisions and stops uploads; local stays remain. Offline requests wait until the app reconnects. Signing out stops this device's updates and hides the connected state until the same account signs back in. The device's existing connection is not automatically transferred to another account.
Deleting a stay on iPhone clears its current cloud record after upload; earlier revisions remain until you erase the whole cloud journal or delete the account. There is no automatic expiry for this revision history. Whole-journal erasure and account deletion remove the active records; provider backups and security or operational logs follow their own retention practices. Earlier downloads and recipient copies are separate.
Desktop sign-in, storage and downloads
The website uses Supabase for email verification and account sessions and Resend for emailed codes. By default, sign-in stays in memory. Choosing Keep me signed in in this tab stores access and refresh tokens in tab session storage. Browsers may restore that storage after restarting; sign out on shared computers. Loaded stays and unsaved form drafts remain in memory. When you choose Save, the basic details and request identifiers for one pending addition or edit are stored in this tab’s session storage before sending, so an interrupted save can be retried without creating a duplicate. This pending save is removed after confirmed success, definitive rejection or sign-out; browser session restoration may retain it after closing a tab. Appearance preferences are stored locally without an account identifier. There is no offline journal cache.
Sign out clears the displayed journal and saved tab session immediately, then attempts to revoke that browser session. Network failure can delay server-side revocation until expiry. Export outline downloads unencrypted JSON containing the currently loaded hotel/date/destination/map outline. It does not contain the full iPhone journal. You control the download's destination and later deletion. Browser screenshots, saved pages and operating-system backups are outside these controls.
The website is hosted using Sites and Cloudflare. Hosting and account providers process requests and operational information such as IP addresses, user agents, timestamps and errors to deliver and protect the service. StayMap does not add advertising trackers or third-party website analytics. Their processing locations and service records follow provider policies: https://openai.com/policies/privacy-policy/ and https://www.cloudflare.com/privacypolicy/. Account-provider practices are described above. The website's Desktop privacy page also explains this scope.
Friends and direct recommendations
If you choose to use Friends, StayMap stores the display name you choose, account identifiers, private invitation hashes, pending requests, accepted connections, timestamps and abuse-prevention counters in Supabase. Names are chosen by users and are not unique or verified real-world identities. Friends responses show your chosen name, not your email address. There is no public profile directory or access to your device address book. Exchange invitations privately with people you know.
An invitation expires after seven days; making a new one replaces the old code. A valid code creates a request only when its recipient explicitly sends it. The invitation owner must accept separately. Opening an invitation never sends or accepts a request automatically. You can revoke an invitation, decline or withdraw requests, edit your chosen name and remove connections. Expiry or revocation stops use of a code; it does not retract an already-created request. Connecting does not upload or share your stays, future travel, nearby notes, photographs, ratings or loyalty information.
Optional shared stats
Stats sharing is off by default. If you explicitly publish a summary in Friends, StayMap stores three totals you review—completed stays, nights and number of countries—alongside your account identifier, the publication time and a revision number in Supabase. Accepted friends can see these totals and when you published them beside your chosen Friends name. The summary contains no hotel or destination names, individual stay dates, future bookings, precise locations, prices, ratings, photographs or private notes. It is a snapshot supplied by your app, not a verified travel record.
Sharing applies to all your accepted friends, including people you accept later, until you turn it off. It is not a public profile or directory. Editing your local journal does not automatically update the shared totals; publishing an updated summary replaces the previous active snapshot. The published summary has no automatic expiry.
Turning off stats sharing removes the active counts and publication time. A revision number associated with your account remains to stop an older, delayed publication request from silently turning sharing back on. Removing a friend or blocking someone removes their access through Friends. Unblocking alone does not reconnect you; accepting a new connection while stats sharing is still on makes the published snapshot available again. Turning off sharing cannot withdraw screenshots or other copies someone already made. Account deletion removes the summary and its revision record; provider logs and backups follow their separate retention practices.
Direct recommendations
When you explicitly send a recommendation to one accepted friend, StayMap stores the selected hotel or nearby place's name, category or accommodation type, brand, address, city/country, map coordinates and website if included; the fresh message you write; sender and recipient account IDs; and delivery times. You see the card before sending. These fields have no booking dates, confirmation or room numbers, prices, loyalty details, photos or other private journal notes. A place name, address or message can itself contain personal information, so check the preview. The recipient sees your chosen Friends name and may save an independent local copy with your message and attribution. A saved hotel becomes a Your places idea; a nearby find can be saved to an existing stay.
Pending recommendation content is accessible for 90 days after sending. Dismissing it removes that content from the active inbox. A content-free delivery receipt containing account IDs, an idempotency key, a payload digest and timestamps remains for retry protection and abuse prevention until 90 days after sending. Ending a connection removes pending recommendation content between both accounts; reconnecting does not restore it. This does not retract copies either person already saved or exported. StayMap does not provide the sender with read or save receipts, send push notifications, or offer a public feed, chat or live shared itinerary through this feature.
Reporting hides a received recommendation and keeps its selected shared content, sender's chosen name, sender/reporter account IDs, selected reason, timestamps and review status for manual operator review. Report evidence expires 90 days after reporting. Private journal content is not attached automatically. StayMap does not notify the sender of a report. Reports are reviewed manually; there is no guaranteed response time. Any local operator review copies must be removed when no longer needed and are not removed automatically by the server cleanup job.
Blocking records the two account IDs and a timestamp, ends their connection, removes pending requests and recommendation content, and prevents new friend requests or recommendation delivery between them while the block remains. You can review your own block list and unblock someone in Friends. Unblocking does not reconnect you or restore removed items. Blocks remain until the person who created them unblocks or either account is deleted.
Daily cleanup removes expired recommendation content, delivery receipts and reports at the next scheduled run after the periods above; outages may delay physical removal. Access checks enforce recommendation expiry even if cleanup is delayed. Deleting your account removes its related active Friends, recommendation, report and block records. Provider logs and backups follow their separate retention practices. Copies other people already saved on their devices remain independent.
Imports and the share extension
You choose the text, screenshots, PDF/text file or shared content to import. Screenshot and scanned-PDF text recognition runs on your device. Supported devices can use Apple's on-device language model to extract booking details, with a local text parser as fallback. StayMap does not send confirmations to a developer-operated AI service. Newly read confirmations can suggest explicitly labelled property check-in/check-out times, breakfast details and arrival instructions for your review; these remain in the local draft until you save or remove them. The parser does not infer a property time zone or automatically update older reviewed drafts and saved stays. Original PDFs and images are read for extraction but are not retained as booking attachments. The original files remain in the location you selected; a cloud Files or Photos provider may download them under its own practices.
Choosing Save to StayMap in the share extension stores the extracted text and preliminary booking fields in a local shared inbox. Importing directly in the app also keeps confirmation text, the first extracted fields and your corrected review draft in this inbox. It retains the full captured text, not only the booking fields, so this can include other personal information from the confirmation. Closing a review or the app keeps unfinished work for later in Confirmations. This screen brings local reviews and the signed-in forwarding inbox together; displaying them together does not upload local reviews or synchronize them between devices. Local reviews remain on the device after signing out. The app and extensions share these files through an iOS app-group container on the device. The separate Add several past stays flow keeps its source list and edited review rows in an app-private local draft until completed or discarded. Saved or discarded inbox and draft copies are normally removed; unreadable files or failed cleanup can leave copies on the device.
When you save an imported stay, StayMap retains its source text with the journal record so you can inspect Original confirmation later. For a past-stay batch, this is the source line for that stay. A local import identifier, source-text fingerprint and import time are also retained to recognize repeated imports. Editing the saved booking does not replace this source text. These source details are included in exported backups of saved stays and in recovery copies when you delete a stay. They are not automatically included in companion booking or recommendation sharing.
Opening a .staymap companion file or selecting one through Import StayMap file reads that file and keeps a local copy in a separate, app-private inbox. Its booking details remain there across app launches until you successfully add the stay or discard the pending copy. Opening or closing a review does not add the booking to your journal. Adding it creates your own independent local stay; duplicate warnings do not overwrite existing stays. A companion message, if included, is saved with your arrival notes. Selecting a file stored with a cloud Files provider may download it through that provider.
Opening a .staymapplaces recommendation file or selecting one through Your places keeps a copy in an app-private inbox until you save or discard it. Closing a review keeps it pending. You review the included places before saving them to Your places; this does not add bookings or change travel statistics. Author names are supplied by the file's creator and are not verified accounts. Existing saved places are kept when a matching recommendation is imported again.
Widgets
A separate local snapshot supplies current and upcoming property names, cities, brand or accommodation labels, dates, check-in status and an opaque stay identifier to widgets. It excludes booking references, room numbers, notes, prices, membership details and precise coordinates. Logos are bundled locally.
Hide property details in Settings removes names, cities and brand identity from that snapshot and its display. Dates and countdowns remain visible. iOS controls refresh timing, so updates may take time. Widgets can expose displayed information on your Home Screen or Lock Screen.
Personal photos
The system photo picker lets you choose an image for a stay. StayMap does not browse your full photo library. The selected image may need to download through Apple's Photos service if it is stored in iCloud. StayMap creates a smaller local JPEG copy, without the source image's embedded location metadata, and leaves the original in Photos unchanged. The saved copy appears in your stay and passport chapter and is included in your exported journal backup. It is not automatically shared with companions or uploaded to a developer-operated service.
Bundled reference photographs for supported cruise ships are stored in the app and can display offline. Displaying these images does not contact Google or the image source. Their credit controls identify the photographer, source and licence; opening an external source or licence link uses that website's practices. A personal ship photo you choose takes priority and follows the personal-photo handling above.
Maps and external services
Apple's map, search and geocoding services can receive search text, property names, cities, countries, relevant coordinates and map regions. Searches occur as you type, when a hotel detail screen loads, or when coordinates are looked up for a saved stay. Map content also loads through Apple services; network activity is not limited to saving a stay. Around your stay searches use the hotel's recorded location or city/country as a search hint. They do not use your live device location, and a result is not proof that a place is nearby. Recommendation cards may also load their included place coordinates through Apple Maps. Finding a cruise port on the map sends the port search text to Apple’s search service. Displaying saved port maps also loads Apple map content for their recorded coordinates and regions. Marking a port or nearby find as visited is a saved journal choice, not live location tracking.
StayMap does not request continuous or background access to your device location. Opening directions in Apple Maps or Google Maps passes the destination to that service, which may use your location under its own permissions. Hotel websites, phone calls, support and other external links use the selected app or site's privacy practices. The Explore hotel/property sheet also offers deliberate Google web searches, Google Maps searches and Tripadvisor-scoped Google searches. These links contain only the recorded property name, city and country—not booking codes, travel dates, ratings or notes. The property name/location themselves may be personal (for example, a rental nickname). Opening the sheet does not run those web searches. Website links supplied by a matching Apple Maps listing are labelled as such; searches and external reviews are not imported into StayMap.
Opening Apple Maps & Look Around can start a search using the displayed property text when no listing is already selected. Opening a selected place's details or choosing Look around the area requests that listing or street imagery from Apple. Coverage and available details vary. These provider views do not replace your saved property or personal cover photo.
Apple Maps privacy: https://www.apple.com/legal/privacy/data/en/apple-maps/
Google hotel photos and details
StayMap includes Google Maps features and content through Places UI Kit. When you open an eligible hotel stay without a personal cover photo, StayMap may automatically search for its photos using the recorded hotel name, city/country and saved map area. It only remembers an automatic match when the name and saved location give a single sufficiently close result. Uncertain results need your selection. This is not a search for every row as you scroll your stay list. A remembered listing may request its photos and details when shown in the stay detail or featured stay card, without a new search or tap on Photos.
You can also open Photos on Google Maps and choose Search Google Maps yourself. The submitted text initially contains the property name, city and country; you can edit it before a manual search. Check it for personal information. Selecting a listing sends its Google place identifier to request photos and details; actions in the Google viewer can make further requests. An unchanged search uses an area around the property's saved coordinates when available. If there is no saved location, or you edit the search text, Apple geocoding first receives the submitted text to help locate the property or city. The resolved area is a search preference, not a strict boundary or your phone's location. If the area cannot be located, no Google search is started until you correct or retry it.
StayMap does not add your account details, booking dates, confirmation or room numbers, personal ratings, notes or journal photographs to these requests. It does not request your live device location for this feature. Text entered into the property's name/location fields or search field is part of the submitted text and can itself contain personal information. Google receives that text, the search area's coordinates, selected place identifiers and network information, including your IP address. Google's SDK declares device identifier collection for functionality and analytics. Google processes this information under its Privacy Policy, including its retention and international-processing practices. Deleting a StayMap stay or account does not issue a deletion request to Google.
StayMap remembers the Google place identifier and selection time on this device, keyed by a hash of the recorded property identity and location, with up to 500 matches. Local counters and rejected-match markers limit repeat lookups. Choose another listing removes that remembered association and stops automatic re-selection for the same property identity until you select a listing yourself. Changing the recorded identity requires a new match. Automatic searches and photo views share a local allowance of up to six app-initiated attempts per device per UTC day, and each property can have at most one automatic lookup in 24 hours. This allowance does not limit manual searches or every internal network request made by the SDK. The existing shared provider quotas still apply; these controls are not a guaranteed spending cap.
Google photos, ratings and listing details remain provider content in Google's attributed viewer, including when that viewer appears in a stay header or featured card. StayMap does not copy them into personal journal covers, include them in journal backups or attach them to recommendations. Your own selected photo takes priority and remains separate. Provider storage and caching follow Google's practices.
Google Maps terms
StayMap includes Google Maps features and content. Your use of those features and content is subject to the current Google Maps End User Additional Terms and Google Privacy Policy.
Sharing, copies and backups
Passport-stamp and achievement sharing sends the previewed artwork to your chosen destination. Dates are included only if enabled; these artwork exports exclude hotel names, booking references, notes and membership details. Screenshots you share can include whatever is visible in them.
Your year in stays offers a previewed image shared through the system share sheet. It includes the selected year, trip-purpose label, whether the year is still in progress, and totals for nights, completed stays, countries, cities and properties. It excludes hotel and destination names, individual travel dates, ratings, photos, booking details and private notes. The app or recipient you choose receives the image under its own privacy practices.
Companion sharing sends either a readable itinerary or an importable .staymap booking file through the system share sheet to the app or recipient you choose. The preview includes property name, stay type, brand, booking platform, location, dates, nights and a map link when available. The booking file includes saved property coordinates when available. Confirmation numbers, room numbers and arrival details are included only when you enable their separate options. A companion message is separate from your private journal. Personal journal notes, room memories, photos, ratings, prices, trip purpose, funding and loyalty details are excluded. Both sharing options produce static, unencrypted copies: later edits do not update them, and StayMap cannot withdraw copies already sent. The receiving app or service applies its own privacy practices. Saving a copy to a cloud Files provider may upload or sync it under that provider's settings.
Recommendations and shortlists are shared as previewed readable text or an importable .staymapplaces file. They contain the selected property's identity, address, coordinates and optional website, plus recommendation text and an author name that you deliberately enter. They exclude stay dates, booking references, rooms, prices, ratings, journal photos, private notes and loyalty details. A friend's received author name and recommendation are not automatically copied into a new recommendation you create. These are static, unencrypted copies sent through your chosen share-sheet destination, with the same recipient and cloud-provider limitations as booking copies.
Share these finds exports only the nearby places you select, with the hotel name, categories, addresses and map links. Your notes are excluded unless you turn on Include my notes. Booking dates, references, room details, spending, ratings, loyalty details and journal photos are not included. The preview and exported guide use the same content. This is a static copy sent through the system share sheet; recipients and chosen apps retain their copies independently.
Copy actions put the selected reference, member number, property location, friend invite code or diagnostics report on the system clipboard. Diagnostics can include app/device versions, file paths, record counts and errors. StayMap does not automatically send that report to the developer.
Backups are unencrypted JSON files containing saved stays, memberships and Your places, including notes, booking references, member numbers, arrival details, saved memory photos, private planning notes, nearby places and received recommendations with sender attribution. For imported stays, backups also include the retained source text and local import identifiers, fingerprints and times. Pending inbox copies, unfinished import drafts and Recently Deleted recovery copies are not included in these exported journal backups. You choose the destination in Files. A selected cloud provider may upload or sync the file under its own settings. Restore reads the file you choose and adds records locally. Device backups may separately include app data depending on your Apple settings.
Apple backup information: https://support.apple.com/en-us/108770
TestFlight and support
For TestFlight builds, Apple automatically collects crash and usage information and shares it with the developer, including installation, session, device and operating-system details. Apple also shares feedback, comments and screenshots you submit. Name and email visibility depends on the invitation method and information you provide; accepting a public-link invitation alone does not reveal them to the developer.
We use beta information to investigate problems and improve StayMap. Review feedback screenshots for private journal details. Emailing support shares your address, message and attachments with the developer and email services. Issues posted to the public support repository are public.
Apple explains TestFlight data, retention and controls here: https://www.apple.com/legal/privacy/data/en/test-flight/
Managing your information
You can edit or delete stays and saved places, remove nearby finds and memberships, discard queued imports or unfinished past-stay drafts and change widget privacy. Account controls let you remove friend connections, turn off stats sharing, dismiss or report recommendations, manage blocks and delete the optional account. Deleting a stay, including using import Undo, first keeps a local recovery copy containing its saved information, including notes, photos and retained confirmation text. Settings → Recently deleted stays lets you restore it or permanently delete the recovery copy. These copies have no automatic expiry and remain on this device until you restore or remove them; a failed cleanup after restore can leave a copy for later removal. They are excluded from active history totals and exported journal backups. Deleting a stay does not cancel a reservation or update a previously published stats snapshot. Other local records remain until you remove them or the app's data. Recovery copies created after a storage failure may remain separately from the active journal.
Deletion does not remove earlier exports, clipboard copies, shared images or device/cloud backups. Manage those through the relevant app, recipient or provider. Contact the developer about access or deletion of support or beta-feedback information you shared with us. Apple-held information is managed through Apple's controls.
Contact
Email: support@staymap.app Support: https://github.com/satsdisco/staymap-support
This policy will be updated when StayMap's data practices change.
Visiting this website
This website has no advertising trackers, analytics scripts, or signup forms. Fonts and images are served with the site. Our hosting service processes requests needed to deliver these pages. When you follow an external link, that service’s privacy practices apply.