Home > Articles > Programming > General Programming/Other Languages

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

Unwrapping Optionals

Optional types always return either a wrapped value or nil. Wrapping means that any actual content is stored within a logical outer structure. You cannot get to that value (in this case, "moo") without unwrapping it. In the Swift world, it is always Christmas, and there are always presents—or at least variables—to unwrap.

Swift offers a variety of mechanisms for unwrapping optionals and recovering the underlying data type stored within them. There are more ways to get at a wrapped optional value than you might expect. The expressive possibilities expanded in Apple’s Swift 2 update to provide greater developer flexibility.

Forced Unwrapping

The simplest way to extract an optional value is to append an exclamation point:

print("The sound is \(sound!)") // may or may not crash

This is also the most dangerous approach, and you want to generally avoid it in production code.

If the value is wrapped (that “optional” result you just read about), the exclamation point returns the value stored within the wrapped element. If the value is nil, you experience a fatal runtime error—which is not nearly as fun or gratifying for your workday.

The nil value is the Swift equivalent of your aunt’s home-crocheted vest with a large friendly moose decoration on it. It’s pretty important to check whether an item is nil before unwrapping it. You can more safely unwrap with an exclamation point within an if statement because this sound is nominally guaranteed to be non-nil in non-extreme (that is, nonthreaded) situations:

if sound != nil {
    print("The sound is \(sound!)") // doesn't crash

Safety is a relative thing. While this forced unwrap is pretty safe at compile time and runtime in its current use, it’s dangerous while editing. If you accidentally move that print line out of the if block, the compiler cannot warn you about it, and you will ship broken code.

In this example, the sound variable is also not weak. It won’t deallocate between the nil test and unwrapping. Never use forced unwraps with weak variables because they may do just that.

As a rule, avoiding forced unwraps, even within if clauses, helps you avoid potential disasters.

Conditional Binding

Conditional binding provides a better and safer approach that avoids forced unwrapping. In conditional binding, you optionally bind (that is, assign) a value to a new constant or variable using an if-let or if-var statement. When the optional is not nil, Swift unwraps the value, assigns it, and executes a block of code. When nil, you either enter an else clause or continue to the next statement:

if let sound = soundDictionary[animal] {
    print("The \(animal) says \(sound)")
} else {
    print("Any sound the \(animal) says is unknown to modern science")

It’s conventional in Swift to use identical identifiers in conditional bindings for both wrapped and unwrapped versions. In the following snippet, a mySound constant is unwrapped within the if-let (or if-var) scope but wrapped outside it:

let mySound = soundDictionary[animal] // mySound is wrapped
if let mySound = mySound {
    print(mySound) // mySound is unwrapped

Using the same identifier makes it clear that you’re working with the same semantics in different states of undress. Conditional binding clauses tend to be short. This enables you to verify your overloaded symbol intent with a glance.

The right-hand value in an if-let assignment must be an optional. You cannot use this construct with an already-unwrapped item. The following statement leads to an error, complaining that a conditional binding initializer must have Optional type:

if let sound = soundDictionary["cow"]! { // error!
    print("The cow says \(sound)")

Conditional Binding and Type Casts

Type casting enables you to re-interpret an instance’s type at runtime. Swift offers two distinct type-casting operators (is and as) with four variations: is, as, as?, and as!. These operators enable you to check value types and cast values to other types. The is operator checks whether you can convert an instance’s type to another, typically more specialized, type:

let value = 3
value is Any // true
value is Int // true
value is String // false

The as operator casts to other types and can test whether an item conforms to a protocol. These are its three forms:

  • The as operator applies direct casts. The compiler must determine at compile time that the cast will succeed.
  • The as? variant contains a question mark. It performs a conditional cast that always returns an optional value. If the cast succeeds, it’s wrapped in an optional instance. If not, it returns nil. This is the cast I use most often in day-to-day coding. The compiler issues warnings when it detects that a cast will always succeed (for example, String to NSString) or always fail (String to NSArray).
  • The forced variant as! includes an exclamation point. It either returns an unwrapped item or raises a runtime error. This is the most dangerous cast type. Use it when you know a cast will always succeed or when you want your application to prematurely crash.

Conditional binding and conditional casting work hand-in-hand. Figure 3-2 demonstrates why. In this screenshot, Swift code creates a string-indexed dictionary that stores arbitrary Any instance types. Even when a lookup returns a valid integer for the "Three" key, a forced unwrap still reports Any type. To use this value as a number, you must downcast from Any to Int.

Figure 3-2

Figure 3-2 Lookups from a [String:Any] dictionary return Optional<Any> values. The type remains Any even after forced unwrapping.

The as? type operator produces optionals even when used with non-optional values:

let value = 3 // Int
let optionalValue = value as? Int // Int?

Conditional binding enables you to apply a cast, test the resulting optional, and then bind unwrapped values to a local variable. In the following example, result is bound as an Int constant within the if clause code block:

if let result = dict["Three"] as? Int {
    print("\(result + 3) = 6") // 6 = 6

This conditional pattern of fetch, cast, and bind commonly appears when working with structured data from web services and databases. Swift enables you to use type safety while navigating through key paths down to data leaves.

Recipe 3-1 searches a UIView hierarchy, using conditional casting to match subviews against a supplied type, returning the first subview that matches that type. The as? type operator returns an optional, which is conditionally bound to a local view variable. If the binding succeeds and a type match is found, the function returns. Otherwise, it recurses down the tree in a depth-first search.

Recipe 3-1 Using Conditional Binding to Test Types

public func fetchViewWithType<T>(
    type t: T.Type, contentView: UIView) -> T? {
    for eachView in contentView.subviews {
        if let view = eachView as? T {return view}
        if let subview = fetchViewWithType(
            type: t.self, contentView:eachView) {
            return subview
    return nil

Binding Cascades

Although useful for accessing values, if-let bindings build into code structures colloquially known as pyramids of doom. Each successive test indents your code further and further to the right, creating a triangle of empty space to the left of the if statements and then the closing brackets:

if let cowSound = soundDictionary["cow"] {
    if let dogSound = soundDictionary["dog"] {
        if let pigSound = soundDictionary["pig"] {
            // use sounds here

It’s the sort of code you don’t want to bring home to your project manager—or your mummy.

Using multiple optional bindings within a single test enables you to avoid this structural mess. First introduced in Swift 1.2, cascading permits any number of conditional bindings tests within a unified conditional:

if let
    cowSound = soundDictionary["cow"],
    dogSound = soundDictionary["dog"],
    pigSound = soundDictionary["pig"] {
        // use sounds here

If any assignment fails, evaluation stops, and control moves past the if statement. This approach is particularly useful when working with web-sourced data, such as JSON, where each step may depend on the results of the previous conditional binding. The following example is from a script that checks prices on the iTunes App Store:

if let
    json = json as? NSDictionary,
    resultsList = json["results"] as? NSArray,
    results = resultsList.firstObject as? NSDictionary,
    name = results["trackName"] as? String,
    price = results["price"] as? NSNumber {
    // Process results

This code pulls data from the App Store and deserializes it with NSJSONSerialization.JSONObjectWithData. The results list is extracted from the JSON data, and the app results from that list, and so forth.

While this approach avoids pyramid indentation, it introduces a bad tendency toward code constipation. Increased blockiness makes if-let cascades hard to mentally process. Copious commenting and spacing can mitigate this. As shown here, the results are faster for the brain to parse, make it easier to spot errors, and are better for adding, removing, and reordering intermediate steps:

if let
    // Access JSON as dictionary
    json = json as? NSDictionary,

    // Retrieve results array
    resultsList = json["results"] as? NSArray,

    // Extract first item
    results = resultsList.firstObject as? NSDictionary,

    // Extract name and price
    name = results["trackName"] as? String,
    price = results["price"] as? NSNumber {

        // Process results

guard Statements

The guard statement was first introduced in Swift 2. It offers another way to unwrap and use optionals. Although guard is not limited to use with optionals—you can use it with general Boolean conditions as well—it provides a major development advantage that’s specific to optional handling. In particular, guard statements move code out of indented scopes by offering early-return error handling.

Early-return inverts the handling of success and failure paths. Errors are handled first, enabling success code to be written at the highest possible scope. Compare this to if-let, where you cannot put the failure path first and your success conditions must be handled in a child scope. Without guard statements, all conditionally bound values must be used with the if statement code block that binds them. For example, the following snippet conditionally binds a cowSound constant using if-let, and the cowSound constant is undefined outside that scope:

if let cowSound = soundDictionary["cow"] {
    // cowSound is unwrapped within this scope
// cowSound is undefined outside the scope

Like if-let, a guard statement conditionally unwraps and binds optional variables. When that binding fails, it executes a mandatory else clause, which must exit the current scope, using throw, break, continue, or return statements. Otherwise, the guard statement unwraps the optional value and binds it to a variable you can use throughout the remaining lifetime of the current scope:

guard let cowSound = soundDictionary["cow"] else {throw Error.MissingValue}
// cowSound now defined and unwrapped

Think of a guard statement as a soldier that will not permit the flow of execution to continue forward unless its condition or conditions are met. Unlike if-let, guard does not establish new scopes. Instead, it guides traffic through the existing scope.

Like if-let, a single guard statement can express multiple conditions, separated by comma delineators. For example, you might perform multiple constant assignments:

guard let
    cowSound = soundDictionary["cow"],
    dogSound = soundDictionary["dog"]
    else {throw Error.MissingValue}

Or you might include a more general test along with assignments:

    soundDictionary.count > 2,
    let cowSound = soundDictionary["cow"],
    let dogSound = soundDictionary["dog"]
    else {throw Error.MissingValue}

Implicitly Unwrapped Optionals

Swift provides a feature called implicitly unwrapped optionals, which you declare by appending an exclamation point to the end of the type. Unlike normal optionals, these versions unwrap themselves, much like a jack-in-the-box or the hired entertainment at a bachelor party. Use implicitly unwrapped optionals cautiously. They’re a fairly dangerous feature as they introduce fatal runtime errors if you attempt to access values stored inside a nil case optional.

Here’s an example of first an assignment to a normally typed constant and then to an implicitly unwrapped one. The difference is what happens when you access the wrapped value. That’s where the name comes from because during access, the value is implicitly unwrapped:

var animal = "cow" // 1
let wrappedSound = soundDictionary[animal] // Optional("moo")
let unwrappedSound: String! = soundDictionary[animal] // "moo"

// prints: The unwrapped sound is "moo"
let soundString = "\"" + unwrappedSound + "\"" // 2
print("The unwrapped sound is \(soundString)")

In this example, when you use unwrappedSound in the string assignment, its value is not Optional("moo"). Its value is accessed as moo, and it behaves like a simple string. Implicit unwrapping extracts the value from an optional item and uses the data type you’d expect from a successful dictionary lookup. Once unwrapped, you can use the variable directly. You don’t have to add that “unwrap this variable” exclamation point or use conditional binding.

A real danger arises from unwrapping nil values. If you replace the assignment to animal in the line marked 1 with "fox" instead of "cow", this code raises a fatal error in the line marked 2. The runtime complains that it unexpectedly found nil while unwrapping an Optional value. With great unwrapping comes great responsibility. Take care that you properly guard these items to ensure that you don’t attempt to unwrap nil.

Limit implicit unwrapping to when you know in advance that a variable will always have a value after some logical point. For example, if you’re responding to button taps or menu clicks, you probably don’t have to wonder “does this button or menu item exist?” It does. If it didn’t, you would never have reached your callback.

Don’t use implicit unwrapping for more general cases like dictionary lookups. That’s just asking for trouble. You can, however, print unwrapped items and test them against nil:

print(unwrappedSound) // prints nil
if unwrappedSound != nil {
    print("Valid:", unwrappedSound)

An error won’t be raised until you perform an operation that attempts to access the value inside.

As a rule, it is legal to assign a value, an optional value, or nil to an implicitly unwrapped variable. The following code is legal and will compile without error:

var myImplicitlyUnwrappedOptional: String!
myImplicitlyUnwrappedOptional = Optional("Value")
myImplicitlyUnwrappedOptional == "Value" // true
myImplicitlyUnwrappedOptional = nil // do not test except against nil
myImplicitlyUnwrappedOptional == nil // true
myImplicitlyUnwrappedOptional = "Value"
myImplicitlyUnwrappedOptional == "Value" // true

Assignments to both optional and non-optional values end with non-optional results, which you see by comparing against the non-optional string literal "Value". The danger lies in the nil assignment. A non-nil comparison tries to access the value and ends in a runtime error. The win is that you can perform an assignment to either optional or non-optional values with a single assignment.

An implicitly unwrapped scenario is common when working with Interface Builder. A view binding is optional; it may or may not be properly instantiated in the interface file. The view use is normally non-optional; presumably you set up the binding correctly. Implicit unwrapping simplifies code access to views at the cost of potential crashes during development and testing.

Swift 2’s one-line guard statement more or less offers a shorthand summary for the following initialization pattern:

let cowSound: String! = soundDictionary["cow"]
if cowSound == nil {throw Error.missingValue} // Handle nil case
// cowSound's value is now usable without explicit unwrapping

This assignment uses implicit unwrapping and then tests against nil. This is a safe check because the code makes no attempt to access an associated value. If the optional is nil, the if statement’s conditional block executes, transferring control away from this scope. Otherwise, execution continues, and the unwrapped cowSound constant is now available for use.

An implicitly unwrapped approach is both wordier and less safe than guard. It uses multiple statements compared with guard’s one, and it makes no conditions about leaving the current scope. If the throw request were replaced with a print statement, the nil case would continue forward. In doing so, it might encounter a use of cowSound’s nonexistent value and a nasty runtime crash.

Use implicit unwrapping cautiously and prefer guard where possible.

Guarding Failable Initializers

When an initializer returns an optional instance, it’s called a failable initializer. The initializer may succeed in establishing a new instance, or it may fail and return nil. For example, the following structure can be initialized only with even numbers:

struct EvenInt {
    let number: Int
    init?(_ number: Int) {
        if number % 2 == 0 {self.number = number} else {return nil}

Mark failable initializers by appending a question mark or an exclamation point to the init keyword (init? or init!). The punctuation choice depends on whether the initializer returns a normal optional instance or an implicitly unwrapped one. The implicitly unwrapped variation is almost never used in real life. According to my technical editor Kevin Ballard, you might theoretically encounter one when working with legacy code ported from Core Foundation or from any unaudited Objective-C API.

Use guard to test assignments from failable initialization. Here’s an example built around the EvenInt struct. When created with an odd number, an EvenInt initializer returns nil. The guard statement throws an error and exits the scope:

do {
    guard let even2 = EvenInt(2) else {throw Error.Odd}
    print(even2) // prints EvenInt(number: 2)
    guard let even3 = EvenInt(3) else {throw Error.Odd} // fails
    print(even3) // never gets here
} catch {print(error)}

Although you can use any approach for testing and unwrapping optionals, guard statements offer a natural synchronicity with failable initializers. Guarding initializers once again enables you to test for failed initialization at the point where you declare variables and constants and ensures that these bindings remain valid for the remaining scope.

Optionals and Sentinel Values

It is tempting to use optionals to signal when an operation has failed. The following snippet represents Swift prior to version 2 and is common to Apple’s traditional Cocoa patterns:

func doSomething() -> String? {
    let success = (arc4random_uniform(2) == 1) // flip a coin
    if success {return "success"} // succeed
    return nil // fail

if let result = doSomething() {
    // use result here

An unsuccessful operation returns nil, and a successful one returns a value.

Starting in Swift 2, reserve nil failures for initialization (although you can also use throws in initializers as well as in normal code) and prefer guard over if-let. Instead of using optionals as sentinels—that is, to signal success and fail conditions—use Swift’s new error-handling system. Error handling enables you to redirect the flow of control to mitigate errors and provide recovery support:

func betterDoSomething() throws -> String {
    let success = (arc4random_uniform(2) == 1) // flip a coin
    if success {return "success"} // succeed
    throw Error.failure // fail

do {
    let result = try betterDoSomething()
} catch {print(error)}

This refactoring skips optionals; the nil case is never of interest to the client code. Swift 2 error handling means you never have to unwrap.

When a thrown error is not of interest to its consumer, the try? operator can discard errors and convert results to optionals. This lets you integrate new-style errors with old-style optional handling. A try? expression returns a wrapped value for successful calls and nil for thrown errors:

guard let foo = try? somethingThatMayThrow else {
    // ...handle error condition and leave scope
if let foo = try? somethingThatMayThrow {}

The new error-handling system profoundly affects Cocoa-sourced APIs. Calls that used NSError pointers pre-Swift 2 change their return type from optional to non-optional, add the throws keyword, and eliminate error pointers from API calls. The new system sends NSError through do-try-catch. Compare the old approach with the new one:

// Old
func dataFromRange(range: NSRange,
    documentAttributes dict: [NSObject: AnyObject],
    error: NSErrorPointer) -> NSData?

// New
func dataFromRange(range: NSRange,
    documentAttributes dict: [String: AnyObject]) throws -> NSData

By introducing error handling, optionals can eliminate overloaded “failed call” semantics. It’s always better to use throws with well-defined errors than to use optional sentinel values. When you really have no information to pass back to the caller other than “I failed,” Swift 2’s updated error system simplifies creating an error enumeration to explain why that failure occurred. It is ridiculously easy to add informative errors that don’t require complicated NSError initializers:

enum Error: ErrorType {case BadData, MemoryGlitch, ItIsFriday}

Although many current APIs, especially asynchronous handlers and calls based on Core Foundation, have yet to transition to the new system, I encourage you to update your code to avoid using optionals as sentinel values. Return your optionals to the “contains a value or does not contain a value” semantics they were designed to handle.


Swift’s nil-coalescing operator ?? unwraps optionals and provides fallback values for the nil case. This next example checks uses nil-coalescing to assign a value to the sound constant:

let sound = soundDictionary["fox"] ?? "unknown"

If the lookup succeeds and the dictionary returns a wrapped value, the operator unwraps it and assigns it to sound. If not, it assigns the fallback value, which is "unknown". In either case, the assignment is not optional. sound uses a String type, not String?.

Use nil coalescing when you can supply fallback values that won’t interrupt a normal operational flow. When you cannot, choose guard instead and handle nil as an error case in the else clause.

Optional Assignment

In nil coalescing, you must supply a valid unwrapped fallback value. In cases where a fallback does not exist, consider optional assignment instead. This approach shortcuts any case where an optional value is unavailable. Normally, you embed assignments into an if-let scope. If the conditional binding succeeds, you assign the unwrapped value.

Alternatively, you might consider creating a custom operator that conditionally assigns values to a target, as in the following example:

// Thanks, Mike Ash
infix operator =? {}
public func =?<T>(inout target: T, newValue: T?) {
    if let unwrapped = newValue {
        target = unwrapped

This snippet builds an =? operator that supports simple assignment by wrapping and hiding its underlying if-let approach with a basic infix call.

The following assignments show this operator in action. The s string variable updates only for non-nil assignments:

var s: String = "initial value"
s =? "value 1" // value 1
s =? nil // value 1

Hiding if-let overhead makes the resulting conditional assignments cleaner and potentially more intuitively obvious to read through.

Optional Patterns

A Swift pattern matches a value’s structure rather than just the value itself. Patterns decompose and express a data structure, including component elements. They enable you to refer to an item’s subconstructs when testing instead of dealing with instances as a monolithic whole. Using patterns is a powerful and nuanced way to represent an instance, and it’s extremely handy for working with optionals.

The optional enumeration consists of two cases, .None and .Some. The .Some case contains an associated value of an arbitrary type:

enum Optional<T> {
    case None
    case Some(T)

With optionals, pattern matching enables you to limit statements to work only with the .Some case. You can reach into that case and bind the internal value using a single declaration. Follow the case keyword with a specific enumeration (the .Some case) and then bind the value nestled within it using let or var:

switch soundDictionary[animal] {
    case .Some(let sound):
        print("Using case, the unwrapped sound is \(sound)")
    default: break

The result is an unwrapped value, ready for access.

The case .Some(let constant) expression provides a one-to-one pattern match with the underlying optional. Optionals with the None case don’t match this pattern, so the case code need not consider nil scenarios.

There’s no denying that the case (case .Some(let constant)) is awkward to process visually. It lacks grace. Responding to the complexity of this optional pattern-matching code, Swift 2 introduces shorthand using a postfixed question mark:

switch soundDictionary[animal] {
    case let sound?:
        print("Using case, the unwrapped sound is \(sound) [2]")
    default: break

This postfixed question mark is nothing more than syntactic sugar for the .Some case. The results are simpler and more readable because this case matches and unwraps its optionals.

The preceding example shortchanges Swift because there’s still no major advantage in using this one-case switch statement over, say, if-let. When you introduce a simple where clause, you begin to see where pattern-matching optionals adds power and concision.

The following snippet uses a switch statement to differentiate unwrapped optionals whose string values are longer than five characters from those that are shorter:

switch soundDictionary[animal] {
case let sound? where sound.characters.count > 5:
    print("The \(sound) is long")
case let sound?:
    print("The \(sound) sound is under 5 characters")
default: break

Swift’s switch cases may experience significant logical overlap where small details select which case to execute.

Using pattern matching with if statements enables you to drop switch statement overhead and simplify one-case code even further. You lose the default statement and the surrounding switch, and you reduce the check to just a simple pattern comparison with where clause support. This if statement uses both pattern matching and a where clause for precise testing:

if case let sound? = soundDictionary[animal] where sound.hasPrefix("m") {
    print("Sound \(sound) starts with m")

The where clause isn’t limited to if-case. You can construct a similar statement using if-let:

if let sound = soundDictionary[animal] where sound.hasPrefix("m") {
    print("Sound \(sound) starts with m")

Pattern matching also enables you to iterate through an array and perform actions on unwrapped non-nil values. The for-case-let approach simplifies working with optional collections, as you see in the following snippet:

// Collect sound optionals into array
let soundOptionals = ["cow", "rhino", "dog", "goose", "hippo",

print(soundOptionals) // [Optional("moo"), nil, Optional("bark"),
                      // nil, nil, Optional("squeal")]

for case let sound? in soundOptionals {
    print("The sound \"\(sound)\" appears in the dictionary")

You can also use pattern matching with guard statements:

guard case let .Some(sound) = soundDictionary["cow"] else {fatalError()}

This example from Apple sample code uses a GameplayKit enumeration. It performs an enumeration pattern match and binds the targetAgent associated value:

guard case let .HuntAgent(targetAgent) = mandate else {return}
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020