Private accounts and Google sign-in
Google sign-in is restricted to approved email addresses; public registration is unavailable. Other accounts are rejected without saving an AQSR account or issuing an authenticated session. Account type (User or Administrator) is separate from approval to sign in: administration also requires Administrator access. Creating an account does not assign ownership of existing or anonymous links.
Google provides your stable account identifier (sub), email and verification status. We retain these, registration and latest sign-in times and, with your permission, your first and last names and Google photo URL. Google photos load directly without a page referrer; this does not itself store an image file in AQSR. We do not request Gmail, Drive or Contacts access, receive your Google password or retain Google access, refresh or ID tokens. Google’s privacy policy: https://policies.google.com/privacy.
Profile and preferences
You can save a display name and upload an account photo. AQSR stores the uploaded photo privately as a processed JPEG and serves it through authenticated account or administrator routes. Choosing Use Google photo removes the custom photo from the current account record; it does not remove the saved Google photo URL. Names and photos do not grant permissions.
We save your language, theme, time zone, date/time format and security, email-update and newsletter preferences. The three notification preferences start enabled for new accounts; existing choices are preserved. They can be changed in account settings. Email delivery and newsletter sending are not enabled in this version; saving a preference does not send mail or enroll you with an external mailing service. Browser theme/language and table-layout choices may also be saved in browser storage.
Activity, sessions and administration
Account activity records event type and time, such as sign-in/out, settings changes, exports and session revocations. The account view shows up to 50 recent events from the last 30 days; older entries are pruned when the account record is updated, not by a scheduled deletion task. Sessions also store a coarse browser/operating-system label derived from the browser’s request header, alongside the session hash, account reference, anti-forgery value and expiry. You can view and end your sessions; see Cookies & Browser Preferences for session durations.
Authorized administrators can view account names/photos, emails, account types, plan labels, registration/latest sign-in times, newsletter choices, recent activity and session counts; they can change account types, revoke sessions and export selected user-list fields. Account-type history retains up to 100 changes per account, including old/new type, acting administrator identifier and time. Link moderation keeps the actor identifier, time, status and reason with the link. User access does not permit administration; removing sign-in approval denies subsequent protected requests.
Export and account deletion
From account settings you can select profile, photo, preference and notification data to export. Administrators can additionally export site links with original/short addresses, creation dates and current status; these are site-wide links, not proof of personal ownership. Exports exclude session credentials and other accounts’ private data. File download is available; email export remains inactive.
You can delete your account after a recent Google sign-in and explicit confirmation. This removes the current account record, saved custom photo/preferences/activity and its authenticated sessions. It does not delete existing short links, link-moderation records, records retained in other accounts or protected backup copies. It does not remove the separate sign-in approval configuration: a later approved sign-in can create a new account. There is no automatic account-deletion period. Contact [email protected] for further review or deletion requests.
What this policy covers
This policy explains how AQSR handles information involved in creating and opening short links, operating the website, and responding to messages.
You do not need a user account to use the current service.
Links you submit
We store the original web address, its short code and the date the record was created, so we can redirect visitors.
A web address can itself contain personal or confidential information. Submit only information you are comfortable sharing through a link. Anyone with the short link can open it and discover its destination.
Technical request information
Website requests involve technical information such as an IP address, request time, requested address, browser information, and security events.
AQSR and its hosting and protection providers may process this information to deliver the service, enforce request limits, investigate errors, and respond to misuse.
Messages you send
If you email us, we receive your email address, message, and any attachments or information you include.
We use this information to respond, investigate a reported problem, or assess a request concerning a link or personal information. Send only the information needed for that purpose.
Browser preferences
The website uses browser storage for interface preferences, including the theme and any language preference saved through an available language selector.
These preferences help keep your choices when you return using the same browser. See Cookies & Browser Preferences for details.
Service providers
AQSR uses Namecheap for hosting and Cloudflare for website delivery and protection. These providers may process technical information as part of providing their services.
Their privacy information is available at:
External destination websites operate independently and have their own privacy practices.
Sharing and retention
We do not sell personal information.
Information may be shared with providers as needed to operate the service, or disclosed where necessary to meet applicable legal obligations or investigate misuse.
Link records are retained to support redirection and the Link Availability & Disabling policy. Messages and operational information are kept for as long as reasonably needed for their purpose. Providers may apply their own retention periods to technical logs.
Deleted or changed records may remain in protected backups until those backups are replaced or expire.
Your requests
Email [email protected] to ask about information you have provided or request correction or deletion.
We may need enough information to identify the relevant record and verify your relationship to it. Available rights and exceptions depend on the law applicable to your circumstances.
Updates
Changes to this policy will be published here with their revision date.