diff --git a/src/options.js b/src/options.js
index 401cbd56..d4532e6f 100644
--- a/src/options.js
+++ b/src/options.js
@@ -10,7 +10,7 @@ import { version as libraryVersion } from '../package.json';
  * @property {boolean} [batchEvents=`false`] -  If `true`, then events are batched together and uploaded only when the number of unsent events is greater than or equal to eventUploadThreshold or after eventUploadPeriodMillis milliseconds have passed since the first unsent event was logged.
  * @property {number} [cookieExpiration=`365`] - The number of days after which the Amplitude cookie will expire. 12 months is for GDPR compliance.
  * @property {string} [cookieName=`amplitude_id`] - *DEPRECATED*
- * @property {string} [sameSiteCookie='None'] -  Sets the SameSite flag on the amplitude cookie. Decides cookie privacy policy.
+ * @property {string} [sameSiteCookie='Lax'] -  Sets the SameSite flag on the amplitude cookie. Decides cookie privacy policy.
  * @property {boolean} [cookieForceUpgrade=`false`] - Forces pre-v6.0.0 instances to adopt post-v6.0.0 compat cookie formats.
  * @property {boolean} [deferInitialization=`null`] -  If `true`, disables the core functionality of the sdk, including saving a cookie and all logging, until explicitly enabled. To enable tracking, please call `amplitude.getInstance().enableTracking()` *Note: This will not affect users who already have an amplitude cookie. The decision to track events is determined by whether or not a user has an amplitude analytics cookie. If the `cookieExpiration</code> is manually defined to be a short lifespan, you may need to run `amplitude.getInstance().enableTracking()` upon the cookie expiring or upon logging in.*
  * @property {boolean} [disableCookies=`false`] -  Disable Ampllitude cookies altogether.