Overview
Flutter 1.x integration, behavior and privacy.
Flutter package 1.6.0, which wraps iOS and Android SDK 1.6.0. The iOS framework is bundled with the plugin; Android resolves its native dependency from Stay22's Maven repository. A newer native SDK release does not change the package you installed.
The plugin turns travel context supplied by your app into a local accommodation notification. Start with the quick start.
Requirements
Flutter 3.19+, Dart 3.3+, iOS 15+ and Android API 24+. The plugin implements Android and iOS. Guard shared code with Stay22.isSupportedPlatform before calling it on other targets.
With the standard Android 7.0 certificate store, the wrapped SDK cannot verify Stay22's server certificate, so it cannot load partner settings or schedule notifications. API 24 remains the build minimum.
Notification behavior
Normal scheduling is evaluated when your app leaves the foreground. Stay22 account settings control the delay and frequency limits. A new trip can replace a pending notification. Operating-system delivery may be later than the requested delay.
From SDK 3.1.1, the SDK no longer compares the destination with an IP-derived home city on the device, so a trip to the user's own city reaches Stay22 like any other. An optional server distance check depends on your account settings. The home city is never used as the trip destination.
Notifications and events explains context updates and cancellation. Account settings can change independently of the installed SDK; this guide does not freeze server policy.
What reaches Stay22
At startup: while enabled, the SDK requests partner settings and sends a load event. Requests identify your partner ID (aid) and a Stay22-issued identifier (sid22) stored on the device and reused on later launches. The load includes the native OS/SDK versions and answers about whether a set of travel booking apps is installed. On iOS, an undeclared URL scheme is left unknown. Stay22 receives the request IP and derives approximate location and timezone from it, even if no trip is submitted.
Before scheduling: the SDK sends the destination, coordinates, dates and hotel name supplied by your app, the identifiers above, and installed-app answers. A trip held by the device cooldown is not sent for a scheduling decision.
After delivery: the SDK reports shown notifications and failures. Stay22 stores destination and dates with a frequency-capping record tied to your partner ID and sid22. The server record expires automatically, by default after seven days; account configuration can change that period. A tap opens the saved booking URL, which carries attribution and trip context. From SDK 3.1.1, once Stay22 enables prepared booking links for your account, the SDK sends the saved link to Stay22 while scheduling and reports each tap separately; the iOS guide describes what that stores.
Cookies: Stay22 responses set a session22 cookie carrying the session identifier. The iOS HTTP client neither stores cookies nor sends stored cookies. Android installs no cookie handler itself, but a process-wide cookie handler installed by your app or a dependency can store the response cookie. The SDK does not read it.
Device and store disclosures: the SDK requests no GPS permission and uses the trip your app supplies rather than reading device location. Its bundled Apple privacy manifest declares Device ID, product interaction, and precise/coarse location for the persistent identifier, trip coordinates and IP-derived location described above. Review your App Store privacy answers and Google Play Data Safety declaration against this behavior; the manifest does not complete those forms for you.
Consent
The SDK starts enabled by default. The native consent-required keys are available from Flutter 1.4.0. Declare them if Stay22 must receive no startup request before an affirmative choice, then pass the current choice to Stay22.setEnabled(...). Setting it from Dart alone can occur after native startup. See initialization.
Release information
Read the Flutter changelog for your installed package, including minimum-version changes within 1.x. Upgrade notes cover the consent and packaging changes.