Guest User

Untitled

a guest
Apr 23rd, 2026
30
0
Never
1
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.38 KB | Software | 0 0
  1. RateSync — Privacy Policy
  2. Last updated: April 23, 2026
  3.  
  4. Overview
  5. RateSync is a Chrome browser extension that syncs your Letterboxd film ratings to IMDb automatically. This policy explains what data the extension accesses, how it is used, and what is never collected.
  6.  
  7. Data We Do Not Collect
  8. RateSync has no backend server, no analytics, and no telemetry. The following data is never collected, transmitted, or stored by the developer:
  9.  
  10. Your name, email, or any account credentials
  11. Your Letterboxd or IMDb account details
  12. Your browsing history
  13. Your sync activity or film ratings
  14. Any personally identifiable information
  15. Data Accessed Locally
  16. All data RateSync accesses stays on your device. Nothing is sent to the developer.
  17.  
  18. IMDb Session Cookie (at-main)
  19. What: Your IMDb login session cookie
  20. Why: Used to authenticate rating submissions to IMDb's API on your behalf
  21. Where it goes: Sent only to api.graphql.imdb.com — the same endpoint IMDb uses internally — to submit your rating. It is never stored by the extension beyond the duration of a single sync.
  22. TMDb API Read Access Token
  23. What: A personal API token you optionally provide from The Movie Database (TMDb)
  24. Why: Used to look up IMDb IDs for films where Letterboxd does not carry a direct IMDb link
  25. Where it goes: Stored locally in Chrome's extension storage (chrome.storage.local) on your device. Sent only to api.themoviedb.org when an IMDb ID lookup is needed. Never sent to anyone else.
  26. Sync Log
  27. What: A local record of your recent syncs — film title, IMDb ID, rating, success/failure status, and timestamp
  28. Why: Displayed in the extension popup so you can see what was synced
  29. Where it goes: Stored locally in Chrome's extension storage on your device only. Capped at 100 entries. Never transmitted anywhere.
  30. Letterboxd Rating Requests
  31. What: The rating value and film ID from your Letterboxd rating submissions
  32. Why: To know what rating to submit to IMDb
  33. Where it goes: Used in memory only for the duration of a single sync. Not stored persistently.
  34. Third-Party Services
  35. RateSync communicates with the following third-party services on your behalf:
  36.  
  37. Service Purpose Their Privacy Policy
  38. IMDb (api.graphql.imdb.com) Submit your rating imdb.com/privacy
  39. TMDb (api.themoviedb.org) Look up IMDb IDs (fallback) themoviedb.org/privacy-policy
  40. Letterboxd (letterboxd.com) Resolve film details letterboxd.com/privacy-policy
  41. These services have their own privacy policies. RateSync only contacts them to perform the sync you triggered.
  42.  
  43. Permissions Justification
  44. Permission Reason
  45. cookies Read the IMDb at-main session cookie to authenticate with IMDb's API
  46. storage Store your TMDb token and sync log locally on your device
  47. webRequest Detect when you submit a rating on Letterboxd
  48. https://*.imdb.com/* Required to read the IMDb session cookie, which is set at the root .imdb.com domain
  49. https://letterboxd.com/* Intercept rating events and fetch film detail pages to resolve IMDb IDs
  50. https://api.themoviedb.org/* Look up IMDb IDs via TMDb when Letterboxd does not carry a direct link
  51. Data Retention
  52. Sync log: stored locally, capped at 100 entries, clearable at any time via the extension popup
  53. TMDb token: stored locally, removable at any time via the extension settings
  54. All local data is deleted when the extension is uninstalled
  55. Changes to This Policy
  56. If this policy changes, the updated version will be published at the same location with an updated date.
Advertisement
Comments
  • Ulrlavor
    5 days
    # CSS 0.84 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1ifNm-s74mX7GChaEzSJ1dVQCy1SrSxlMVRYi8ys0rgQ/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 25% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from SimpleSwap — instant swap).
Add Comment
Please, Sign In to add comment